Update Table

M

Marius

Hi all
Recently I have added a new field (True/False Field) to an existing table in
SQL Server, since then every OpenRecordset with Edit and then update propmpt
me with the message
"Microsoft Jet database engine stopped the process because you and another
user are attempting to change the same data at the same time"

I get the same message when I open the table directly using Access as a
linked table, and try to update the record directly.

When I change the OpenRecordset to RunSql, it runs with no problem.

I will appreciate any suggestion.
 
R

Rick Brandt

Marius said:
Hi all
Recently I have added a new field (True/False Field) to an existing
table in SQL Server, since then every OpenRecordset with Edit and
then update propmpt me with the message
"Microsoft Jet database engine stopped the process because you and
another user are attempting to change the same data at the same time"

I get the same message when I open the table directly using Access as
a linked table, and try to update the record directly.

When I change the OpenRecordset to RunSql, it runs with no problem.

I will appreciate any suggestion.

Bit fields in SQL Server need to be set to a default and NOT NULL to work
properly with Access. If that doesn't correct the problem try adding a
Timestamp field to the table.
 
O

Ofer

I had this problems few times, my work DBA doesn't allow me adding a data
stamp saying that it cause alot of problem to the database.
I had to change the field type from True/False to Small int, and the problem
was solved.
I still needed to run few changs in the code, for some reason Access didn't
recognize 1 as True in this field type.

Good luck
 
Top