Re: Class Instantiating Problem
From: Carsten Bonde (bonde)
Date: 06/23/04
- Next message: crampe: "Release object in a procedure"
- Previous message: Anders Altberg: "Re: Manuel for ODBC"
- In reply to: Yoganathan Sivaram: "Class Instantiating Problem"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 23 Jun 2004 13:19:20 +0200
Yoganathan,
You could try to exclude the ClasslibB from the project (In the
project-manager, rightclick "ClasslibB" -> "Exclude"). Now you must copy the
VCX-Files to the proper folders along with the .EXE/DLL-File.
Cheers
Carsten
"Yoganathan Sivaram" <ysivaram@remove.this.for.spam.yahoo.com> schrieb im
Newsbeitrag news:ewKgmFGWEHA.1356@TK2MSFTNGP09.phx.gbl...
> I have a DLL project with two classes (Let's say ClassA and ClassB).
>
> From ClassA I want to call a method in a different class, which is also
> called ClassB (this is not the same ClassB that is included in the
project).
>
> Now if I use
> NewObject('ClassB', Path of ClassB),
> instead of creating the ClassB from the path I specify, it creates
> the ClassB that is included in the project.
>
> How can I instatiate the ClassB that is stored outside this project?
>
> (I guess I did not confuse!)
>
> Best Regards,
> Y. Sivaram
>
>
- Next message: crampe: "Release object in a procedure"
- Previous message: Anders Altberg: "Re: Manuel for ODBC"
- In reply to: Yoganathan Sivaram: "Class Instantiating Problem"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|