J
Jochen
Running COM objects created with VS2008 (FW3.5) either C# or VBasic yields
the following effect on all my machines, hence it seems not to be
installation dependent: Running the objects either with late or early
binding from Access2002 or vbscript runs w/o problems, using the same code
in Word 2002 causes an automation exception("Can not find ... or one of its
dependencies"). The Object browser of Word shows correctly the objects with
all their methods.
By the way: When compiling the same Code for the COM objects with VS2003
all calls from Word for these objects work fine.
I wonder if someboby has stumbled over this behaviour as well or has some
idea how to overcome it. Chasing the internet did not produce any results
thisfar.
many thanks for your help
Jochen
the following effect on all my machines, hence it seems not to be
installation dependent: Running the objects either with late or early
binding from Access2002 or vbscript runs w/o problems, using the same code
in Word 2002 causes an automation exception("Can not find ... or one of its
dependencies"). The Object browser of Word shows correctly the objects with
all their methods.
By the way: When compiling the same Code for the COM objects with VS2003
all calls from Word for these objects work fine.
I wonder if someboby has stumbled over this behaviour as well or has some
idea how to overcome it. Chasing the internet did not produce any results
thisfar.
many thanks for your help
Jochen