[DUG] Com support

Conor Boyd Conor.Boyd at trimble.co.nz
Tue Jul 31 09:55:02 NZST 2007


Can you give more details about the "calls not working"?

E.g. presumably in your client code, you're trying to instantiate the
COM object you want to work with?  E.g. MyObj := CoSomeClass.Create; 

Is this call succeeding, but subsequent calls failing, etc?

If this call is failing, then, as Leigh suggests, your COM EXE is not
properly registered on the client machine.  COM exes can be registered
by running the exe with a /regserver parameter on the command line.

Is this COM or DCOM?  I.e. are you trying to instantiate a COM object on
another PC?

Any more details you can give about the specifics of the failure would
be good.

C.

-----Original Message-----
From: delphi-bounces at delphi.org.nz [mailto:delphi-bounces at delphi.org.nz]
On Behalf Of Robert martin

Its actually an exe that provides COM support.  I was missing the .tlb
which I managed to copy back of another machine.  This now allows me to
bring up the type library but alas still no com support.  It is failing
on multiple machines.

Sorry our Internet is down.  Will provide further details ASAP.

Leigh Wanstead wrote:
> Have you registered your com dll?
>
> -----Original Message-----
> From: delphi-bounces at delphi.org.nz
> [mailto:delphi-bounces at delphi.org.nz]On Behalf Of Robert martin
>
> Hi I have an app that (usually) provides some COM support.  I have 
> just updated a client and the COM stuff seems to be 'turned off'  (as 
> in the calls don't seem to work.  I did the COM stuff years ago, does 
> anyone have any suggestions where to start looking (I assume its a 
> setting / line of code somewhere I have turned off).
>
> p.s. My COM code and tlb file still seem intact.
>
> Hellllllp



More information about the Delphi mailing list