I am attempting to upsize my systems to SQL Server 2000. I have migrated a few tables over and made sure that they have Primary Keys setup. I have linked them into an Access 2002 mdb file and can open, add, delete, modify while in the datasheet view but when I create a bound form to the data, even a single table form, I receive a Write Conflict error when I attempt to change the data. This happens when I use simple automation. I have a dblclk property on a field that does this

Me![Desired Quantity] = Me![Quantity
Me.Refres

but when the refresh is executed, I get the error

The form properties for recordset are "dynaset" and Record locks are set to "edited record

Any idea what I am doing wron

[quoted text, click to view]
a few tables over and made sure that they have Primary Keys setup. I have
linked them into an Access 2002 mdb file and can open, add, delete, modify
while in the datasheet view but when I create a bound form to the data, even
a single table form, I receive a Write Conflict error when I attempt to
change the data. This happens when I use simple automation. I have a dblclk
property on a field that does this:
[quoted text, click to view]

Using bound forms are never scalable when you move the data from Access to
SQL Server. Use unbound forms and manage the data retrievel/updates with
code. An excellent book on this:
Microsoft Access Developer's Guide to SQL Server
by Andy Baron & Mary Chipman
http://www.amazon.com/exec/obidos/tg/detail/-/0672319446/qid=1083085036/sr=1
-2/ref=sr_1_2/002-0476042-9237655?v=glance&s=books

Steve