Access 97 DB Wont Run on Windows 2003

[ian_w]

Hi,

Im currently implementing terminal server.

I have an access 97 database which all my users will use, back end sits on the server share and is a mapped drive, front end is on the users local drive at present but will become a shared DB on the terminal server.

I can get the DB running by opening in admin mode using the shift key but if I try to run it normally then it just opens access then closes immediately

Ive checked the event logs and all I get is this..

Faulting application MSACESS.EXE Version 8.0.0.3512

If I enter the DB as admin, then try to run the forms it crashes, is there something in Windows 2003 server that could be blocking them or the code behind them?

Regards

Ian

 

[Bilbo_Baggins_Esq]

Is there an error message when it crashes?

Is this happening while you're still using the front end on the local drive, or is this happening now that you've tried to move it as a shared db?

 

[ian_w]

Hi,

No error message, its just opens up access then closes straight away

It happens when I try to run it from the actual terminal server machine and when logged on a terminal console.

From the server it is back end on a Share (on actual machine), front end located on C: Drive.

Also happens when I try to run it from terminal client.

I have access 97 setup to run as a terminal services application, I can have the database open in admin mode on numerous machines at the same time.

Thanks

Ian

 

[The_Doc_Man]

First, did you buy a special license that lets you open Access from multiple places using Windows Terminal Services (TS)? For Ac97, that license option might not exist. What you are doing at the moment (with FE on each machine) is legal, but if you use Win TS as a way to run your DB from a workstation that does not have a legal copy of Access, you are in violation of the End User License Agreement for Ac97.

The reason it might not run is because Ac97 run locally (I.e. FE on local machine) has a registry setup that allows it to run. Access on the BE machine must ALSO be set up, and I strongly suspect the problem is that on the BE machine you have some missing references.

Search this forum for "Terminal Services" and "References" to understand more about the two issues I've mentioned.

 

[ian_w]

Hi, thanks for the reply.

We have a volume license (not sure of the correct terminology for Office licenses) for Office 97.

I have managed to get this working fine, the problem was the server had Office 2003 installed on it as well (Standard edition though with no Access )

Once I removed this and installed Outlook 2003 on its own it all works fine.