Replication vs. FE Auto Update

[Tony Toews [MVP]]

The user doesn't open the master FE stored on the network drive. He runs a
copy of the master FE which my version checker downloads to his local drive.

However the users FE date/time changes every time you open the
MDB/MDE. Well not every time but very often and likely a very moot
point.

There David is pointing out that you might as well copy the FE MDB
down every time.

In my Auto FE Update I store the date/time of the FE MDB/MDE that's on
the file server in an INI file in the client FE folder. I then
compare that date/time, and not the users FE MDB/MDE date, against the
date/time of the FE MDB/MDE on the server.

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/

 

[David Portwood]

However the users FE date/time changes every time you open the

MDB/MDE.

I've explained myself badly. I never check the datetime of the user's local
FE.

In my Auto FE Update I store the date/time of the FE MDB/MDE that's on
the file server in an INI file in the client FE folder. I then
compare that date/time, and not the users FE MDB/MDE date, against the
date/time of the FE MDB/MDE on the server.

Yes, that's what I'm doing, too - although I'm not using an INI file to
store the date/time of the master FE. Each user runs a local copy of the
version checker applet. This is just a plain old mdb file. I store the
datetime of the master FE in a table in this mdb. I also store the path to
the local folder in which the FE resides on the user's machine. The table
consists of one record with two fields.

I don't know if it is better to store this data in a local table versus an
INI file. I access the table data using a recordset variable. I suppose you
pull the data from an INI file using a system call? But I don't know
anything about INI files and I do know about recordsets. So, for me, it was
simpler to use a local table.

 

[Tony Toews [MVP]]

I don't know if it is better to store this data in a local table versus an
INI file. I access the table data using a recordset variable. I suppose you
pull the data from an INI file using a system call? But I don't know
anything about INI files and I do know about recordsets. So, for me, it was
simpler to use a local table.

Not a problem. I chose to use INI files because that was a light
weight solution and the data can be read by anyone using notepad. And
yes lots of API calls. My Auto FE Update has hundreds of API calls in
it reading/writing INI files, registry entries, creating/reading
shortcuts, etc, etc, etc.

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/

 

[David W. Fenton]

Two mouse clicks and you've created an MDE. Unless you have a
error in your code which could take a few minutes to fix.

.... and if that's the case, you should be happy to find out about it
so that it can be fixed. Of course, I decompile and fully recompile
before distribution, so creating an MDE never fails for me.