Corruption Problem with 2.0

[Tony Toews [MVP]]

MDBs haven't been updated in several versions of Access and thus are
dead end technology.

Wrong.

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's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[a a r o n . k e m p f]

who cares

if your database craps out, move the **** up to sql server

spit on anyone using jet

 

[a a r o n . k e m p f]

name one bug fix

how about.. oh.. cleaning up after DAO variables?
how about.. making SQL Passthrough linking available through the
linked table manager?

Your piece of shit database is completely unusable.

Stack queries on top of queries and tell me how much better _THAT_ has
gotten over the years.

Stack 100 queries on top of each other for all I care.
Cuz it works in SQL Server.

SQL Server never goes on strike and just throws a tissy.
Access does when you stack 3 queries on top of each other

You can't share variables in JET_- like you can with SQL Server.
Access just isn't robust enough to be anything other than a
paperweight.

www.microsoft.com/sql

so sorry that you're stuck in the 1st grade of the db world

 

[LeeG]

I have a multi-user (approx 8 people) on a back-end 2.0 database which is
currently about 86,000KB in size. They each have a front end on their local
hard drive, using whatever Access version is on their pc (from 2000 up to
2007). The backend has been working just fine for several years until a few
weeks ago.

In the last 3 weeks we've been getting "unrecognized database format" errors
(7 times total). I've been able, thus far, to repair/compact, but it's taking
longer each time. I'm running through various checks to see if I can find the
cause.

At the same time, I think it's probably time to bite the bullet and convert
the back end to a higher version. I know this has been discussed many times,
but is there a favorite set of procedures to do this conversion? And a
version more stable than others that I should move to? We don't have that
many tables, but I think the biggest headache for me will be dealing with
several auto-number fields. Also, is it ok to have two backend databases?
Because of size restrictions, I thought it might be better to split the one
backend into two this time?

Any and all help, comments, suggestions would be greatly appreciated. Thank
you!
Louise

 

[LeeG]

An issue was introduced with WinXp XP3 as well as a security update Microsoft
shipped in late May (MS08-028 / KB950749) that is causing the issue you are
experiencing. Call Microsoft Customer Support and request hotfix KB954193.

 

[Louise54]

Thank you LeeG! This was certainly our problem, and we were at our wits end
trying to figure out what was causing it. Just saw your reply two days ago,
and after immediately installing the hotfix, we have gone two straight days
without an issue - something that hasn't occurred since late May!
Once again, thank you for taking the time to provide me with this information!
Louise

 

[Guest]

Thank you LeeG! This was certainly our problem, and we were at our wits
end
trying to figure out what was causing it. Just saw your reply two days
ago,
and after immediately installing the hotfix, we have gone two straight
days
without an issue - something that hasn't occurred since late May!
Once again, thank you for taking the time to provide me with this
information!
Louise