Problem running Access 2003 and Access 2000 apps on same machine.

[Rathtap]

We have an Access 2003 compiled application that is installed on a
client computer that already has Access 2000 apps on it. The Access
2003 app works fine but when they try and run the Access 2000 app it
errors out. However if they start up Access 2000 and then attempt to
run the Access 2000 app it works. It seems to me that when the 2003
app runs it registers the runtime dlls which then cause the 2000 app
to stop working. Somehow starting Access 2000 resets the dlls.
Could this be an valid explanation? If so could somebody tell me what
the runtime dlls are for both 2003 and 2000.
Thanks for your help.

 

[Mark C]

I don't know the entire reason, but it does seem to me that that is how
it works. When either of the apps (2000 vs 2003) they register
themselves as handlers for mdb adp etc and the only way to get them to
launch correctly is to launch them with the correct run time path in the
shortcut.

e.g.
c:\program files\common files\access2000runtime\msacess.exe project.mde

Works fine for my multi version apps.

Mark

(e-mail address removed) (Rathtap) wrote in @posting.google.com:

We have an Access 2003 compiled application that is installed on a
client computer that already has Access 2000 apps on it. The Access
2003 app works fine but when they try and run the Access 2000 app it
errors out. However if they start up Access 2000 and then attempt to
run the Access 2000 app it works. It seems to me that when the 2003
app runs it registers the runtime dlls which then cause the 2000 app
to stop working. Somehow starting Access 2000 resets the dlls.
Could this be an valid explanation? If so could somebody tell me what
the runtime dlls are for both 2003 and 2000.
Thanks for your help.

.................................................................
Posted via TITANnews - Uncensored Newsgroups Access-=Every Newsgroup - Anonymous, UNCENSORED, BROADBAND Downloads=-

 

[Pieter Wijnen]

My solution has always been to avoid the .mdb extension
make your own
ie
..a2k
..a97
..a2kXP

sample registry file:
-------------------------------------
REGEDT4
[HKEY_CLASSES_ROOT\.a2k]
@="Access.Application.9"
-------------------------------------
and let Access versions quarrel as much as they want about .mdb ;-)

HTH

Pieter

 

[Tony Toews]

We have an Access 2003 compiled application that is installed on a
client computer that already has Access 2000 apps on it. The Access
2003 app works fine but when they try and run the Access 2000 app it
errors out. However if they start up Access 2000 and then attempt to
run the Access 2000 app it works. It seems to me that when the 2003
app runs it registers the runtime dlls which then cause the 2000 app
to stop working. Somehow starting Access 2000 resets the dlls.
Could this be an valid explanation? If so could somebody tell me what
the runtime dlls are for both 2003 and 2000.

Close. But not DLLs.

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

Also 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

Mark and Peters suggestions will work quite well too.

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