Hi there,

I have some DTS routines which run overnight doing some calculating and some
flattening of data and form a Data Warehouse Database. We are currently
moving the routines from SQL7 to SQL2000 on another server. Now, one of the
DTS tasks is an ActiveX Script task which calls 2 methods in a vb6 dll, and
as part of the move I have rewritten the vb6 dll to a c# assembly.
Unfortunately, I can no longer call the new .NET assembly, I keep getting an
"ActiveX cannot create object" error. I've made my c# assembly with COM
interop and can call it from a vb6 application and it runs OK, but as soon as
I use 'CreateObject("WarehouseDTS.Routines")' I get the activeX error.

Can anyone help? Will I have to wait for SQL2005 before I can call .NET
assemblies directly (No COM Interop)?

If you have created a CCW then this should work. The error says that the CCW
is not registered correctly, same error you get when a regular COM DLL is
not registered correctly. Have you installed in correctly on the same
machine as the DTS package is being run, remembering DTS is all client side
COM itself.

--
Darren Green
http://www.sqldts.com

"Cammie Watson" <Cammie Watson (AT) discussions (DOT) microsoft.com> wrote

Hi Darren,

I have registered the DLL on the server. It is certainly something to do
with the CreateObject statement. I created a little test application with 2
buttons on a form, one that called the DLL using
CreateObject("WarehouseDTS.Routines") (just like the ActiveX task will) and
the other button called the DLL using 'Set X = New WareHouseDTS.Routines'.
And the second call works OK. Anyway I have worked around this problem by
creating an intermediate DLL in vb6 which calls the offending dll using the
second statement and then I call the intermediate DLL from the ActiveX script
using CreateObject.

Cheers

Cammie.

"Darren Green" wrote: