- Are any other characters affected besides 0xa7?
- Is the binary itself being changed or is it just being interpreted incorrectly?
A quick test shows that at least german umlauts are also affected. If you save a string into the ( dbase ) database and then open it with an editor you will find the string as is in the database when using the old NI drivers on NT but you will see some translation on non ASCII characters done using the Microsoft drivers on XP . So you will will get only problems if you write with the old driver and read with the new driver or vice versa.
- Does regular ASCII work? (the first 127 characters)?
Seems to work . But I didn't test all ASCII characters.
- Is it the native ODBC driver from Windows or an additional one?.
It's the driver which which is called in the ODBC control panel "Microsoft dBase Driver 4.00.6304 Microsoft Corporation ODBCJT32.dll 4.8.2004 "
- What code pages are set for Windows?
I'am not quite sure where to lookup the settings for codepages. Is it in the control panel ? Then I did overlook it.
I'm using a standard german language setup.