Access 97 Corruption

[Bob Wassmer]

In a Access 97 database that is running on a file server
(W2K) accessed by a number of workstations (12 or so)
running 98, XP and W2K, corruption has been occurring
more and more frequently in the past 6 months. The most
recent event left us w/ a database that could not be
repaired by any means (compact, repair, import into new,
MS jet repair), until we tried to open in Access 2000.
This repaired the db, leading me to consider the
possibilty that some Access 2K-specific artifact was
contained in the corrupt db.

Examining the MS Jet engine that resides on each unit we
found that all units have MS Jet 4.0 dll, but most also
have Jet 3.5. The front end application uses the BDE
Native MS Access driver IDDA3532.DLL version v. 5.1.0.4.

The registry seems to list only the 4.0 dll, but should
Access 97 be using 4.0? If not, is there a way to have
Access 97 use the 3.5 dll while other apps use 4.0?

Any help wil be much appreciated.

Thanks.

 

[Douglas J. Steele]

Access 97 should be using DAO 3.5x, although it is possible for it to use
DAO 3.6x.

You might check out what Tony Toews has to say about corruptions at
http://www.granite.ab.ca/access/corruptmdbs.htm

 

[Bob Wassmer]

Thanks

-----Original Message-----
Access 97 should be using DAO 3.5x, although it is possible for it to use
DAO 3.6x.

You might check out what Tony Toews has to say about corruptions at
http://www.granite.ab.ca/access/corruptmdbs.htm

--
Doug Steele, Microsoft Access MVP

(No private e-mails, please)






.

 

[Tony Toews]

The most
recent event left us w/ a database that could not be
repaired by any means (compact, repair, import into new,
MS jet repair), until we tried to open in Access 2000.
This repaired the db, leading me to consider the
possibilty that some Access 2K-specific artifact was
contained in the corrupt db.

No. A2000 can frequently open up corrupted A97 MDBs.

Examining the MS Jet engine that resides on each unit we
found that all units have MS Jet 4.0 dll, but most also
have Jet 3.5. The front end application uses the BDE
Native MS Access driver IDDA3532.DLL version v. 5.1.0.4.

So the FE application isn't an Access MDB/MDE then? But Delphi
instead.

It may very well be that you don't need Jet installed on the system at
all if the IDDA3532.DLL driver gives you the ability to view and
update data in MDBs.

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

 

[Bob Wassmer]

So, perhaps it would be a good idea to remove the MS Jet
engines from the server and limit access to the directory
where the MDB resides. If it is only the application that
ever updates the mdb, at least we could rule out
misaligned Jet engine versions.

Thanks for your help.

 

[Tony Toews]

So, perhaps it would be a good idea to remove the MS Jet
engines from the server and limit access to the directory
where the MDB resides. If it is only the application that
ever updates the mdb, at least we could rule out
misaligned Jet engine versions.

<shrug> I have no idea as to the specifics as I've never used the
BDE.

Needless to say I'd do all this one step at a time to ensure things
didn't get worse.

I'm starting to wonder though if users aren't hitting the MDB directly
using Access in addition to the Delphi FE. Possibly that's where the
mismatch in versions and corruptions are happening.

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