Board index » delphi » Using the same ActiveX DLL on different machines results different results

Using the same ActiveX DLL on different machines results different results

What does your COM DLL do?

--
Binh Ly
http://www.techvanguards.com

Quote
"eldad" <el...@email.com> wrote in message news:39877b82_1@dnews...
> Hi,

> I'm stuck with a problem I can't solve.
> I have build an ActiveX DLL wich is registered (CreateOLE ) every times I
> launch the app.
> For some reason, the ActiveX runs without any problem on machines where
> delphi is installed, but when I try to run the same DLL and EXE on a
> machines without Delphi, I get errors (I can't even see what the errors
> are).

> Can someone help me with it, I think it has something to do with the
> integrated de{*word*81} of delphi, I just can't figure why the same code, with
> the same registration works on some computers and on others it doesn't.

> Thanks in advance,

> eldad

 

Re:Using the same ActiveX DLL on different machines results different results


Hi,

I'm stuck with a problem I can't solve.
I have build an ActiveX DLL wich is registered (CreateOLE ) every times I
launch the app.
For some reason, the ActiveX runs without any problem on machines where
delphi is installed, but when I try to run the same DLL and EXE on a
machines without Delphi, I get errors (I can't even see what the errors
are).

Can someone help me with it, I think it has something to do with the
integrated de{*word*81} of delphi, I just can't figure why the same code, with
the same registration works on some computers and on others it doesn't.

Thanks in advance,

eldad

Re:Using the same ActiveX DLL on different machines results different results


I found the problem

I had an IStrings interface that was not properly used.

This is the line that failed to work on computers without delphi :

GetOLEStrings (vValueObject.ItemsList as TStrings,vValueElement.FFixedItems)

The vValueElement.FFixedItems is a IStrings interface (nil).
For some reason, when I used this procedure on machines with delphi, no
error occured and string values were properly assigned to the interface, but
on other machines (without delphi)... error.

I changed it and added a function and a procedure to encapsulate a
TStringList with an IStrings, and it worked everywhere.

What I still wonder is, why didn't I get any error when I used it on delphi
machines ...

Re:Using the same ActiveX DLL on different machines results different results


Must have been a latent bug. :(

have fun
--
Binh Ly
http://www.techvanguards.com

Quote
"mike" <raffl...@email.com> wrote in message news:39887e4b_2@dnews...
> I found the problem

> I had an IStrings interface that was not properly used.

> This is the line that failed to work on computers without delphi :

> GetOLEStrings (vValueObject.ItemsList as

TStrings,vValueElement.FFixedItems)
Quote

> The vValueElement.FFixedItems is a IStrings interface (nil).
> For some reason, when I used this procedure on machines with delphi, no
> error occured and string values were properly assigned to the interface,
but
> on other machines (without delphi)... error.

> I changed it and added a function and a procedure to encapsulate a
> TStringList with an IStrings, and it worked everywhere.

> What I still wonder is, why didn't I get any error when I used it on
delphi
> machines ...

Other Threads