Hi,
I am getting the error "The microsoft jet database engine stopped the process because you and another user are attempting to change the same data at the same time." It happens when I try to delete one row from a table.
This is my scenario. I am testing a certain situation, so I use a form to add a record, then I go into the table via a query, and select the row to delete it. When I do so, I get the above message. I could have sworn that it let me do the delete earlier today. But I have been getting this message on and off during my testing today.
I am the only user, so I know no other user is locking the record. Could I have locked it when I did an Insert from my form? I have read lots of threads regarding this error, but none seem to apply. I did a compact and repair of the db, but it did not help. I exited Access and got back in, but still no good. All else seems to work fine, except the delete of this one record.
I am running SQL server on my laptop (MSDE), with linked tables, from front end to back end.
Any suggestions?
Thanks,
Lori
I am getting the error "The microsoft jet database engine stopped the process because you and another user are attempting to change the same data at the same time." It happens when I try to delete one row from a table.
This is my scenario. I am testing a certain situation, so I use a form to add a record, then I go into the table via a query, and select the row to delete it. When I do so, I get the above message. I could have sworn that it let me do the delete earlier today. But I have been getting this message on and off during my testing today.
I am the only user, so I know no other user is locking the record. Could I have locked it when I did an Insert from my form? I have read lots of threads regarding this error, but none seem to apply. I did a compact and repair of the db, but it did not help. I exited Access and got back in, but still no good. All else seems to work fine, except the delete of this one record.
I am running SQL server on my laptop (MSDE), with linked tables, from front end to back end.
Any suggestions?
Thanks,
Lori