quote:
Hi alicejwz,from what you have sent me off-forum, could it be you have a bit field in one of your tables without a default value? That's working in Access, but not in SQL Server.
Cheers,
Frank
It is possible to store NULL in bit field in SQL2000, but Access doesn't like that, and if there is a bit field without default in a database, it is a very likely cause for Write Conflict. Other causes can be more misterius, perhaps linked to missing ServicePack or so.
Hope that helps
PS: Access also doesn't like after-triggers on insert into table.