"Michiel Rapati-Kekkonen" <mi*****@nonsense.zzwrote:
>I would like to generate a versionnumber (and save it in a internal table)
on the moment I make a mde.
You could create a subroutine which you always call to do the version number update
and make the MDE which would have the following code in it.
You can automate MDE creation with the Application.RunCommand method, using
acCmdMakeMDEFile as the argument, either in code or with a macro.
For Access 97 use SysCmd 603, "CurrentMDBName.MDB", "MDEName.MDE"
>Then there would also be such version tabel in the central, linked data mdb.
When the mde is opened it checks if the number in the datafile is higher,
lower or the same.
If it is lower than it's own, it would update the number in the datafile.
If it is lower it knows that there is a newer version of the application and
dispalys a message to urge the user to fetch it.
Is this a good plan?
And is it possible?
Sure is. But the Auto FE Updater just looks to see if the date/time of the MDE, and
other files, on the server has changed. If they're changed it automatically copies
down the new files. Now given that Access updates the date/time of the MDE/MDE
while the user is in it the date/time of the files on the server are stored in an INI
file on the workstation.
There are links to such sample code out there on the page mentioned below.
I specifically created the Auto FE Updater utility so that I could make changes to
the FE MDE as often as I wanted and be quite confident that the next time someone
went to run the app that it would pull in the latest version. For more info on the
errors or the Auto FE Updater utility see the free Auto FE Updater utility at
http://www.granite.ab.ca/access/autofe.htm at my website to keep the FE on each PC up
to date.
Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog -
http://msmvps.com/blogs/access/