If you talk about a dbf as the external file, Mike is right. And it would also be good not to change the code page of the dbf as that might corrupt data for whatever other app may be using the same dbf.
That problem can occur if you for example use a dbf of a dos app in windows.
You can set the code page your program will work with via a config.fpw with the line CODEPAGE=...., eg 437 for US MSDOS or 850 for international MS DOS.
Besides that the codepage dialog only pops up, if you open the dbf exclusive and it has no codepage set. So that indicates you have one or two errors: The dbf has no codepage set and you work exclusive on it. The latter is an error only, if the app should support shared data access. Exclusive acccess but can be okay for single user or maintainance, when you want or need exclusive access.
See cpzero (maybe that was used on the dbfs) and use it to set the correct codepage on the dbfs.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.