>Then what could it be? He was using an APP file rather than and EXE and he had the forms on the same path way.

The apps are "launched" from an executable. The only problems I've had are users without proper configuration. I wrote a VBScript file to take care of that problem.

There's a main procedure file, that's marked as excluded in the app file, but included in the executable. All the apps contain it and if the executable is updated, all the apps automatically "inherit" (for want of a better word) the changes.

>>Probably not. I've been using a single executable to start applications on a network on a file server for 10+ years without a problem.