I'm sorry if this is a repost, I ran a quick search and didn't really find what I needed. I recently upsized an Access database to an SQL Server. I can access the database fine on multiple computers but there seems to be no locking system in place. Whenever I access the same table from 2 different client computers, they can each edit the form simultaneously which of course leads to errors. I connect to the database through an Access project. I need to keep using Access and was wondering if anyone could tell me how to implement or activate (if that's the case) a locking system that will prevent simultaneous editing. Thanks in advance.

SQL Server locking is much different than Access locking. SQL Server can apply locks at many different levels; row, pages, keys, indexes, tables, and even databases.

You can configure these, and your best bet is to look in the SQL Server Book Online (BOL) and read up on locking. Otherwise, this would be a really long post. :-)

Scott

Check your app after INSERT,UPDATE,DELETE or using COMMIT;
IF not using,You will lock the DB or TABLE or COL until this db system timeout

I think part of the problem is what the definition of "lock" is. It is different in SQL than for FoxPro/Access/Xbase. What the requester appears to want to do is what Oracle calls a "select for update", this feature does not exist in MS-SQL. But you can design it into the schema/application. What they appear to want is if user1 is viewing and editing a record #100, the developer wants to block some other user from retrieving for update the same #100 record. It is not related to field or row or table level locking in the SQL sence. It is to flag the row as someone is editing this row don't touch it till they save their changes (or do a sql update).