>>>>I guess the problem arises when one of the "remote users" uses the program? By remote, I mean they are connected to this server in some way, >but they don't use the keyboard and monitor of the server. This connection should be via for instance Remote Desktop, which means that the >program itself runs on the server, on the local machine you "remote control" this program on the server. If you don't understand what I mean, >Google on Remote Desktop. Remote Desktop typically comes with Windows, as far as I know.
>>>
>>>>Connecting to a server via some unreliable network is a terrible idea with VFP, it's begging for problems.
>>>
>>>>NB! I write "for instance" since there are other programs out there which does the same as Remote Desktop.
>>>
>>>Yeah, Tore. "problem arises when one of the 'remote users' uses the program"
>>>
>>>Many years ago I started installing my Clipper programs on the local computer. So only data "travel" through wire (or that's what I wanted to do) now I'm doing the same with my VFP net systems. I install program locally and working folder is remote. (remote means 10 meters at most )
>>>
>>>The program itself doesn't run on the server I understand.
>>>
>>>Forget about remote desktop, I use a program for that and only for technical support.
>>>
>>>What is "NB!??? (a few month ago a friend here wrote me "ASAP" and I didn't know what he meant... )
>>>
>>>What do you call an "unreliable network"? Hardware, software? Hardware of course, but software too?
>>>
>>>I need to believe "Work net" of W 7 is not an "unreliable network" cause I'm almost launching a new system for 6 (six) workstations in a supermarket and that would really be a great problem.
>>>
>>>Thank you.
>>
>>NB! Means Nota Bene, which is an international expression, something like "Also note this".
>>
>>With realiable network I mean just that! If something in a network is not working 100%, it's unreliable. A bad network card, a bad cable, a bad hub, router, switch. Or software. Or bad power, which is why an UPS is not a luxury, it's a minimum requirement! Anything related to the network connection. "No connection is stronger than the weakest link".
>>
>>If you for instance unplug a network cable just for a millisecond at the "right" moment, you may get index corruption.
>>
>>Also a bad user who turns the PC off without exiting the programs, should be fired and/or billed immediately.
>
>Absolutely!
>
>Either you have a truly reliable network or you need to run everything on the server (and have a reliable server!!).
>
>The only way around this is to get away from the DBFs and switch to a database server (SQL Server for example). It takes some work to convert, but after that network issues will not result in corrupted tables/indexes/memos etc. You still need a reliable server to host the database, but the database will protect itself from network issues.

And let us not forget that SMB2 protocol will spells trouble for DBF files (as well as other "desktop" database formats like Access). Although at present you might not have configuration that causes problem (Windows Server 2003 or later combined with workstation w/ Vista or later -- I don't recall if peer-to-peer using Vista has same issue or not, but I probably would guess that you'll probably have the problem).