I think that I may have figured it out but thought that I would pass my find along so that someone else might benefit.

For the particular apps that I was having the problem with I found that the procedure that was doing the actual "DO FORM" command was running the form name using macro substitution. I have a property on this particular class that contains the name of the form that I want to run. Whenever I subclassed (overwrote) this method in my code and then just did the "DO FORM XXXX" the problem went away. I guess this means that even if you have a form included in the project it doesn't necessarily mean that it is going to compile it into the APP or EXE.

If you gave this some thought earlier I appreciate it. If you have any other suggestions or comments please feel free to respond.

Dave :-)