Dear Tipsters,
I am using Access2k as a front-end to a SQL2k database that is used by 25+ users. The way it was originally designed was that each users PC held a local copy of an mde file. When they log onto their machine, part of the login script would check the modify date of the mde file and compare it to the modify date on a copy held on a deployment server, changing them if the server version was newer.
I have had to make some changes to the front end, and now it seems that the modify date gets changed each time a user uses it - making the rollout procedure useless (the local version date is always after the server version date)
My question is what changes the modify date? Will the modify date change when someone populates forms etc?
Thanks
mrees
I am using Access2k as a front-end to a SQL2k database that is used by 25+ users. The way it was originally designed was that each users PC held a local copy of an mde file. When they log onto their machine, part of the login script would check the modify date of the mde file and compare it to the modify date on a copy held on a deployment server, changing them if the server version was newer.
I have had to make some changes to the front end, and now it seems that the modify date gets changed each time a user uses it - making the rollout procedure useless (the local version date is always after the server version date)
My question is what changes the modify date? Will the modify date change when someone populates forms etc?
Thanks
mrees