T
TADropik
My Access application is split in to 2 mdb's, a client interface and the data.
The client interface resides on the local computer and the data resides on
the server.
I often update the client interface and put the new version on the server
along side the data.
The user then executes a batch file that copies the client interface to the
local and opens it from there.
The problem with useing a batch file is it keeps the Cmd.exe window open
even after the Access mdb is open.
Is there a better way to do this so an extra window doesn't remain open?
The client interface resides on the local computer and the data resides on
the server.
I often update the client interface and put the new version on the server
along side the data.
The user then executes a batch file that copies the client interface to the
local and opens it from there.
The problem with useing a batch file is it keeps the Cmd.exe window open
even after the Access mdb is open.
Is there a better way to do this so an extra window doesn't remain open?