My database system is an front-end/back-end system. The backend db is on the file server and the frontend db is on users' local computers.
I created a vbs file and intended to use it to update the frontend database automatically. A user runs the vbs to start the frontend db. The vbs checks the version number of the frontend db and, if the verison number is not right, copy the front-end db from the file server over.
Here is the script.
The code works fine. I found out that, after the db is started, the db shuts down without a warning when a user tries to put a form in design mode. This sounds an extra to me because I certainly do not want a user to see a form in design mode. However, I want to know why this happens and whether this means that an Access db started by vbs is less stable.
Any advice is appreciated.
Seaport
I created a vbs file and intended to use it to update the frontend database automatically. A user runs the vbs to start the frontend db. The vbs checks the version number of the frontend db and, if the verison number is not right, copy the front-end db from the file server over.
Here is the script.
Code:
'code to check the version number
'code to copy over frontend using FileSystemsObject
dim appAcc
set appAcc=CreateObject("Access.Application")
appAcc.OpenCurrentDatabase "c:\prod\prod.mdb"
appAcc.Visible=True
set appAcc=nothing
The code works fine. I found out that, after the db is started, the db shuts down without a warning when a user tries to put a form in design mode. This sounds an extra to me because I certainly do not want a user to see a form in design mode. However, I want to know why this happens and whether this means that an Access db started by vbs is less stable.
Any advice is appreciated.
Seaport