Every time I try to add or change some fields in a record I get the message that the record is opened by another user but there definately is no one else in the database.
Thank you, the Yes/No field which is a bit data type in SQL Server is probably causing the problem. Normally, if this is allowed to be NULL on the sql server side it will not map cleanly through ODBC and the ODBC provider will pick this field up as being changed even though it was not. The are a number of ways to fix, one way is to add a timestamp data type to the sql server table. Sql server will send this back as a hidden field on the resultset to Access and ODBC will use this field as the primary key for update purposes and ignore the mapping of the bit data type. Another way is to make sure this field does not allow null and defaults to 0 (No) on the sql server side. You could write an update query to set these to zero in the existing data. There are other possibilities but you might want to explore this as the problem.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.