Tracking down a .mdb corruption problem

[Todd Lemen]

I am trackiing down a .mdb corruption problem that has cropped up in the last
week at a client locaiton. I don't know of any installations or changes that
may have occured in the last week to start the failures, but I have found an
interesting quirk in their client computers.

There are two copies of msjet40.dll on these machines; one in C:\I386, and
another in C\Windows\system32. The version in C\I386 is older than the
version in \\system32.

May I assume there should be only one msjet40.dll installed on each client?
May I also assume that msjet35.dll and msjet40.dll should not reside in the
same client (as is the case in some of the machines I've found here)?

All client machines are running Access 2K; all are pointing to the same
backend tables on a Win2K Server... I'm working my way through the rest of
the checklist...

Thanks,

TL

 

[Allen Browne]

The C:\I386 folder probably does not come into it. That could be where
Windows was installed from, and so the fact that it contains an old version
is probably irrelevant. Unless there is something weird with the Path, it is
the copy in system32 that would be in use. Hopefully that version is
4.0.8xxx.0 (where the xxx digits don't really matter.)

The presence of msjet35.dll is not a problem either. That's quite normal for
all of us who use Access 97 as well as later versions.

For general suggestions for avoiding corrupt MDBs, see:
Preventing Corruption
at:
http://allenbrowne.com/ser-25.html

 

[Todd Lemen]

Thx, Allen.

TL

The C:\I386 folder probably does not come into it. That could be where
Windows was installed from, and so the fact that it contains an old version
is probably irrelevant. Unless there is something weird with the Path, it is
the copy in system32 that would be in use. Hopefully that version is
4.0.8xxx.0 (where the xxx digits don't really matter.)

The presence of msjet35.dll is not a problem either. That's quite normal for
all of us who use Access 97 as well as later versions.

For general suggestions for avoiding corrupt MDBs, see:
Preventing Corruption
at:
http://allenbrowne.com/ser-25.html

 

[Jerry Whittle]

I have a white paper in a Word document named Fix Corrupt Access Database
towards the bottom this page that may help you:
http://www.rogersaccesslibrary.com/OtherLibraries.asp

 

[Tony Toews]

I am trackiing down a .mdb corruption problem that has cropped up in the last
week at a client locaiton. I don't know of any installations or changes that
may have occured in the last week to start the failures, but I have found an
interesting quirk in their client computers.

Any wireless connections? Those are very unstable from an Access
viewpoint.

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

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]

MDB is crap don't listen to these sissies

dont ever use MDB for anything in the real world. i mean, duh!!

if you care enough to build a database; use SQL or MSDE.. MDB is
russian roulette; it isn't reliable or stable enough for ANYTHING EVER
not even a single record.

 

[aaron.kempf]

'any wireless connections'

shit kid; i mean seriously

blame EVERYTHING _EXCEPT_ the crappy database format why dont you?

 

[Tony Toews]

MDB is crap don't listen to these sissies

dont ever use MDB for anything in the real world. i mean, duh!!

if you care enough to build a database; use SQL or MSDE.. MDB is
russian roulette; it isn't reliable or stable enough for ANYTHING EVER
not even a single record.

<shrug> Aaron, MDBs have their purpose as do MSDE or SQL Server.

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]

MDB is worthless as are MDB dorks

 

[Tony Toews]

MDB is worthless as are MDB dorks

Clearly our opinions differ.

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 just think that it's funny.. i mean.. ADP is a clearly superior
solution for these reasons:

a) performance
b) ease of deployment (tables and queries are magically stored in one
place)
c) stability
d) functionalty - TSQL is just more powerful than silly VBA and ASQL
e) price - it's FREE with MSDE; same price as mdb
f) ability to schedule jobs - not trivial
g) ability to take real BACKUPS and RESTORES
h) ability to leverage 100s of 3rd party development tools
i) ability to use triggers
j) object level; column level permissions

I just believe that you MDB sissies are misguided by a bunch of MDB
sissies and i wish that you MDB sissies would STFU and go to some silly
microsoft.public.access.mdb newsgroup. just because it's
microsoft.public.access doesn't mean that this newsgroup has nothing to
do with ADP.

