Sure.
I remember, there was a bug for VCX class libraries - when class library from another EXE/APP is already loaded in the memory (you can check if VCX exists using SET('CLASSLIB')), NewObject generate error. Probably the same situation is with NewObject() for program files. Just look in SET('PROCEDURE') list of procedure and see if your app or program from that app is not in that list. If yes, use "release procedure ..." command to clear it from memory. After that try again:
NEWOBJECT("cls2","ClassDef2.PRG","TESTCLS.APP")
Above should work accordingly to help.
>>Then
>>
>>o2=NEWOBJECT("cls2","ClassDef2","TESTCLS.APP") && no extension
>>
>With no extension, vcx is default extension.
>
>MarianL
Vlad Grynchyshyn, Project Manager, MCP
vgryn@yahoo.comICQ #10709245
The professional level of programmer could be determined by level of stupidity of his/her bugs
It is not appropriate to say that question is "foolish". There could be only foolish answers. Everybody passed period of time when knows nothing about something.
