Networks

Ask something
Discussion Locked

Write conflict with SQL 7 after import

0 helpful
4 replies

by ajd

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have a database on SQL Server 7.0 and I am using an Access 2000 front end.
In Access 2000, I wrote an append query to import data from an Exchange 5.5 mailbox. The query runs OK and all the fields are imported, but when I try to edit the importedrecords in Access, I get a "Write conflict" error and the record cannot be edited.
Earlier records that were not imported in this way can be edited without error in the same table.
How do I free up the newly imported records for editing?

4 replies

by ajd

Further info: the locked records can be successfully edited via another update query or by using SQL Enterprise Manager. It is only by using the Access form that the "Write Conflict" is generated.

by saratogapete

AJD -

You goaded me into an attempted response by selecting my last answer! (Thanks for the selection.)

First thing I would want to know is what kind of login & security you in place on SQL Server.

Second thing, when you say that you can'tedit the row, how are you trying to do the edit? I know that you are using Access but are you using a linked table or a query? A Form? Or are you actually importing into an Access table back from SQL Server.

I'm guessing that SQL Server things that the Access connection has one set of rights but when you are trying the edit you are being recognized with a different set of rights. SQL Server is kind of particular as to your login since there is usually a set of rights to each ID.

by ajd

Thanks for your help, but I figured it out eventually: I had upsized a table that had null values in a bit field. This caused SQL to lock the records.

This discussion is closed to new replies.