Icon View Incident Report

Serious Serious
Reported By: Faichung Hu
Reported On: 3/23/2010
For: Version 4.29 Build 2
# 3170 The ODBC Driver DSN Configuration Does Not Work Correctly on Chinese Version of Windows

I can set up the DSN alright in the Windows ODBC administrator. It can connect to the DBSRVR and display the available databases for me to choose. All seems well. However, when I later recheck the DSN, the username is all scrambled (showing Chinese characters: I am using Chinese Windows XP) and I am prompted for the user/password again. If I type in the correct user/password, it would proceed again like before.

I rechecked the DSN because when I tried to use it in Crystal Report XI or Access, the user/password prompt appears. And it does not matter what I typed in, it just kept re-appearing. When I used SVRADMIN to check the connection, the connection is there but it has no user name. It just seems like the login information is not passed (correctly) to DBSRVR.

Comments Comments and Workarounds
The encrypted registry entries for the user ID and password that are used for remote connections were being saved as string values. This did not work correctly on MBCS versions of Windows such as Chinese Windows XP or 7, and certain characters would be interpreted as leading bytes. These registry entries are now saved as binary data, avoiding this issue. The ODBC driver can read both string and binary data values for these registry entries, but always writes them out as binary data as of 4.29 B3.

Resolution Resolution
Fixed Problem on 3/27/2010 in version 4.29 build 3

Products Affected Products Affected
DBISAM ODBC Client-Server
DBISAM ODBC Client-Server with Source
DBISAM ODBC Standard with Source