Hey there folks--
I have a split database (Access 2002) with the tables on a network drive and linked to from the frontend. Obviously, for the speed aspect, I would like to run the front-end from the user's local machine.
I have a table in the front-end to store the version. Theoretically, I would like to compare the local version number with the network version number, and, if the local is older than the network, copy the network version down and run it. Presently, I have two databases, one is the actual front-end and the other consists only of a module to do the comparison/copy. Past that, I have a batch file running the CheckVersion and then the front-end.
My question: how can I do this more efficiently? The batch file window won't close until after the front-end has completed, and I've never really liked the idea of using a batch file in Windows anyway... Does anyone have any suggestions? Thanks!
-- michael~
I have a split database (Access 2002) with the tables on a network drive and linked to from the frontend. Obviously, for the speed aspect, I would like to run the front-end from the user's local machine.
I have a table in the front-end to store the version. Theoretically, I would like to compare the local version number with the network version number, and, if the local is older than the network, copy the network version down and run it. Presently, I have two databases, one is the actual front-end and the other consists only of a module to do the comparison/copy. Past that, I have a batch file running the CheckVersion and then the front-end.
My question: how can I do this more efficiently? The batch file window won't close until after the front-end has completed, and I've never really liked the idea of using a batch file in Windows anyway... Does anyone have any suggestions? Thanks!
-- michael~