Up until recently I have gotten by with setting only 4 Params within a database component connecting to a SQL Server 7.0 database. These being the DATABASE-NAME, USER-NAME, ODBC DSN and PASSWORD. These have been enough on the majority of machines (both development and client) for the majority of the time. Recently one of the client PCs was starting to display 'é' characters as '#' as they were not recognised through the database connection. This was resolved by adding a further parameter of "LANGDRIVER='ascii' ANSI" to the database. The 'é' characters were then read correctly.
Am I using a suitable LANGDRIVER for this database connection or should I be using something else ?
Thanks in advance
Steve
Am I using a suitable LANGDRIVER for this database connection or should I be using something else ?
Thanks in advance
Steve