ADP is the best product to ever come out of redmond.. i mean-- have you
seen the sproc designer included in AC2002 or AC2003?

I mean.. seriously.. have you ever LOOKED at it?

I'm FASTER at developing ADP solutions that anyone else is with MDB; i
mean-- sproc binding is MORE POWERFUL so it's pointless to use MDB for
anything.

and when i want to digest sprocs with parameters?? in a web
environment-- i can do this.

with MDB you have to rewrite all your queries without parameters; i
mean-- MDB is just a silly silly product and you guys are all sissies

 

[Tony Toews]

i just think that it's funny.. i mean.. ADP is a clearly superior
solution for these reasons:

a) performance

Some things are faster in Jet. Some things are faster in SQL Server.

b) ease of deployment (tables and queries are magically stored in one
place)

Hmm, how about ease of deployment of an MDB containing the queries,
forms, reports and modules. No difference there.

There are other deployment issues with MSDE.

c) stability
Sure.

d) functionalty - TSQL is just more powerful than silly VBA and ASQL

e) price - it's FREE with MSDE; same price as mdb
Ok.

f) ability to schedule jobs - not trivial

Not a big deal.

g) ability to take real BACKUPS and RESTORES

Backup and restores can be done with MDBs as well. Now granted the
user has to get out of the database while this is happening. So sure
SQL Server is better there.

h) ability to leverage 100s of 3rd party development tools

And there aren't hundreds of 3rd party tools in Access?

i) ability to use triggers

I thought MS was deprecating the use of triggers.

j) object level; column level permissions

Sure that would be useful

I just believe that you MDB sissies are misguided by a bunch of MDB
sissies and i wish that you MDB sissies would STFU and go to some silly
microsoft.public.access.mdb newsgroup. just because it's
microsoft.public.access doesn't mean that this newsgroup has nothing to
do with ADP.

The above comments are pretty useless.

ADP is the best product to ever come out of redmond.. i mean-- have you
seen the sproc designer included in AC2002 or AC2003?

I mean.. seriously.. have you ever LOOKED at it?

No, I haven't. Other MVPs have commented in the past that ADPs have
their own set of quirks.

I'm FASTER at developing ADP solutions that anyone else is with MDB; i
mean-- sproc binding is MORE POWERFUL so it's pointless to use MDB for
anything.
Sure.

and when i want to digest sprocs with parameters?? in a web
environment-- i can do this.

with MDB you have to rewrite all your queries without parameters;

Haven't done any web work so no opinion on this.

i mean-- MDB is just a silly silly product and you guys are all sissies

And I'm sure that statement will have everyone agreeing with you.

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

 

[Larry Linson]

I mean.. seriously.. have you ever LOOKED at it?

Yes, as a matter of fact, I have worked with ADP. It isn't "awful", but it
isn't as "astonishing" as you seem to think.

And, there are some security exposures required that would cause most SQL
Server DBA's to experience panic attacks.

I'm FASTER at developing ADP solutions
that anyone else is with MDB; i mean-- sproc
binding is MORE POWERFUL so it's
pointless to use MDB for anything.

As the poster known as "aaron" cannot possibly know how quickly the people
he's addressing can develop any given ADP solution, I have to assume that he
is either terminally conceited or ingesting substances that alter his
perception of reality.

Larry

 

[aaron.kempf]

have you used DAP?

DAP from ADP is an awesome awesome stack.. i mean.. WOW

it's a PITA: but then again, so is adp; and so is mdb

i just wish that they could start testing this software before they
sell it.. and i wish that they would start fixing bugs when WE have
bugs for them to fix.

I just wish that I could call up some governmental agency; and file a
complaint that Microsoft is selling shoddy software. They are
fraudulently selling buggy software; they promise to fix bugs.. and
they dont deliver.

Microsoft is abusing their monopoly power--- just because there isn't
anyone else out there; that doesn't mean that they are DOING GOOD
ENOUGH.

DOING GOOD ENOUGH would be a simple review of bugs; listening to people
when they submit bugs..

DOING GOOD ENOUGH would be fixing MDB _AND_ fixing ADP.

