>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.