[kevina]

I have done more testing of this, and have found the following results:

Both isql and osql will do this conversion improperly if the 'Automatic ANSI to OEM conversion' flag is checked in the SQL Server Client Network Utility.

For some reason, osql always does the conversion (even with the setting unchecked). So (as you previously stated), the only way to load these characters (from an ANSI file) is to invoke isql instead.

We will update the sql server action to allow the user to specify either isql or osql in a future release of Visual Build Pro.

In the meantime, another option (since you are inputting your sql from file anyway), would be to simply save your input files as UNICODE. Then you could continue to use the Sql Server action and load your data properly (and you don't have to uncheck the conversion setting in Client Network Utility). Just a thought.

Kevin