Shared records corrupting in Access XP runtime

[LW]

I'm running into a problem since I upgraded from Access 97 runtime to Access
XP runtime. Sometimes when 2 or more users are sharing a record, the record
will corrupt. The corrupted record literally has Chinese characters in most
fields or #Error in all fields. Another problem is new records that
disappear once they are created. Once the table corrupts, a compact/repair
eliminates the bad record.

The Access 97 database and runtime interface worked for 9 years without
these problems until I upgraded to XP. Now the problems occur as much as 3
times a day. Records are accessed by users in front-end forms that are bound
to tables that are linked to the backend. I have made sure that I have
installed the most recent service pack for runtime.

Any ideas?

LW

 

[Kevin3NF]

Last time I saw this, it was a bad hub in the network, not the version of
Access...

 

[Tony Toews]

I'm running into a problem since I upgraded from Access 97 runtime to Access
XP runtime.

Was this on the same computer? No new computer? OS still the same?
Anything new on the network side of things? Are you seeing any "Disk
or Network Error"s?

Kevin is correct. I'd look elsewhere than Access for this problem.

For more information on corruption including possible causes,
determining the offending PC, retrieving your data, links, official MS
KB articles and a list of vendors who state they can fix corruption
see the Microsoft Access Corruption FAQ at
http://www.granite.ab.ca/access/corruptmdbs.htm

The Access 97 database and runtime interface worked for 9 years without
these problems until I upgraded to XP. Now the problems occur as much as 3
times a day. Records are accessed by users in front-end forms that are bound
to tables that are linked to the backend.

Does each user have their own copy of the FE MDB/MDE? Although this
would tend to cause corruptions in the FE and not the BE

I have made sure that I have
installed the most recent service pack for runtime.

Do all users have the same version of Jet?

What I've done is use the various API calls available and am checking
the version number and date/time of a crucial dll, msjetxx.dll, to
ensure it matches what I have on my system. See the Verify
Appropriate Jet Service Pack is installed page at my website for more
details including sample code:
www.granite.ab.ca\access\verifyjetsp.htm

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

 

[aaron.kempf]

I call bullshit on this; these fuckers blame EVERYTHING on the network

Access Data Projects doesn't just randomly crap out like this