>Thanks for explanation...I'm in kind of a catch 22 at the moment, this will sound kind of funny, I think :)...the main reason I implemented the launch exe to copy main exe to user drive is so we can make frequent updates to server version of main exe, we have many testers and already some users and people always have main exe open. So hence copy to user drive overcomes that problem. But next, we find that we need changes to launch exe frequently (for now, at least) so we had to close that quickly to make updates there too. Soon as we get the launcher set, then we can use DO and/or APP :)

I don't think that it sounds funny at all. Rather it sounds like a well thought out solution to the problem. What I think is funny is that Nick mentions his LAUNCHER.EXE, you mention "need changes to launch exe...", and then there's the name of my FPW framework...LAUNCH.EXE (which runs the app files on the network) :-)