diagnosing forced closing of Access

J

Jeff Rupprecht

After having opened a table out on the network and then
leaving Access for about one hour, I get the
message "Microsoft Access has encountered a problem and
needs to close. We are sorry for the inconvenience." This
happens several times a day. I sent off the error report,
but did not get any information back regarding a solution
to the problem. I looked at the data report, but that
didn't help much. I looked in the knowledge base and
thought I had found a solution. (I bumped up the ODBC
refresh interval to 32000.) But that did not help. Does
anyone know what the problem might be or how I would go
about relating the error report to a solution in the
knowledge base or elsewhere?

Jeff
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top