Nadya,

The app files can come down to the desktop as easily as the exes, although you'll only have the file timestamp to check versions. I recently had lots of problems trying to build exes where the classlibs and code were out on the network drive. VFP would throw totally useless File Access Denied errors without telling what file it couldn't compile. Since we've moved to SourceSafe and all work is done on local drives the problem has gone away.

If you are doing a CLEAR ALL, CLOSE ALL and that doesn't free them there's not much you can do. But those two commands can easily destroy your launcher program's environment. So you are stuck between a rock and a hard place.

>Now, let me describe, that we currently have (I don't think, we're going to change it):
>
>All applications (we didn't compile an exe, we compile with app extension) reside on the server. The main application is called JobControl. User enters into the system and then he/she invokes and closes applications. Until he/she invokes an application A, I can recompile it on the server without problem. But if it was once invoked, then closed, I can not recompile it anymore, until users completely get out of the whole system. As I said, all applications use common classlibraries. I think, then application is closed, it didn't properly close referenced classlibs, so they're still in the memory. That's the reason, I can not recompile an application, even if nobody uses it at this time.
>
>My question is: is it possible make a proper cleanup and allow to recompile application, after this application was closed, but the main system is still running? If not, we have to finally implement a launcher approach (using any of already available launcher classes in Download section).