>There was discussion about that in the Thread #553005. Looks like you can use the third parameter in the NEWOBJECT function for .VCX based classes only.

Sergey,

Ok, reread the function and yes you're right about the third parameter. It does state that in a not so obvisious way... IMO.

Could someone please tell me why the third parameter of the NEWOBJECT() function can't be used the for a (.prg) as well as the (.vcx)? Is there some problem with the SET PROCEDURE that doesn't make this very easy to implement? I mean there must be a reason... How do we get this fixed? Is there some kind of system in place where developers can rank things they'd like changed or adjusted? It would be of great benefit to me.

Don't get me wrong I love FoxPro. ;)

thanks for your help

BTW, here's how the documentation reads:

NEWOBJECT(cClassName, cModule, cInApplication)
cClassName
Specifies the class or object from which the new class or object is created.

cModule
Specifies a .vcx visual class library or Visual FoxPro program (.prg, .mpr, .app, .exe, and so on) containing the class or object specified with cClassName. The default is a .vcx visual class library; you must include an extension if you specify a program.

cInApplication
Specifies the Visual FoxPro application (.exe, or .app) containing the .vcx visual class library you specify with cClassLibName. You must include an extension for the application. CInApplication is ignored if cModule is omitted, or if cInApplication is the empty string or the null value.

Remarks
NEWOBJECT( ) makes it possible for you to create a new class or object without opening a .vcx visual class library or procedure file.

>
>>Tried that before I started ranting.
>>
>>

>>loService = NEWOBJECT('AppService_manager','main_servicemanager.fxp','ServiceManager.exe')
>>

>>
>>produces the same error, even with the prg extension - "File 'main_servicemanager.prg' does not exist."
>>
>>>Try to change .PRG to .FXP
>>>
>< snip >