Re: "FE Updater" and macro security
- From: "Tony Toews [MVP]" <ttoews@xxxxxxxxxxxxxxx>
- Date: Tue, 10 Apr 2007 16:49:06 GMT
"Wayne" <cqdigital@xxxxxxxxxxxxxxx> wrote:
On my machine the old .exe file would start Access 2003 (the most
recently opened version). When I used the new .exe file it opened
Access 2007. Not sure why this is if it designed to work the same as
the old version.
Actually the way the utility currently works is it looks at the version of the
MDB/MDE. Then it goes down the registry keys from newest version to oldest looking
for a version of Access that is allegedly installed on your system. Then it executes
that version. So if you had A2000 and A2003 installed with an A2000 MDB/MDE it
would run A2003. I did this mostly because the assumption on my part was that A2003
would be inherently more stable.
However given the huge switching times with A2007 this is a royal PITA for the
developers. Now end users aren't likely going to have this problem because they will
very likely only have one version of Access installed.
So I'm thinking of what is the best way to handle this. Do I reverse the order to
look through the registry keys? Or do I add another entry line that has a default
version of Access? The latter approach would be better for ADPs as the utility
doesn't handle those gracefully at all.
By the way, thanks for an excellent utility.
Thanks for your kind words.
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
.
- Follow-Ups:
- Re: "FE Updater" and macro security
- From: Wayne
- Re: "FE Updater" and macro security
- References:
- "FE Updater" and macro security
- From: darren via AccessMonster.com
- Re: "FE Updater" and macro security
- From: Wayne
- Re: "FE Updater" and macro security
- From: Tony Toews [MVP]
- Re: "FE Updater" and macro security
- From: Wayne
- "FE Updater" and macro security
- Prev by Date: Problem setting LinkChildField property in VBA code
- Next by Date: Re: "FE Updater" and macro security
- Previous by thread: Re: "FE Updater" and macro security
- Next by thread: Re: "FE Updater" and macro security
- Index(es):
Relevant Pages
|