>Any advice on the fastest & easiest way to accomplish this? Also the client is considering moving to a browser based system using SQL Server 2000 as the back end for users on their intranet. Would it be easier to migrate directly? Thanks.
>
>-Mari
>
>P.S. I'm presently working on another project using ASP.net in C#. The main portion of this app was originally written in VB6 so I have some current experience doing this (I also left a message under VFP6 & .Net)

I don't know much about browser and C/S.

For a networked system, several frameworks already have built-in support. If you manage your own framework, you have to make sure the tables are opened shared: set exclusive off.

Also, it is convenient to use buffering. Most programmers prefer optimistic buffering.

You should also use private datasessions. This way, you can open several copies of each form - or open different forms that access the same tables. This will not only give a great user-interface, but it will also let you test access to the table from several forms - this should be quite similar to accessing from different machines.

Records locks or file locks are seldom used, nowadays. When you use buffering, VFP does all the required locking automatically.

HTH,

Hilmar.