Access 97 closing with no errors

[dzirkelb]

I have recently done a fresh install of access 97 to our 2003 server. I load up an access app, it brings up a form with a button...I clidk the button, and it closes the app with no errors, and leaves the ldb file in tact. Checking the event viewer, I get this message:

Faulting application msaccess.exe, version 8.0.0.5903, faulting module unknown, version 0.0.0.0, fault address 0x00202878.

It appears to be on the buttons that open forms / reports, but not those that run queries. Any ideas?

 

[The_Doc_Man]

Possibly broken references. Somewhere in the middle of those versions, Access changed for a while from a default of DAO to a default of ADO - AND the versions of the modules changed as well. Also, the ORDER of references can be an issue if any things in common between DAO and ADO aren't qualified by their module type.

E.g. Dim db as Database

vs. Dim db as DAO.Database

Finally, look up that address in the MS Knowledge base. Search for it. Sometimes you can find specific addresses associated with known issues.

 

[dzirkelb]

A brand new 2003 and access 97 server does not work either...I still get the same problem. I am still searching on the web for more solutions.

 

[dzirkelb]

It also happens on creating a new button on a form for a blank database...it closed automatically.

 

[The_Doc_Man]

This is either a security issue (some .DLL with wrong security) or a broken reference. However, saying that isn't necessarily productive.

I would suggest looking into your system's event logs using Event Viewer. Odds are that your system log and your application log would be viable places to look.

If that fails, MS Office has a "Refresh" option that would allow you to reinstall Access and repair any damaged or missing files.

Beyond that, we need more data to make a good guess.

 

[dzirkelb]

The error provided on the original post is what comes from the event viewer. I see no broken references (at least none are labeled as missing.) I gave the root drive (c) access to everyone and full control. I have reinstalled access, and I have even reinstalled the terminal services server. I dont think that it matters, but this is a VMWare server, so its install is an instanced.

 

[dzirkelb]

I have done some testing...it appears all of our 2003 servers have the same problem with access 97. One server gave this error:

The instruction at "0x00194b78" referenced memory at "0x00194b78". The memory could not be "written".

Clik ok to terminate the program.
Click cancel to debug the program.

Hitting cancel simply closes it.

 

[dzirkelb]

I have come to the conclusion that access 97 simply doesn't work with server 2003 and we are going to do a much needed upgrade.

 

[boblarson]

I have come to the conclusion that access 97 simply doesn't work with server 2003 and we are going to do a much needed upgrade.

Are you saying that you've had Access INSTALLED on the server and not on the individual machines?