Corrupted memo field

I support a relatively large Access 97 application which is installed at 2 of our customers.  The following problem only occurs on on of them:

The main table (Orders) has one memo field.  In the past month or so, I've run into a problem where the memo field on a specific record will go corrupt, and display "#error" in the place where the data should be.  All the other fields on that record appear OK.

When this happens, you can't compact the database.  If you do, it says "The jet database engine stopped this process because you and another user are attempting to edit the same data at the same time".   If I run a repair of the database, it says "Repaired successfully", but the problem still exists.

So, the only way I've been able to resolve the problem is the write a little function to loop through all 130,000 records to find the corrupted one.  Then I delete it, and the database compacts just fine.

This is happening at the rate of about 2-3 records per week.  Not tragic, but a real nuisance.

So...
1.  Is there a way to solve the problem without deleting the record?

2.  How can I prevent this from occuring?

More info:
Server:       Novell 4.1
Workstations: Windows 95, Pentium, 32 MB RAM
Database size: ~75 Meg


LVL 3
slpatchesAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

cymbolicCommented:
Have you tried deleting your .LDB file, then compacting.  It may be your locks file is bad.  
0
slpatchesAuthor Commented:
Yes.  I've tried that.  Same result.
0
TrygveCommented:
Try setting Default Record Locking to Edited record. It seems like the this default is set to No Locks by default. This will prevent two users from working on the same record and this might be the reason for your problem.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
slpatchesAuthor Commented:
Thanks. I'll try that.  When I know the results, I'll grade the question.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.