Access 2000 Forms with Linked Tables to Microsoft SQL Server

[Rick Edison]

I have a Sql table linked into Access 2000 where we use Access as the
front end to our SQL server. I have a table that has been imported
from a previous version of Access. I have created a form with a combo
box to find records on in my table. The form works perfectly on old
data in the same table. When I use the form to find recently added
records and make a change and move to a new record by selecting new
text in the combo box, I get an error that says Write Conflict. The
record has been changed by another user since you started editing it.
If you save the record you will overwrite the changes the other user
made.

I know for a fact, I am the only user. When I debug my code I see
Private Sub Combo76_AfterUpdate()
' Find the record that matches the control.
Dim rs As Object

Set rs = Me.Recordset.Clone
rs.FindFirst "[Id] = " & Str(Nz(Me![Combo76], 0))
If Not rs.EOF Then Me.Bookmark = rs.Bookmark
End Sub

Where Me.Bookmark = rs.Bookmark is highlighted.

This code works for older records but not new ones.

I have recreated the Id field which is the primary key for the table
and still no help.

Looking for suggestions.... Thanks in advance.

[DCM Fan]

Somewhere in that table is a BIT field w/o a value...here's what you need to
do:

1) Run an UPDATE query, setting all NULL bit fields to 0.

2) On the SQL Server side, set a default value of 0 for the BIT fields. (or, on
the Access side, make sure you provide the value)

[Rick Edison]

dc****@aol.comSPNOAM (DCM Fan) wrote in message news:<20***************************@mb-m16.aol.com>...

Somewhere in that table is a BIT field w/o a value...here's what you need to
do:

1) Run an UPDATE query, setting all NULL bit fields to 0.

2) On the SQL Server side, set a default value of 0 for the BIT fields. (or, on
the Access side, make sure you provide the value)

I just had to reply to say that it worked perfectly! I don't know how
you linked that issue to the problem unless you had the same problem
once. But thanks again.

Best regards... Rick

[DCM Fan]

<<I just had to reply to say that it worked perfectly! I don't know how
you linked that issue to the problem unless you had the same problem
once. But thanks again.>>

Oh yes, I had the problem before...not in your context exactly...but the
symptoms were the same: new records behaving like they're in perpetual lock
mode.

After spending a few hours on solving the problem, I whittled it down to the
bit fields, then I searched MS KB, and got this:

http://support.microsoft.com/default...b;EN-US;280730