>>Likely a question with a simple answer, but I haven't yet found the answer: must the libraries for objects created at run time be distributed with the app? To create my application object from the startup program, there is obviously code that points to the vcx (on my workstation drive) to get the class from. This code creates an error when running the executable from the server because my drive is obviously not accessible from the server. Once past the 'invalid path' error, the app runs fine. My application object is the only instance created at run time, everything else in the program is compiled into the executable. How is this done?
>
>I assume you are building your application from a project, for starters. Anything included in the project, including visual class libraries, need not be distributed with the executable.
>
>What does your SET PATH TO statement look like? Is there a path or drive on it that cannot be resolved from the running machine?
>
>Also, you mentioned that the drive cannot be accessed from the server. Are you trying to run the application from a server? Windows applications need Registry modification (including indications of paths) to run properly. This implies a proper application installation on the machine that is running the program.

I guess the problem might be originated from including path into SET CLASSLIB.
Issue
SET CLASSLIB TO MyVcx ADDITIVE
without path (just library name) and it should work Ok without separate distributing.