Paul Barrako said:
Is there a method to determine what version of access
to 'open' a particular database with.
I'm lucky enough to have a significant population of
users still on access 97, but am writing new apps with
2003. The problem is trying to educate them on how to
use the right-click open with method...
my quesiton is, is there a way to change the properties
of the short cut (or other method) to automatically open
up the correct version of access that app was compiled in?
all machines have a dual install of 97/03.
Couple of different approaches.
One is to ensure the shortcuts have the explicit path of the
msaccess.exe executable in the target field. Another would be to use
the Auto FE Updater utility at my website which will automatically
open the appropriate version of Access which matches the FE.
1) You need to add explicit path and file names of the appropriate
versions of access to all the shortcuts. For example "C:\Program
Files\Microsoft Office 97\Office\msaccess.exe". Including the quotes
if you have any spaces in the path name which is very likely.
There are some programs out there which will automatically start the
appropriate version of Access.
One of those is ACCVER - Allows you to work with multiple versions of
MS Access databases. Detects the version of Access used to create your
MDB, MDE or MDA files and either reports the version number or starts
the appropriate version of MS Access.
http://www.aylott.com.au/accver.htm
Also see: INFO: Access 2000/Access 97 Coexistence FEPs (Frequently
Experienced Problems)
http://www.trigeminal.com/usenet/usenet019.asp?1033
Subject: INFO: Avoiding the default system.mdw loss when
re-registering Access 97
http://www.trigeminal.com/usenet/usenet018.asp
2) However you really want to put the FE on each machine or place in a
user specific directory on the server. This will help avoid some
weird error messages when users are changing the same forms record
source, filters and such as well as corruptions.
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.
In a Terminal Server or Citrix environment the Auto FE Updater now
supports creating a directory named after the user on a server. Given
a choice put the FE on the Citrix server to reduce network traffic and
to avoid having to load objects over the network which can be somewhat
sluggish.
Unfortunately there's a bug in the latest release in which I just
added the logic to start the appropriate version of Access. And it's
a long story but it's going to take a few or eight hours of work to
get the source code to a point where I can fix this problem. But I
don't have those few or eight hours right now. I will have in a few
days.
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