>>Do you hard code pathing inside your code? Do you say do form d:\blah\somefolder\yourscreen.scx in the code in your production exe? If so, vfp is attempting to look there for the form. Inside your exe, your code does not need such pathing. You can also use sys(2450,1) to force it to look in the exe first. You only need a path to the form at design time during design-time testing in the IDE. At runtime, you only need a path to the data folder and possibly image folders. I open all tables at app start. Subsequent USEs inside private data session forms and also subsequent SQL queries benefit. That is because they basically do a USE AGAIN which is fast on an already open table.
>
>Thanks, Mike. No, I don't specify path inside programs. Everything's in one exe (around 13MB total). There's only one PATH statement in config.fpw (made sure it's all valid), and that's it. And yes, I leave most frequently accessed tables USEd at run-time.

I would definitely put the exe on the local machine. It may not be a visible speed improvement, but it all adds up. Also remove quite a number of things from the exe such as graphics. That will speed downloading the exe to the local pc. Put such files in the same local folder as the exe. If you are using the data environment of the screen, vfp stores the full path. I remove those from the .scx. You could also try a local dbc for stored procedures, triggers, referential integrity (anything that is code to execute) and possibly a remote dbc for the tables.

If you can, tell virus scanning software not to scan the vfp temp file locations.