asked on

Write conflict when editing a linked table - linked to SQL Server 2000

I have an Access database where the tables are linked to a SQL Server 2000 database. In one of the tables if I add or modify a record within Access (either via the table or a form view) I get a Write Conflict message (see attached). The record can be modified/added through SQL with no problem. I know that this error is because the SQL table has some fields of data type 'bit', but I don't know why this should be a problem or how to fix it, (other than to take the 'bit' fields out).

accesserror.jpg

Scott McDaniel (EE MVE )

Why would you think this has anything to do with a Bit datatype field? Write conflicts can occur for several reasons and are not dependent on any particular datatype. While you may be having an issue with a Bit field, I have several SQL Server tables with Bit fields and can update them.

Did you recently upsize this database to SQL Server? If so, then Access uses the Bit datatype for the YesNo field ... in most cases, however, this translates over perfectly well.

The error you're getting typically means that you or another user has the same table/record open and have 'dirtied' the same record. This can occur when if you have a Form opened to that record and have made ANY change to the data - either through the interface or through code - and you then open the Table that form is built from and try to modify the same record.

This can also occur at the form level if you use VBA/SQL to try and update the same record as you're viewing on the form.

Robijef

ASKER

Hi,
Well, because if I delete the bit fields then I can update no problem.
I didn't upsize, I created the The SQL tables independantly and linked them in Access, and there is definitely no other user using this database.
I have had the same issue on other databases linked to SQL.
Regards, Jeff

Scott McDaniel (EE MVE )

Then I'd presume that your Access application isn't properly setup. As I mention, I have several Access Frontends to SQL Server backends via linked tables, and I use the Bit datatype with no problems.

Any Triggers on the tables? Constraints?

Robijef

ASKER

Yes, I also have other applications where this works OK - but they would be Access 2000 rather than 2003.
I'm sure the problem is Access/SQL setup also, but exactly what - I don't know. There are no triggers or constraints on the SQL tables.
Also, the problem isn't constrained to just my PC which suggests its not an Office setup issue so re-installing office wouldn't make any difference.
Very weird I know, but when did I ever get a straightforward problem!!

ASKER CERTIFIED SOLUTION

perezjos

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Robijef

ASKER

Worked fine

animallover

Thank you, thank you! I searched all over for a solution and once again was able to find it here. I had 4 bit fields and once I set them all to default of 0 i was able to edit new records in my table. I did have to delete and relink my table through ODBC in Access to make it possible.

You saved my day!