By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
454,962 Members | 1,266 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 454,962 IT Pros & Developers. It's quick & easy.

Request for Steve Jorgensen

P: n/a
DFS
Steve,

In the Access on Citrix thread you remarked on a system someone else showed
you.

I'm sort of embarrassed to ask, but is there a chance you can post the
source code utilized in the 'little MDE' you talk about. I don't want to
chase dead-ends if I can help it.

I'll owe you one. Thanks
=======================================
You said:
It was shown to me by a fellow names Steve Titus.

You don't copy the file on logon, that's an additional process that has to
be
implemented and maintained by IT, and it can break invisibly - that's bad.

What you do is have the little MDE that initially launches (that one
actually
is shared, but doesn't stay open very long) and the one that runs the
applciation. The first MDE looks for the personal copy of the main
application MDE, checks the version, and copies the newest version on top of
it if it's not up to date. Next, it launches the personal copy of the
application MDE in another instance of Access, then that first MDE exits.
This all takes less than 1/2 a second to run. This also works without
having
to log out. To update everyone, just have everyone exit and restart the
application.

To check the version, you can use a table in the MDE, but I just like to use
an extra file that gets copied to the same directory as the database called
something like "2005-10-02v2.ver". You can look for "*.ver" in the database
directory, and if you don't find one, or it is the wrong version, copy the
update.
=======================================

Nov 13 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.