>>Hi all,
>>
>>we've a VFP call system that is in place a long while with a customer. It works fine but as time has gone on the customer has required more functionality and also more ways to access the information. We not have another VFP application access the data and a website too. Recently we have added a new connectivity option to a mobile solution and this is where the issue is coming from. The interaction with the mobile solution involves adding a record in a table where the unique key is held in a different table. The interaction is written in .NET while the back end if VFP and the unique key table is in VFP too. I need to lock the table, get the next number and then unlocl the table. Adding a stored procedure to the VFP database may not be viable, are there any other ways to lock and unlock a record in .NET? Or any other solutions anyone can suggest.
>>
>>~M
>Do you need to lock the table or lock the row?
>If you need to lock the row, you can do it logically by adding a column that says that the row is in use and setting it and clearing it.
Thanks Bill,
I need to lock the row. Good idea about adding an extra column but I think that would still leave the possibility of different updating programs (4 in total) getting a duplicate number.
~M