G
Guest
My company has decided to finally upgrade from Office 97 to Office 2003, which probably mainly is a good thing.
However, I get horrible problems with applications containing table links to an old Foxpro-based application, since the links use the old ISAM routine.
So I created an ODBC data source, which works excellently except for various national characters that are no longer displayed correctly (they mainly seem to be replaced with other weird characters, but sometimes are not displayed at all). This happens regardless of what collating sequence I choose.
Reading the tables as dBase III/IV ISAM files works fine, national characters and all, except for the two tables that contain Memo fields.
Modifying or upgrading the Foxpro application in any way is not an option at the moment.
I'm fine with using ODBC if anyone knows how to get around the national character issue. Does anyone here know how?
Henrik
However, I get horrible problems with applications containing table links to an old Foxpro-based application, since the links use the old ISAM routine.
So I created an ODBC data source, which works excellently except for various national characters that are no longer displayed correctly (they mainly seem to be replaced with other weird characters, but sometimes are not displayed at all). This happens regardless of what collating sequence I choose.
Reading the tables as dBase III/IV ISAM files works fine, national characters and all, except for the two tables that contain Memo fields.
Modifying or upgrading the Foxpro application in any way is not an option at the moment.
I'm fine with using ODBC if anyone knows how to get around the national character issue. Does anyone here know how?
Henrik