frequent database corruption

[Tony Toews]

the LDBVIEW utility provides you an interface to all
the information available in an LDB (through a DLL):

http://support.microsoft.com/default.aspx?scid=kb;EN-US;176670

Trouble is LDBView gives you misleading results for Jet 4.0 MDBs. Everyone who logs
out is marked suspect even though they aren't.

I now have all my A2K apps record on user startup what version of
the MSACCESS.EXE file they are using and what version of
MSJET40.DLL.

For the original poster, not for you David:

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

Is this server running MS Exchange, by chance? I had a client once
where an Exchange hot fix started causing corruptions. As Exchange
wasn't even in use on the server (and shouldn't have been running
and should not have been patched), we backed out the hot fix and the
corruption never recurred. That was a very long time ago (early
1999) with very different versions of software (and replication
involved, to boot), but it taught me a very important lesson:
corruption can be caused by changes to the software configuration of
a server, something I'd never really considered before that point.

Ah, very interesting. Thanks.

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

 

[Mitchell Thomas]

Here is the update:
29th june we did the oplocks disable.
Till 8th july no problem - we were about to distribute sweets in the
office when

1. On 9th one table in the BE database had two problems
a) One record had "#ERROR" in every field
b) Another record had oriental characters (like japanese or chinese)
in every field and the id field (which usually has a four digit
number) had a minus 9 digit number.
c) We lost one record.
Also to be able to use the table further, we had to copy all the
uncorrupted records (around 3578) to a fresh table with the same
structure.

Any ideas what could have caused all this and HOW TO PREVENT THIS.

2. Today, 12th July we once again got the unrecognised database - need
to repair error message - and had to run a compact and repair.
Any ideas where we go from here.

thanks ina advance
adirat

We experienced the same problem with data being corrupted into chinese
characters, i spent a couple of months trying to figure out this
problem even worked with Microsoft directly, could not find the cause
of this problem, never had this problem with Access97, only
Access2002. We finally just converted our BE to Oracle, since then
no more corruption with chinese characters, still using Access 2002 as
FE. I think there is a bug in Access 2002 that is partly responsible
for causing this corruption.