'MSACCESS has generated errors..'

[trancelogic]

Hello. I wonder can anybody help me with a persistent problem that has recently started to occur when running code from a form. I get the message 'MSACCESS has generated errors and will be closed by Windows. An error log has been created.' Access is then immediately halted. (and I don't know where to look to find the error log.)

What is odd, is that the message does not recur in exactly the same point in the program, which suggests the problem has nothing to do with the code itself.

(The problem seems to have started - or become more frequent - since the server I am working on recently switched from NT to Windows 2000. I am using Office 97.)

Does anybody know what might be going on? I'd appreciated any comments. Thanks for your time, and my apologies if this is an old question..

 

[rich.barry]

I had some really inconsistent problems recently which were to do with the database being corrupt.
Remedy was to create a blank database and import everything from the problematic one into it.

Perhaps you might start by trying this.

 

[chenn]

I know what you mean. I've been searching postings to find any information on windows 2000 server compatabilities with access 97. I maintain about 180 access databases and usually everything runs smoothly. However, this past week our company converted all our servers to win 2000. Since the new sever was installed, my security (.mdw) file has corrupted twice, and I've had at least 10 databases corrupt. I'll keep looking and I'll post any results I find.

Good luck.

 

[chrismcbride]

I run a medium sized A 97 db on a brand new server running Win 2K SBE and I have had some of the issues you describe. The errors I get seem to indicate that, for some reason, the connection between the server and client is compromised somehow. It is not consistant nor have I been able to diagnose the error.
One thing is for sure, it got WAY worse when I tried to move the db to A XP. Plus it seems to be getting a little worse lately.
I am going to try a dedicated NT fileserver strictly for the db, but would be glad to hear of similar experiences.

Chris

 

[chenn]

Pretty sure Pat is right. I've been searching for some answers on this and here are a couple sites with the most info I was able to find.

http://www.datarevive.com/support/kb/kb2202.htm

item # 7

http://info.connect.com.au/docs/hosting/vws/option/access-nt.html