>By design, you can be in debug mode within Fox or as standalone, as long as the Debug.txt file exists in the directory.

Are you talking about the MetaData table? If debug mode is on, it rebuilds it's tables based off what's included in the project. If it's a standalone, I don't see how it can do this since the project is not available.

>Since the libs never go out of scope in Fox, and do in the executable, I'd suggest doublechecking that the EXE has its own set of path statements executing.

The stub program works in any directory and is not tied to the app's directory other than looking for some constants. The error is coming from the compiled mm app's exe. Both exes work (well if I don't call the other) standalone so I think I'm missing your point. Should I issue a clear all or something after the stub is finished running it's procedures and before I call the mmapp's exe?

In the main prg of the stub exe, I run the stub program by creating a global object, release it when it's finished and simply issue a DO mmapp.exe (the main app). Am I doing it like you do it?

>If the classes are not in the project, they won't be compiled into the app, and need to be included separately.

All of the classes are compiled into the app.

Sorry for all of the questions. I've never done this before and after reading the DEVGUIDE, it seemed rather simple.

Thanks for your response, I'll continue checking...

Chuck