Re: Delphi DLL / VB app
- From: "DanG" <dang57@xxxxxxxxxxx>
- Date: 24 Apr 2005 09:46:38 -0700
Thanks Markku
I tried it as I did in Access, and again, it worked.
But it got me thinking. I had added a DLL reference in Access and VB
to the test project, then did the CreateObject. But the real VB app
cannot do that. It doesn't know anything about my DLL, other than that
there will be a function called "Process". So I attempted to do a
'late bind" by changing the "dim myObject" statement to only define
"Object" rather than my DLL. That did fail at execution.
So what would VB need to do to locate my DLL? I couldn't come up with
a good example. All I've seen as an example is:
Dim myObject as Object
set myObject = CreateObject(dllname.classname)
....but that doesn't work. Assuming that VB really does have a way to
do the late-bind, I expect the VB application does that. But if the
call to the DLL fails, then maybe there is something I need to do in
the DLL to allow VB to complete the late bind.
Suggestions are welcome.
Cheers
Dan
.
- Follow-Ups:
- Re: Delphi DLL / VB app
- From: J French
- Re: Delphi DLL / VB app
- From: Markku Nevalainen
- Re: Delphi DLL / VB app
- References:
- Delphi DLL / VB app
- From: DanG
- Re: Delphi DLL / VB app
- From: Markku Nevalainen
- Delphi DLL / VB app
- Prev by Date: Could someone explain this variable please
- Next by Date: Re: Could someone explain this variable please
- Previous by thread: Re: Delphi DLL / VB app
- Next by thread: Re: Delphi DLL / VB app
- Index(es):
Relevant Pages
|
|