I NEED HELP

[John W. Vinson]

I read this topic and I have a similar problem.
The diference being that I am using SQL 2005 Server and the table is linked
by ODBC to an Access 207 MDB.
If I open the Access database and the attached table, I can delete records
without any problem. However, if I add any recor or edit any record, I cannot
edit or delete records without getting the 3197 error. Any Ideas on this?
Thank you
Fernando

Is there a Timestamp field (it's actually a binary string and has nothing to
do with the date or time) in the backend table? That seems to help greatly
with problems like this.

Also the backend table should have a Primary Key and the linked table should
be aware of what that field is.

John W. Vinson [MVP]

 

[Fernando Oliveira]

Thank you for your reply.

In the meantime, I found the problem.
Just to clarify: the table has a primary key and a timestamp field (I always
add timestamp).
The problem is something stupid: the table has a Bit field which cannot have
null values but no default value. When I open the table in Access, the field
shows "0" and not "null".
The stupid part is that if I insert a record instead of giving the message
that the field cannot have a null vale, the record was still saved but I
could not edit or delete it anymore in Access. I noticed this when I opened
the table in SQL Management Studio and the field was showing "null".
Since I added the False default value, the problem was fixed.

Thank you once again for your concern.
Best regards,
Fernando