From your post, I get the impression that you are using DataPump to take reports from an external source, and to populate data in tables in Sybase using OLEdb? I presume that you've migrated all your v6 .mod files to v9 .xmod files using the Utility?
You might want to check in Monarch the Options around ASCII and ANSI - as this might affect the ' character issue. The null/space issue I'm not sure I can diagnose. We've noticed also that DataPump v9 is sensitive to server changes in regional options - so it's possibly worth looking in the registry to see if something's changed there.
I'm also having the same migration issues from V6 to V9. We populate SQL tables though. But characters in V6 display as null in SQL and V9 pushes them as spaces.
We had the same type of conversion issue with numeric values too, where V6 nulls would translate the field to 0, but in V9 null are pushed as null. So, to correct that we had to use calc fields in the model to correct the number fields.
But I can't figure out out to recreate the null behavior with a character field?
Create a numeric field with 1/0 as the formula to get a null value. Works in Monarch, so DP should be the same.
Edit: character field requirement. Hmm... try str(1/0). Success?[/QUOTE]
Data Kruncher, never thought of the STR function. That works!
I used the following for field A. Changed field name A to A_PRE . Created calc field A
The number filed was similar except for we used the following for a numeric field