Terminal Server - Access 2003 & 2007

[Jared]

I have developed an accdb database that I have installed on Server 2003, with
clients connecting via terminal server. The company has 25 licences for
Office 2003 and uses several existing mdb databases. As upgrading to
Office/Access 2007 is a significant expense, the 2007 access runtime has been
installed.

Here's the fun part. Everytime an mdb file is opened, Access 2003
reinstalls. Then when the accdb is opened, the 2007 runtime reinstalls. This
happens each and every time a different database is opened, driving users
crazy.

The perfect result would be that mdb's open with 2003 and accdb's open with
the 2007 runtime. If anyone is able to help with this issue I would greatly
appreciate it.

 

[Arvin Meyer [MVP]]

Multiple versions always cause this. It is unavoidable since the registry
must contain the values necessary. You can use a version checker to open the
correct version, but there can still be the reinstall process of the last
used version is the earlier one. If you don't need any of the "features" of
2007, some of which violate relational database rules anyway, you should
just convert to the earlier (mdb) format, which will work with both
versions.

 

[Scott McDaniel]

I have developed an accdb database that I have installed on Server 2003, with
clients connecting via terminal server. The company has 25 licences for
Office 2003 and uses several existing mdb databases. As upgrading to
Office/Access 2007 is a significant expense, the 2007 access runtime has been
installed.

Here's the fun part. Everytime an mdb file is opened, Access 2003
reinstalls. Then when the accdb is opened, the 2007 runtime reinstalls. This
happens each and every time a different database is opened, driving users
crazy.

If you switch between Access 2003 and Access 2007, you'll have to go through the reinstall each time. 2007 SP1 was
supposed to make this a bit quicker, but it's still a bit of a wait when switching.

The perfect result would be that mdb's open with 2003 and accdb's open with
the 2007 runtime.

I'm not sure you could do this, although there's probably some Windows script file you could run to always associate
..mdb/.mde with 2003 and .accdb et al with 2007 whenever your databases closed. Even then, however, when switching from
one to the other you'll have the reinstall issue - and if you try to run both at once (i.e. a session of 03 and one of
07) you'll have no end of issues (at least I did).

If anyone is able to help with this issue I would greatly

appreciate it.

Scott McDaniel
scott@takemeout_infotrakker.com
www.infotrakker.com