My client's Access 2002 db crashes. Why???

[Esmee]

Hi there,
Hope you guys can help me out.
For one of my clients I have created an Access 2002 db. It used to be
under Access97, but I have converted it to Access 2002, without any
problems.
My client works with this db in a multi-user environment.
(Another client of mine works with this db in a multi-user environment
as well, but under Access97. Done so for years now without problems)

The first client is experiencing frequent Access crashes. An error
appears claiming taht the application has performed an illegal
operation and needs to shut down. Then they ask whether the client
wants to send this error report to Microsoft. And after that the db is
really screwed up. (they have a good backup of the db, so they install
that again). What I can't figure out is why the db crashes and
especially so frequently (at least once a day).
This is the info I have so for. They work with Managed workplace. And
they recently told me that their network sometimes has a time-out of a
few seconds.
Maybe that's the culprit?
Furthermore, the crash usually occurs on a workstation which has been
idle for a time. Which I find even more strange.

Does anybody have any suggestions how I can find out what is happening
and even better, how I can go around solving this problem?

Thanks
Esmee

[Fletcher Arnold]

"Esmee" <g.********@ins pektor.nl> wrote in message
news:2e******** *************** ***@posting.goo gle.com...

Hi there,
Hope you guys can help me out.
For one of my clients I have created an Access 2002 db. It used to be
under Access97, but I have converted it to Access 2002, without any
problems.
My client works with this db in a multi-user environment.
(Another client of mine works with this db in a multi-user environment
as well, but under Access97. Done so for years now without problems)

The first client is experiencing frequent Access crashes. An error
appears claiming taht the application has performed an illegal
operation and needs to shut down. Then they ask whether the client
wants to send this error report to Microsoft. And after that the db is
really screwed up. (they have a good backup of the db, so they install
that again). What I can't figure out is why the db crashes and
especially so frequently (at least once a day).
This is the info I have so for. They work with Managed workplace. And
they recently told me that their network sometimes has a time-out of a
few seconds.
Maybe that's the culprit?
Furthermore, the crash usually occurs on a workstation which has been
idle for a time. Which I find even more strange.

Does anybody have any suggestions how I can find out what is happening
and even better, how I can go around solving this problem?

Thanks
Esmee

Is the application split front and back end? It certainly should be.

Is user-level security involved? If not (or if it wouldn't take too long to
reset) you could create a brand new blank database using Access XP (possibly
on site) and import all objects into the new one. Make sure it compiles.

I have found stability issues when swapping db's between machines with
different versions, which following the above advice has sorted out
entirely. An alternative is to start the database with the /DECOMPILE
switch and then later recompile on the XP machine.

Fletcher

[Esmee Waller]

Thanks for your reply Fletcher.
Of course the application is split front end and back end.
And I have already once created a completely blank database and imported
all objects into the new one.
And I have decompiled the application using Access XP.
But the problem still persists.
Thanks for your suggestions. Any more ideas?
That would be great
Esmee
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

[Fletcher Arnold]

"Esmee Waller" <g.********@ins pektor.nl> wrote in message
news:40******** *************@n ews.frii.net...

Thanks for your reply Fletcher.
Of course the application is split front end and back end.
And I have already once created a completely blank database and imported
all objects into the new one.
And I have decompiled the application using Access XP.
But the problem still persists.
Thanks for your suggestions. Any more ideas?
That would be great
Esmee

You could certainly look here for a start:
http://www.granite.ab.ca/access/corruptmdbs.htm

Fletcher

[David W. Fenton]

Esmee Waller <g.********@ins pektor.nl> wrote in
news:40******** *************@n ews.frii.net:

Of course the application is split front end and back end.
And I have already once created a completely blank database and
imported all objects into the new one.
And I have decompiled the application using Access XP.
But the problem still persists.
Thanks for your suggestions. Any more ideas?

If there are network timeout issues, that's likely to bollix up
Access, as it is completely unforgiving of that kind of thing.

Are user getting the "disk or network error" message? That's what
I'd expect if the timeout were the source of the problem.

It also seems strange to me that the data would get corrupted by a
crash like that. Perhaps memo fields are getting corrupted? If so,
you should strongly consider going to unbound memo fields. I explain
how to do that near the end of this post:

http://groups.google.com/groups?selm...entonbwaynetin
vali%4024.168.1 28.78

But my guess from your remark that you just restore the corrupted
MDB from a backup is that you are getting corruption in the front
end, not the back end, and that would likely be because you're
sharing it.

The effort of splitting is not worth a bucket of warm spit if you
still share the front end.

If that's not the case, then I can't think of anything else without
further information.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc