M
Mark Schirle
I have a frontend/backend A2k3 database. I have about 20 users. I use a
small vb program on the users machine to open the program. It checks the
copy of the frontend mdb file on the users machine and compares it to a
copy of the file I put in the same folder as the backend database. That
way if I need to make changes to the frontend I can make the changes on
my machine and copy it to the backend folder and when users open the
program if there is a new version it will load the new version over the
old version.
Now the problem. I've tried a couple of ways of comparing the files. By
date and by size. If they don't match I copy the new file. But the
problem is some of the procedures on the front end make changes to the
file. For example if they run a form that creates a new query it causes
their file to have a new size and a new modified date. So everytime they
open the file they have to wait for the "NEW" version to copy over even
though it's not new.
Any ideas?
TIA
small vb program on the users machine to open the program. It checks the
copy of the frontend mdb file on the users machine and compares it to a
copy of the file I put in the same folder as the backend database. That
way if I need to make changes to the frontend I can make the changes on
my machine and copy it to the backend folder and when users open the
program if there is a new version it will load the new version over the
old version.
Now the problem. I've tried a couple of ways of comparing the files. By
date and by size. If they don't match I copy the new file. But the
problem is some of the procedures on the front end make changes to the
file. For example if they run a form that creates a new query it causes
their file to have a new size and a new modified date. So everytime they
open the file they have to wait for the "NEW" version to copy over even
though it's not new.
Any ideas?
TIA