What I'm trying to do...
------------------------
I'm trying to import data into an SQL server 2000 DB from an Ingres 6.4 DB, (on VAX-VMS), using a pre-setup DSN that uses an ODBC driver.
What goes wrong...
------------------
When I use the DTS Import/Export Wizard I select my (system) DSN for the source data, (Ingres),then enter the Username and Password for this Ingres DB and click <Next>.
At this point I get a DTS Import/Export Wizard Error dialogue "A serious error occurred when connecting to the provider"
This DSN works fine with other applications; for example I can link or import tables using MS Access and I have C++ Builder apps. which also work using the same DSN. I notice that within the DTS wizard the dialogue that is presented to enable you to declare the DSN or connection is different to the one in Access.
The DTS Import/Export works OK if I select an Access DB.
I have tried starting services such as Distributed Transaction Coordinator but it has made no difference.
I'm waiting for an upgrade for the ODBC driver and IngresNet comms. from CA but I've no reason to believe the newer drivers will fix this ... but I can hope!
=======================
Any suggestions????
=======================
------------------------
I'm trying to import data into an SQL server 2000 DB from an Ingres 6.4 DB, (on VAX-VMS), using a pre-setup DSN that uses an ODBC driver.
What goes wrong...
------------------
When I use the DTS Import/Export Wizard I select my (system) DSN for the source data, (Ingres),then enter the Username and Password for this Ingres DB and click <Next>.
At this point I get a DTS Import/Export Wizard Error dialogue "A serious error occurred when connecting to the provider"
This DSN works fine with other applications; for example I can link or import tables using MS Access and I have C++ Builder apps. which also work using the same DSN. I notice that within the DTS wizard the dialogue that is presented to enable you to declare the DSN or connection is different to the one in Access.
The DTS Import/Export works OK if I select an Access DB.
I have tried starting services such as Distributed Transaction Coordinator but it has made no difference.
I'm waiting for an upgrade for the ODBC driver and IngresNet comms. from CA but I've no reason to believe the newer drivers will fix this ... but I can hope!
=======================
Any suggestions????
=======================