In addition to Olaf's comments: To work on a LAN you basically need to do the following.
Instead of opening files in exclusive mode, you have to open them shared.
A mistake that is sometimes made is to PACK every time a DELETE is done. This is unacceptable for a multiuser system. Just SET DELETED ON to hide deleted records. PACK might be done once a month, as a maintenance task.
To access data, access the tables directly, or use local views.
I recommend optimistic buffering. In case of an update conflict (two users change the same record, almost at the same time), the second user who saves will not be able to save data (using default properties of TableUpdate()), and will simply have to undo and start over again.
>I am upgrading a system written in old versions of Foxpro for windows. I wanted to present a new system that will make use of the LAN.
>
>My idea is to have a desktop computer that will act as a data server of several workstations. I wanted to have a submit button in my webpage where data from the workstations will be saved in the data server. When printing reports, my visual foxpro program will simply retrieve data from the data server and print it. I don't want any data to be saved in the workstations.
>
>I wonder now what issues shall I need to consider when creating this system. I know VFP can handle multi-users but will this make my system run slower? I have only about 50 users running 5 different systems. All data from these system will ideally be in one desktop computer.
>
>I know that I can make a webpage using VFP, although I'm not sure HOW.
>
>Please advise me.
>
>TIA.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
