Hi,

I've got a DTS package with a number of Data Transformation tasks
pulling data from an Oracle database into a SQL Server 7 database.
I'm not doing any conversion of the data - it's a straight per column
copy. When I run the package from my local machine (which has SQL
Server 2000 client tools) special characters such as Ö are getting
converted to their standard ascii equivalents, eg O. When I schedule
the package to run on the server (SQL Server 7) the special characters
are copied correctly.

Both database connections are using DTS Connection objects.

Clearly there is something different between the server and my local
machine that is causing the problem. I would like to fix my local
machine so it does the import correctly.
Does anyone know exactly what will be causing this problem, or can
anyone suggest where I should look? Is it likely to be my MDAC
version, my OLEDB for Oracle drivers, the SQL Server client tools
themselves, or something else?

I had an evaluation version of Toad on my machine which I used to look
at the oracle data, and it was unable to see the special characters.
Also using MS Access via ODBC driver for Oracle doesn't display the
special characters.

The driver I'm using to access Oracle through DTS is the 'Microsoft
OLE DB Driver for Oracle'. My msdaora.dll file's version is
2.60.6526.0.

many thanks for any help or suggestions,

- Rory

You can try DBPut converter , It support convert Oracle to SQL Server,
Download from http://www.dbput.com

DBPut might work, but I would first look at collation differences between the databases and how to keep them in sync as well. This can account for much of what you are experiencing

Regards
John Miceli