Updating field goes to wrong record

[chrismalan]

This is an old database, but a new problem. Updating a field in the form loads a new primary key to the form. That makes it appear that the update will go to the wrong record. Closing the form and opening it again makes this problem disappear for a while. The form is on a networked computer and the back end is on a SBS2003 on the same local network.

Any idea what is going on? To me the answer is just one thing; Microsoft.

[RuralGuy]

Are you saying just editing one field on your form forces your form to change records?

[chrismalan]

Are you saying just editing one field on your form forces your form to change records?

Yes, that's exactly it. Any idea why this happens?

[RuralGuy]

Is this with *any* control on your form? Do you have any AfterUpdate event code running? How about a Timer Event somewhere?

[chrismalan]

Is this with *any* control on your form? Do you have any AfterUpdate event code running? How about a Timer Event somewhere?

It's with any field. And there are no after update events running. The closing of the form and things working again afterwards makes me think the problem is with memory. Not amount, as the one machine has 4GB, but something gets corrupted somewhere and the reference to this corrupted value is deleted when the form is closed.

[RuralGuy]

At this point I would *import* everything into a new, fresh db and see if the problem follows: http://www.btabdevelopment.com/ts/impnew

[chrismalan]

At this point I would *import* everything into a new, fresh db and see if the problem follows: http://www.btabdevelopment.com/ts/impnew

Thanks. I compacted and repaired the back-end and unset the auto-correct option on it. So far so good. If it does it again I'll do the import thing. Thanks again. That was quick.

[RuralGuy]

The import only takes a minute or so but if you are satisfied then go ahead and use the Thread Tools and mark this thread as Solved.