469,909 Members | 1,742 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,909 developers. It's quick & easy.

Access 2003 Corruption

I've got a system that's been corrupting repeatedly recently and I'm
having trouble tracking down the cause. I've done as much reading as I
can so far, but am starting to get lost as most of the common
causes/solutions don't seem to apply.

Particulars:
Access 97 recently converted to 2003 (started life in 2.0). Corruption
did start after the 2003 upgrade, which is in prep for converting to
SQL Server.

Up to 10 users in at once, not all doing the same things.

Backend on Small Business Server, Frontends on XP

No network issues, new switch, wiring checked

Purchasing System (Items, POs, Invoices)

Sometimes missing PO records. Sometimes Items table refuses to load
(form shows white box where the subform datasheet would be). Items
missing or either showing as Chinese characters or all pound signs
(#####). Errors most often pop up when Users entering or modifying Item
data. Items table had up to 58,000 records, now down to 34,000.

System set for "No Locks" and "Open using record-level locking".

File locks on server for ldb file show 4/6/8/10/12, etc when multiple
users connecting, even if just sitting on the Menu page. Single user
shows 0.

Some users connecting via SBS Remote Access from outside the office,
but remote controlling machines inside.

All recordsets closed once finished.

Hidden form bound to a single record table opens first.

Was an older, unused table with no key that had been getting
duplicated. Had 949,000 records before found and deleted. System
repaired and compacted after removal.

Data imported into a clean mdb.

Still corrupting. Just got an email from a user. Got the "another user
made changes to the record, do you want to save"? message, then the
system crashed (item datasheet missing, showed white).

More detail (while trying to post this it happened again):

After using JetCompact, there was this in the MySysCompactErrors table

ErrorCode ErrorDescription ErrorRecid ErrorTable
-1003 Invalid argument. ITEM

and there was a ##### record in the items table I deleted

What am I missing? This is getting really frustrating for me, much less
the poor users. This is now an every day thing.

Jason
Ja***********@gmail.com

Nov 13 '05 #1
3 1442
Jason,
I found these links helpful while trying to solve a similar problem.
Though it sounds like you are being really thorough.

Keep us posted...

Good luck,
Jim

http://members.iinet.net.au/~allenbrowne/ser-25.html
http://www.granite.ab.ca/access/corr...sesoplocks.htm

Nov 13 '05 #2
Thanks. Actually have already checked those out. Fantastic information,
but I've been slowly ruling out all the "usual suspects". That's why I
posted here.

Jason

Nov 13 '05 #3
One thing I did not see in your list: have you split the front and back end,
and given each user their own copy of the front-end database? If you have
multiple users logging in to the same copy of the frontend or into a
monolithic (un-split) database, you significantly increase your chances of
database corruption.

Larry Linson
Microsoft Access MVP


Nov 13 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

14 posts views Thread by JK Peck | last post: by
26 posts views Thread by jamesbeswick | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.