Calling Visual Basic DLL from Visual Objects
I know nothing of VO. However you should be aware that VB creates ONLY
Active-X DLLs. If VO is looking for a Standard DLL then you are not going
to get
it to fly! is VO an OLE Client? Find out the parallel to CreateObject or
Set within
the VO lingo...Basically, you don't do Declares with VB AX-DLL's...How do
you access
Objects in VO?? Some questions to get the brain-juices flowing. How about
talking to
the VO developer(s). Do they have a clue? If not then someone needs to do
some
sort of post implimentation design-triage thing.. ;-) Good luck, wish I
could help, but...
had anyone mentioned this at the beginning? had anyone tried it or was it
just an
assumption that a DLL is a DLL...Moe, Curly and Shemp do software...!!;-)
Neila
Quote:
>Erik,
>What version of VO is being used for this?
>What code have you created (or are are using) for declaring the DLL
>methods and etc.?
>> Hello,
>> I have produced a Visual Basic DLL for a customer who needs to be
>> able to access it from a Visual Objects application. When I use
>> the DLL from another VB application it works fine, but when we
>> try to use the DLL from VO, VO complains bitterly. I assume that
>> something is not being exported and/or mangled correctly, but not
>> being a VO developer I am not sure exactly what I need to do to
>> get it to work.
>> I have a class (say class1) with 2 public methods (method1 and
>> method2) which are hooks into the rest of the DLL functionality.
>> We have tried pulling it into VO both as a DLL and as an OCX
>> without any success (although it works fine from another VB
>> application as either a DLL or an OCX).
>> Does anyone have any pointers on how to resolve this problem?
>> Any help would be greatly appreciated!
>> Sincerely,
>> Erik Shepard
>--
>g.
>Gary Stark
>http://RedbacksWeb.com
>Sent via Deja.com http://www.deja.com/
>Share what you know. Learn what you don't.
