record locks problem

[bubbaj_423]

I keep getting an error message on my existing A '97 database that says another user is attempting to change the same data at the same time, even when I'm the only one using the database. I have all users on the "no locks" option, and the weirdest part of this is that the error message always comes up when I either use the "edit/find" function or page through the db and come across one record in particular.

I'm thinking it may be a blip on the disk, but repairing the db using "database utilities" doesn't fix it.

Help!

 

[Mile-O]

Sound like you have the same recordset open twice maybe as a recordsource on a form and through DAO, ADO, or a query, etc.

 

[bubbaj_423]

I can't find any duplicates, but I may not be looking in the right places. I guess I need a little hand-holding.

 

[keith_pyrasoft]

Presumably this happens within a bound form........ is it possible you are accessing fields in the bound recordset from code in a module somewhere via DAO instead of through references to the form?

 

[The_Doc_Man]

I've seen this once before (I think...)

My problem was that the form had some code "before update" to store a date in the underlying record in a way that was not the result of a user action in a date-based control. It was just the fact that the user had touched another element on the same form and the code tried to force that update in, you might say, an audit trail.

I had to change the way it worked. I made the history info into a separate table, then updated it with a simple append operation using recordsets that opened, updated, and closed within the same event routine.

I don't know if the same thing applies to you, but it's the closest experience I've ever had that showed the same symptoms.

 

[IgorB]

Take a look at the shared .ldb file which could be at the same location as your database.
If you do have it then physically delete it.