Class Lib Question

[jack]

I am building a VB.NET dll to act as a wrapper to a set of
V6 and .net libraries. I have the basic V6 features
working with the exception of this one thing.

I need the object to me able to create multiple intstances
when called using the
set objname=createobject(dllName.dll")
What is happening now is that subsequent calls to the
createobject just picks up the previous instance of the
object and operations second object effect the behavior of
the first.

My New code is simply:
bDB = CreateObject("Objec.class")
wher ebDb is a global object.

I know this is something simple that I am not doing in the
init code, I just do not knwo what it is.

[One Handed Man \( OHM - Terry Burns \)]

AFAIK, This create a reference to an existing COM object, it does not
instantiate a new one.

--

OHM ( Terry Burns )
. . . One-Handed-Man . . .
If U Need My Email ,Ask Me

Time flies when you don't know what you're doing

"jack" <ja**@sonomaenterprises.com> wrote in message
news:24****************************@phx.gbl...

I am building a VB.NET dll to act as a wrapper to a set of
V6 and .net libraries. I have the basic V6 features
working with the exception of this one thing.

I need the object to me able to create multiple intstances
when called using the
set objname=createobject(dllName.dll")
What is happening now is that subsequent calls to the
createobject just picks up the previous instance of the
object and operations second object effect the behavior of
the first.

My New code is simply:
bDB = CreateObject("Objec.class")
wher ebDb is a global object.

I know this is something simple that I am not doing in the
init code, I just do not knwo what it is.

[jack]

That is what I am finding. I even tries to create a
global reference to the object and then when I used it
create a new reference with obj = new gObj, but this did
not work since the gObj's definition was unknown.

I knwo this can be done, either in the definition of the
object in the library.

Has anyone done this before???

Jack

-----Original Message-----
AFAIK, This create a reference to an existing COM object, it does notinstantiate a new one.

--

OHM ( Terry Burns )
. . . One-Handed-Man . . .
If U Need My Email ,Ask Me

Time flies when you don't know what you're doing

"jack" <ja**@sonomaenterprises.com> wrote in message
news:24****************************@phx.gbl...

I am building a VB.NET dll to act as a wrapper to a set of V6 and .net libraries. I have the basic V6 features
working with the exception of this one thing.

I need the object to me able to create multiple intstances when called using the
set objname=createobject(dllName.dll")
What is happening now is that subsequent calls to the
createobject just picks up the previous instance of the
object and operations second object effect the behavior of the first.

My New code is simply:
bDB = CreateObject("Objec.class")
wher ebDb is a global object.

I know this is something simple that I am not doing in the init code, I just do not knwo what it is.

.