Write Conflict Error MS Access 2003

[gazsharpe101]

Hi everyone,

I am doing some work on my company's database. It is a MS Access 2003 front-end with an SQL back-end.

Recently, I have asked the database administrator to add some new fields to an existing table and two of them are yes/no fields. When I have tried to update these fields, it comes up with a 'Write Conflict' error message and I can only choose 'Copy to clipboard' or 'Drop changes'. But either way, my changes do not get saved.

I have found that the error occurs when I refresh the table links to add the new fields and then try to save over just the old fields and not even trying to add anything into the new fields. Two of the fields are yes/no but they have a default value of 0 and I'm not sure what is causing my error. I read that it may be due to these yes/no fields having no default values so I thought I would mention it incase anyone may have suggested that to be the reason for my error message.

Any help is appreciated.

Thanks.
Gareth.

[RedSon]

We have an Access forum for a reason...please use it.

Moved from Misc.

[gazsharpe101]

Sorry about that I couldn't find it earlier and I posted this in a rush.

Thanks.
Gareth.

[Jim Doherty]

Access will try to give SQL server a null value for bit fields where there is no default defined and of course a bit can never be null it must be true or false. And yes...I am aware that that is something that raises its head from time to time as an issue for the unsuspecting user/developer with no explanation readily to hand from either Access or indeed SQL Server leaving you having to scour the web seeking the answer.

You merely need to insure your defaults are there for bit field one way or the other true or false. Take care also in that SQL server only accepts 1 as representative of true not minus 1 (-1) again the Access interpretation of true designed (it seems) to send the developer/user into an general frenzy of seeking why there is this difference between systems that are meant to seemlessly talk to one another. :P :)

To give you a pointer on this here is an MS link that describes the issue

http://support.microsoft.com/kb/280730

Regards

Jim :)