>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.
>
Why not break out the routines already running in your other apps into a new mini COM vfp application, which feeds your webserver ? If you want to stay with the vfp backend IMO the safest way to continue, or when asked to move old vfp apps/routines to new runtimes, my standard approach is to move the data backend to some SQL backend as very first step.

Otherwise chances are really stacked that you will run against some wall via ODBC, if you code against vfp data