Record Lock Error Message

[abetown3]

Hello. I'm having data entry problems with a database I've created. I'm working in Access 2003 although the db was created in 2000 format. When data entry first began the db allowed for multiple users without locking anyone out. At the most - 4-5 people are doing entry at once. Data entry continued fine for several weeks - until our IT staff begun moving files around to different servers. Now when more than one person tries to do data entry they get the error message: "could not update currently locked." Everytime the system locks up - the record being entered is deleted. Very frustrating for data entry people.

I've tested everything I can think of to fix the problem. I checked to see if the same record was being accessed when the error was received, but that was not the case. I read that the problem of records locking had been changed with the 2003 version so I made a copy of the db and reformatted it to 2003. That didn't work.

I hope someone has some ideas about what's going on. It's stumped me and my office's IT staff.

Thanks for any help you can offer.

[MMcCarthy]

You have posted in the Articles section. I am moving this question to the Access forum.

ADMIN

[abetown3]

You have posted in the Articles section. I am moving this question to the Access forum.

ADMIN

Sorry about that. I need to watch more closely where I'm at.

[NeoPa]

Sorry about that. I need to watch more closely where I'm at.

You're fine AbeTown. We're getting that organised better soon so that members won't find it so easy to get wrong.
Your question, on the other hand, may be a problem. It's not clear (at least to me) why it would behave that way from what you posted. Certainly, the ability to share access to a database depends very heavily on settings (Tools / Options) which are set on a per installation (PC) basis, but the same PCs are still in use (or so I gather from your question).
The locking features are what I would look at, but if they're already ok then I don't know :(

[abetown3]

You're fine AbeTown. We're getting that organised better soon so that members won't find it so easy to get wrong.
Your question, on the other hand, may be a problem. It's not clear (at least to me) why it would behave that way from what you posted. Certainly, the ability to share access to a database depends very heavily on settings (Tools / Options) which are set on a per installation (PC) basis, but the same PCs are still in use (or so I gather from your question).
The locking features are what I would look at, but if they're already ok then I don't know :(

Thanks for your response. I think this might be one of the great db mysteries. I've checked everything I can think of and our IT department has tried several fixes. Nothing seems to work. It's a very frustrating problem for those trying to do data entry. I'm going to keep working on it.

[NeoPa]

I'm afraid it's also a difficult one to understand from afar.
Keep posting if you think of anything or want clarification on anything. I'm afraid we can't promise much in the way of results though, unless we get lucky.
Good luck with it.

[MMcCarthy]

Hello. I'm having data entry problems with a database I've created. I'm working in Access 2003 although the db was created in 2000 format. When data entry first began the db allowed for multiple users without locking anyone out. At the most - 4-5 people are doing entry at once. Data entry continued fine for several weeks - until our IT staff begun moving files around to different servers. Now when more than one person tries to do data entry they get the error message: "could not update currently locked." Everytime the system locks up - the record being entered is deleted. Very frustrating for data entry people.

I've tested everything I can think of to fix the problem. I checked to see if the same record was being accessed when the error was received, but that was not the case. I read that the problem of records locking had been changed with the 2003 version so I made a copy of the db and reformatted it to 2003. That didn't work.

I hope someone has some ideas about what's going on. It's stumped me and my office's IT staff.

Thanks for any help you can offer.

1. In Tools - Options for all the installations of Access using this database set the Default Record Locking to Edited Record.

2. Check the tables for corrupt data. The easiest way to do this is to try to import the the tables to another database and see if any errors occur.

[abetown3]

1. In Tools - Options for all the installations of Access using this database set the Default Record Locking to Edited Record.

2. Check the tables for corrupt data. The easiest way to do this is to try to import the the tables to another database and see if any errors occur.

Thank you for your suggestions. I'm going to give them a try and will report back.

[abetown3]

Thank you for your suggestions. I'm going to give them a try and will report back.

Thanks for all of your help and suggestions. I've tried everything and I'm still having the locked records problem. I guess it's "just one of those computer things". I'll keep trying.

[Boxcar74]

I don't know if this help's but I was recentally getting similar locking errors.

When my db was moved to a different server where I had read only rights to the server.
So make sure every one has read/write status.

Then (after I got read/write rights) I got a similar message when I'd have a linked Excel Spreadsheets open and the DB open at the same time. The records were locked when Excel was querying it.

I do a compact and repair with mine often and obviously it can't be updated then.

Most of the time when I get errors like this I copy the DB to my computer and see if happens there. If it doesn't happen there then the DB is probably working OK.

I hope any of this helps.

[NeoPa]

That copying to the local PC idea is a good one BoxCar :)

[Rory_Small]

Wow - I didn't think anyone had this problem! I am working a small to mid sized database (somewhere in the 40mb range). It is a constantly updated database (started off as a bunch of seperate DB's in the 90's). Anyways, updated it all the way through to Access 2000 (yes, I know it's 2007). We have approx 25 users and have never had any issues until one of the users migrated to 2003.

I have it set up as a front end / back end on a server (only the actual program is run on the local PC). Anyways, I have the same record locking error only with one user (although about 6 users have migrated to 2003).

[NeoPa]

You don't say what results you got when you tried all the ideas in the thread so far.