Does updating a database via a SQL statement without any type of lock (such as the AdLockOptimistic property of the recordset object's update method) pose any problems to the stability of the database??<BR><BR>Thanks.
No, it does not. You will want to use a lock when you open a recordset object and use the .AddNew and .Update methods to add and update rows in your database. When you use the .AddNew/.Update method, you are working with a "copy" of the data, which can go out of date if others work on it, that's why the locking issue is an issue there!<BR><BR>However, if you just use SQL statements, you do not need to worry about locking. SQL Server is advanced enough to make sure that the database remains consistent... :-)