Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Codepage trouble
- Thread starter Schweiger
- Start date
The codepage fault occurs when dbase is installed using a different codepage than DOS.
Invariably, this will be 860 (US) v 437 (UK).
Data in tables and indexes (.ndx and .mdx) will be affected by a differing codepage.
You can either change the code page of your DOS, or reinstall dbase using the same codepage as DOS, but you will have to open and reindex all data and indexes before you can eradicate this problem.
Let me know which codepage your operating system operates on
(at DOS prompt, type CHCP and press enter. This will advise you of the active codepage).
Invariably, this will be 860 (US) v 437 (UK).
Data in tables and indexes (.ndx and .mdx) will be affected by a differing codepage.
You can either change the code page of your DOS, or reinstall dbase using the same codepage as DOS, but you will have to open and reindex all data and indexes before you can eradicate this problem.
Let me know which codepage your operating system operates on
(at DOS prompt, type CHCP and press enter. This will advise you of the active codepage).
- Thread starter
- #3
CHCP shows 437 as the active codepage. I know that I would have to install dBase to correct the problem, but the trouble is that it is a network installation witch nobody knows which adjustments have been made. So to avoid new troubles (never change a running system...) I would like just to ignore the error. I have never encountered any problems because of the wrong codepage so it's not an issue to me to correct it. My trouble is only, that the message shows up and the user has to answer it. I've found out, that I can add a field to the table, store the table and remove the added field again an then the message doesn't occure any more, but as foxpro writes to this table the wrong codepage will show up again after a while.
Btw Visual Foxpro uses 1252 as codepage... perhaps there's a way to tell VFP to use 437 as default codepage... who knows...
Thank you anyway for the explanation of the codepage issue
perhaps it gets me on the right track
Schweiger
Btw Visual Foxpro uses 1252 as codepage... perhaps there's a way to tell VFP to use 437 as default codepage... who knows...
Thank you anyway for the explanation of the codepage issue
perhaps it gets me on the right track
Schweiger
1oldfoxman
IS-IT--Management
"... perhaps there's a way to tell VFP to use 437 as default codepage... who knows..."
Find or create the Visual FoxPro configuration file called CONFIG.FPW. Change or add the following line in this text file :
CODEPAGE = 437
If you have to create the file, put it in the directory where FoxPro is installed. This file is supposed to be read on execution of FoxPro and allows you to set a number of defaults like codepage. I have not personally done this for codepages, but the VFP (version 6) documentation describes this ability to set codepages from within CONFIG.FPW.
Hope this helps
dennis
Find or create the Visual FoxPro configuration file called CONFIG.FPW. Change or add the following line in this text file :
CODEPAGE = 437
If you have to create the file, put it in the directory where FoxPro is installed. This file is supposed to be read on execution of FoxPro and allows you to set a number of defaults like codepage. I have not personally done this for codepages, but the VFP (version 6) documentation describes this ability to set codepages from within CONFIG.FPW.
Hope this helps
dennis
- Status