Well, I have to admit, I am a little surprised that the programmer has to handle the maintenance of locks on the data. I thought that one of the attractive features of an SQL system was that it took care of all that stuff for you (Even though I something told me it couldn't handle all of it).

So, it appears that it is not possible to allow a client to modify data accessed through SQL unless that client software was written specifically to access that particular data.




>>Well, I haven't really begun with any particular SQL software yet. Just thinking about things. Maybe it is too soon to think of such things ?
>>
>
>Oh, its never too soon. If you are considering a server based solution, (MS SQL Server, PostgreSQL, Oracle, whatever...) one way to handle record locks is with a table dedicated to that purpose. IOW, you can have a table called 'locks' with just a few fields: name of table being locked, the primary key of the record being locked, user id, and perhaps a time stamp. This method does not require adding any fields to your tables.
>
>HTH,