It just pisses me off; that all you guys sit around and accept 'good
enough' from microsoft
and I have seen a better way-- i have seen an awesome application with
more powerful queries; and more powerful parameters.

i have seen a better way of doing things; and i wish that i could just
wave my magic wand; and show to the world the beauty of ADP

it just pisses me off that Microsoft won't have an open discussion
about ADP; and they keep on promising us a SQL 2005 patch for ADP
2003.. but does anyone know when it's coming??

and i mean.. the whole Access department at Microsoft should be shot.
Because you guys have been selling SHIT products for way too long.

AND IM SICK AND FUCKING TIRED OF DEALING WITH BUGS IN ACCESS

i mean-- who do these people think that they are?

they're snake-oil salesman; used-car-salesman of the vilest breed

selling SHODDDY SOFTWARE and growing a warchest of $50 BILLION?

FIX SOME GODDAMN BUGS MICROSOFT!!!!

I have a list of bugs; i would like to work with the rest of you
idiots; in order to compile a comprehensive list of bugs in Access; and
we submit them via Ralph Nader. Ralph shows up and says 'look Billie;
you need to refund the purchase price of every copy of Microsoft Access
EVER SOLD or fix these 27 bugs'

im just pissed off of working with crappy software; it's like-- this
software just isn't fit to be sold.

if i had it to do over again; i would have stayed working with php

 

[aaron.kempf]

Tony;

you seriously haven't checked it out?

i mean seriously here

you haven't started up an ADP and written a sproc?

that just blows my mind; who the hell do you think that you are?
you're not valuable; you're not a professional

i just want to know why it is that all MVPs are sissies.. i mean.. why
is it that Microsoft gives the awards to the biggest WIMPS?

i just dont understand it.

do you really accept what other mvps say?

maybe you should learn to think for yourself kid

 

[aaron.kempf]

Larry

and seriously here

what security problems do you see in ADP?

i mean-- seriously here

having beancounters write views and sprocs?? that is no more dangerous
that having them write mdb queries

allowing them to see the table directly?

big friggin deal-- SQL Server is much more robust than MDB and it's
HILARIOUS that you guys think that it's somehow a bigger deal to let
end users poke through SQL Server data; but then you dont give a shit
about data in MDB?

is that what you're saying?

how is it SCARIER to let people change data in SQL?


SQL has **BACKUPS** where MDB you have to reboot a file server 5 times
a day in order to get anyhting done

i just dont understand you silly silly mdb folk
never have, never will

 

[aaron.kempf]

and no, im not terminally conceited.

I AM RIGHT

and im not afraid to let you wimps know that there is a better way

 

[Tony Toews]

Tony;

you seriously haven't checked it out?

i mean seriously here

you haven't started up an ADP and written a sproc?

that just blows my mind; who the hell do you think that you are?
you're not valuable; you're not a professional

i just want to know why it is that all MVPs are sissies.. i mean.. why
is it that Microsoft gives the awards to the biggest WIMPS?

i just dont understand it.

do you really accept what other mvps say?

maybe you should learn to think for yourself kid

Correct, I've spent no time with ADPs as I've read numerous comments
regarding the shortcomings of ADPs. And I have need to play with
ADPs as MDBs work just fine for me.

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

 

[Tony Toews]

MDB you have to reboot a file server 5 times
a day in order to get anyhting done

Rubbish. I have clients who haven't rebooted servers in months and
months.

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

 

[Larry Linson]

and seriously here

what security problems do you see in ADP?

Google comp.databases.ms-access for Lyle Fairfield's comments on the
subject. Lyle was an early, and strong supporter of ADPs -- he doesn't use
them any more.

SQL Server databases work very nicely via MDB and ODBC, and have since
Access 2.0 (maybe 1.1 -- I never had occasion to do an Access 1.1 client
application). And, MDB and ODBC also work very nicely with server databases
other than Microsoft SQL Server -- Sybase, Informix, Oracle and others. ADP
is a "one-trick pony" -- either you use MS SQL Server or you find another
development tool.

Umm. Lots of people _think_ they are "RIGHT". If you don't think you are
"terminally conceited", how about "terminally condescending"?

Larry