krd0829
asked on
Access 2000 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.
I am running Access 2000 for my forms, reports, queries etc and pull in linked tables from SQL server to store the data. I currently have two forms in a database that are saving the recordsets in a SQL table. The data is saving fine, but when I try to delete a record out of the SQL table from within access it gives me the error message The Microsoft Jet database engine stopped the process because you and another user are attempting to change the same data at the same time. I have other forms and SQL tables inside this database that are working fine. The only time I see the error is when I try to delete from within Access. I can log on to the table inside of SQL and delete fine. No one is currenly using this side of the database or saving into this table so I know there isn't a user confict. Any thoughts on how to fix the problem would be much appreciated.
If you close all your forms/reports etc, can you then delete the record?
Can you delete a record on the form?
Can you delete a record on the form?
ASKER
I can update the table fine but not the records saved from either of the forms. I can open the table inside the database and add new records directly into the table and delete those fine enough, but I cannot edit or delete the records saved from either of the forms. That is when the error occurs. I had already included a timestamp field, and updated the linked table. I even removed it and reimported the table from SQL, but am still having problems.
OK - and you don't have any Bit fields which allow Null and have no default value?
<OK - and you don't have any Bit fields which allow Null and have no default value>
My next question ... just had a battle with this one ...
My next question ... just had a battle with this one ...
ASKER
I have 6 bit values that allow null values, but none of them are being used from inside the form. They were left overs from when the table was used inside a different database. They auto default to 0.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Booled? What happened with my fingers there? :-s
Boolean, naturally.
Boolean, naturally.
It manages well enough - but if you include a TimeStamp column in your SQL Server table then it allows an immediate determination of the record's state by the local engine.
Hence you should be able to perform your deletion without the virtual conflict.
(When you've altered the schema of the server table you should always then refresh / relink the table in your Access FE).
Cheers.