FoxPro 2.5 and VFP 6.0

All, hope I'm in the right newsgroup. Hope I can explain my problem.

I have an excel file which I've converted via DataJunction to a foxpro 2.5
table.
I'm having trouble with when it comes to reading foreign characters.
MEANING: It doesn't read foreign characters!
I've got wierd characters on a lot of the foreign records.


I think it has to do with the codepage 437 not being able to display the
characters correctly.

If I open the original excel file, it displays fine. In foxpro 2.5 version
it does not. Depending on if I am at home or work version 6.0 may or may
not.

When I open in 2.5 it opens fine but displays poorly. When I try to read it
in with VFP 6.0 it states that the file "is not marked with a codepage". It
asks for me to choose a codepage. I've been choosing 437 and 1252 in
different tries with varying success.

What I need is for the version 2.5 to display them as well as can be done
for DOS.

Am I on the right track? Right or wrong, could someone offer any insight
what might be happening?

Regards
Dale Jones

Wolfgang
Mon Feb 14 19:40:45 CST 2005

I'd try codepage 850 International DOS
To correct the codepage look for the CPZero.prg in your VFP folder
Home()+"Tools\Cpzero\cpzero.prg"
then write SET CPDIALOG ON in the command window and open the table. Then
you should be asked to choose the codepage for that dbf IMHO you'd choose
850

--
----------------------------------------------

Mit freundlichen Grüßen

Wolfgang Schmale



--------------------------------------------
"JaleDones" <djones_1> schrieb im Newsbeitrag
news:OgBP3jvEFHA.3728@TK2MSFTNGP14.phx.gbl...
> All, hope I'm in the right newsgroup. Hope I can explain my problem.
>
> I have an excel file which I've converted via DataJunction to a foxpro 2.5
> table.
> I'm having trouble with when it comes to reading foreign characters.
> MEANING: It doesn't read foreign characters!
> I've got wierd characters on a lot of the foreign records.
>
>
> I think it has to do with the codepage 437 not being able to display the
> characters correctly.
>
> If I open the original excel file, it displays fine. In foxpro 2.5
> version it does not. Depending on if I am at home or work version 6.0 may
> or may not.
>
> When I open in 2.5 it opens fine but displays poorly. When I try to read
> it in with VFP 6.0 it states that the file "is not marked with a
> codepage". It asks for me to choose a codepage. I've been choosing 437
> and 1252 in different tries with varying success.
>
> What I need is for the version 2.5 to display them as well as can be done
> for DOS.
>
> Am I on the right track? Right or wrong, could someone offer any insight
> what might be happening?
>
> Regards
> Dale Jones
>
>
>

JaleDones
Mon Feb 14 20:10:42 CST 2005

Thanx for the reply Wolfgang.

I want to use the 2.5 version. Did you mean "in your VFP folder"? I.E.
Visual FoxPro?

I'm assuming the DOS 2.5 version of Foxpro has nothing to do with "Visual"?

Just want to be sure I'm on your wavelength.

Dale



"Wolfgang Schmale" <Spamkocher@strang.lt> wrote in message
news:OQW%23f9vEFHA.628@TK2MSFTNGP15.phx.gbl...
> I'd try codepage 850 International DOS
> To correct the codepage look for the CPZero.prg in your VFP folder
> Home()+"Tools\Cpzero\cpzero.prg"
> then write SET CPDIALOG ON in the command window and open the table. Then
> you should be asked to choose the codepage for that dbf IMHO you'd choose
> 850
>
> --
> ----------------------------------------------
>
> Mit freundlichen Grüßen
>
> Wolfgang Schmale
>
>
>
> --------------------------------------------
> "JaleDones" <djones_1> schrieb im Newsbeitrag
> news:OgBP3jvEFHA.3728@TK2MSFTNGP14.phx.gbl...
>> All, hope I'm in the right newsgroup. Hope I can explain my problem.
>>
>> I have an excel file which I've converted via DataJunction to a foxpro
>> 2.5 table.
>> I'm having trouble with when it comes to reading foreign characters.
>> MEANING: It doesn't read foreign characters!
>> I've got wierd characters on a lot of the foreign records.
>>
>>
>> I think it has to do with the codepage 437 not being able to display the
>> characters correctly.
>>
>> If I open the original excel file, it displays fine. In foxpro 2.5
>> version it does not. Depending on if I am at home or work version 6.0
>> may or may not.
>>
>> When I open in 2.5 it opens fine but displays poorly. When I try to read
>> it in with VFP 6.0 it states that the file "is not marked with a
>> codepage". It asks for me to choose a codepage. I've been choosing 437
>> and 1252 in different tries with varying success.
>>
>> What I need is for the version 2.5 to display them as well as can be done
>> for DOS.
>>
>> Am I on the right track? Right or wrong, could someone offer any insight
>> what might be happening?
>>
>> Regards
>> Dale Jones
>>
>>
>>
>
>

Jeroen
Tue Feb 15 04:12:09 CST 2005

On Mon, 14 Feb 2005 18:54:47 -0600, "JaleDones" <djones_1> wrote:

>I have an excel file which I've converted via DataJunction to a foxpro 2.5
>table.
>I'm having trouble with when it comes to reading foreign characters.
>MEANING: It doesn't read foreign characters!
>I've got wierd characters on a lot of the foreign records.
Since you converted from Excel TO FPD, it is Excel's responsibility to
convert the 'special'characters.
If I am not mistaken, Excel always saves to a DBF file using a
codepage 437 (meaning DOS-USA). However depending on the version of
Excel it may allow for characters that are not included in codepage
437, so Excel has no substitute for the character.

>I think it has to do with the codepage 437 not being able to display the
>characters correctly.
That's correct, not all international symbols are represented in the
437 codepage, therefore they desigined Unicode

>If I open the original excel file, it displays fine. In foxpro 2.5 version
>it does not. Depending on if I am at home or work version 6.0 may or may
>not.
The display in Foxpro Dos is partly determined by the underlying DOS
codepage (set in config.sys/autoexec.bat).
In VFP it is determined by the 'codepage=' setting in config.fpw and
the current codepage in the dbf

>When I open in 2.5 it opens fine but displays poorly. When I try to read it
>in with VFP 6.0 it states that the file "is not marked with a codepage". It
>asks for me to choose a codepage. I've been choosing 437 and 1252 in
>different tries with varying success.
A codepage within a .dbf file indicates to VFP how the special
characters in the DBF are defined. Using that VFP will do an automatic
character translation when is has to display the value (akin to
CPCONVERT(..) )

>What I need is for the version 2.5 to display them as well as can be done
>for DOS.
To determine if all characters are correctly converted, you can read
in the resultant dbf back into Excel. If all special characters are
displayed correctly than it is something you can fix in FPD, if
characters are missing/strange than it is Excels fault and you cannot
repair the damage in FPD

Wolfgang
Tue Feb 15 04:15:40 CST 2005

Hi Dale!

I mean the homedir of my VFP-Dir. But I think there should be a cpzero.prg
in your FPD-dir too.
In the directory of my FPW2.6 exists a cpzero.prg. But if you cannot find it
I'd send it to per eMail

--


------------------------------

Mit freundlichen Güßen aus der Zigarrenstadt

Wolfgang Schmale

------------------------------------------------
"JaleDones" <djones_1> schrieb im Newsbeitrag
news:Ob1nUOwEFHA.3244@TK2MSFTNGP15.phx.gbl...
> Thanx for the reply Wolfgang.
>
> I want to use the 2.5 version. Did you mean "in your VFP folder"? I.E.
> Visual FoxPro?
>
> I'm assuming the DOS 2.5 version of Foxpro has nothing to do with
> "Visual"?
>
> Just want to be sure I'm on your wavelength.
>
> Dale
>
>
>
> "Wolfgang Schmale" <Spamkocher@strang.lt> wrote in message
> news:OQW%23f9vEFHA.628@TK2MSFTNGP15.phx.gbl...
>> I'd try codepage 850 International DOS
>> To correct the codepage look for the CPZero.prg in your VFP folder
>> Home()+"Tools\Cpzero\cpzero.prg"
>> then write SET CPDIALOG ON in the command window and open the table. Then
>> you should be asked to choose the codepage for that dbf IMHO you'd choose
>> 850
>>
>> --
>> ----------------------------------------------
>>
>> Mit freundlichen Grüßen
>>
>> Wolfgang Schmale
>>
>>
>>
>> --------------------------------------------
>> "JaleDones" <djones_1> schrieb im Newsbeitrag
>> news:OgBP3jvEFHA.3728@TK2MSFTNGP14.phx.gbl...
>>> All, hope I'm in the right newsgroup. Hope I can explain my problem.
>>>
>>> I have an excel file which I've converted via DataJunction to a foxpro
>>> 2.5 table.
>>> I'm having trouble with when it comes to reading foreign characters.
>>> MEANING: It doesn't read foreign characters!
>>> I've got wierd characters on a lot of the foreign records.
>>>
>>>
>>> I think it has to do with the codepage 437 not being able to display the
>>> characters correctly.
>>>
>>> If I open the original excel file, it displays fine. In foxpro 2.5
>>> version it does not. Depending on if I am at home or work version 6.0
>>> may or may not.
>>>
>>> When I open in 2.5 it opens fine but displays poorly. When I try to
>>> read it in with VFP 6.0 it states that the file "is not marked with a
>>> codepage". It asks for me to choose a codepage. I've been choosing 437
>>> and 1252 in different tries with varying success.
>>>
>>> What I need is for the version 2.5 to display them as well as can be
>>> done for DOS.
>>>
>>> Am I on the right track? Right or wrong, could someone offer any
>>> insight
>>> what might be happening?
>>>
>>> Regards
>>> Dale Jones
>>>
>>>
>>>
>>
>>
>
>

Dale
Tue Feb 15 09:43:28 CST 2005

Ok Wolfgang, I get it.

New problem tho. I mistakenly said this version of foxpro was 2.5. It = is
not. It is 2.0. This seems to matter. Is this version too old to use = the
suggestion you put forward?

Dale

"Wolfgang Schmale" <SpamIstSoSchön@Spamkocher.bla> wrote in message
news:OvX8Md0EFHA.560@TK2MSFTNGP15.phx.gbl...
> Hi Dale!
>
> I mean the homedir of my VFP-Dir. But I think there should be a cpzero.prg
> in your FPD-dir too.
> In the directory of my FPW2.6 exists a cpzero.prg. But if you cannot find
> it I'd send it to per eMail
>
> --
>
>
> ------------------------------
>
> Mit freundlichen Güßen aus der Zigarrenstadt
>
> Wolfgang Schmale
>
> ------------------------------------------------
> "JaleDones" <djones_1> schrieb im Newsbeitrag
> news:Ob1nUOwEFHA.3244@TK2MSFTNGP15.phx.gbl...
>> Thanx for the reply Wolfgang.
>>
>> I want to use the 2.5 version. Did you mean "in your VFP folder"? I.E.
>> Visual FoxPro?
>>
>> I'm assuming the DOS 2.5 version of Foxpro has nothing to do with
>> "Visual"?
>>
>> Just want to be sure I'm on your wavelength.
>>
>> Dale
>>
>>
>>
>> "Wolfgang Schmale" <Spamkocher@strang.lt> wrote in message
>> news:OQW%23f9vEFHA.628@TK2MSFTNGP15.phx.gbl...
>>> I'd try codepage 850 International DOS
>>> To correct the codepage look for the CPZero.prg in your VFP folder
>>> Home()+"Tools\Cpzero\cpzero.prg"
>>> then write SET CPDIALOG ON in the command window and open the table.
>>> Then you should be asked to choose the codepage for that dbf IMHO you'd
>>> choose 850
>>>
>>> --
>>> ----------------------------------------------
>>>
>>> Mit freundlichen Grüßen
>>>
>>> Wolfgang Schmale
>>>
>>>
>>>
>>> --------------------------------------------
>>> "JaleDones" <djones_1> schrieb im Newsbeitrag
>>> news:OgBP3jvEFHA.3728@TK2MSFTNGP14.phx.gbl...
>>>> All, hope I'm in the right newsgroup. Hope I can explain my problem.
>>>>
>>>> I have an excel file which I've converted via DataJunction to a foxpro
>>>> 2.5 table.
>>>> I'm having trouble with when it comes to reading foreign characters.
>>>> MEANING: It doesn't read foreign characters!
>>>> I've got wierd characters on a lot of the foreign records.
>>>>
>>>>
>>>> I think it has to do with the codepage 437 not being able to display
>>>> the characters correctly.
>>>>
>>>> If I open the original excel file, it displays fine. In foxpro 2.5
>>>> version it does not. Depending on if I am at home or work version 6.0
>>>> may or may not.
>>>>
>>>> When I open in 2.5 it opens fine but displays poorly. When I try to
>>>> read it in with VFP 6.0 it states that the file "is not marked with a
>>>> codepage". It asks for me to choose a codepage. I've been choosing
>>>> 437 and 1252 in different tries with varying success.
>>>>
>>>> What I need is for the version 2.5 to display them as well as can be
>>>> done for DOS.
>>>>
>>>> Am I on the right track? Right or wrong, could someone offer any
>>>> insight
>>>> what might be happening?
>>>>
>>>> Regards
>>>> Dale Jones
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>

Cyrus
Tue Feb 15 10:10:08 CST 2005

Dale wrote:
> Ok Wolfgang, I get it.
>
> New problem tho. I mistakenly said this version of foxpro was 2.5. It = is
> not. It is 2.0. This seems to matter. Is this version too old to use = the
> suggestion you put forward?
>
> Dale
>
> "Wolfgang Schmale" <SpamIstSoSchön@Spamkocher.bla> wrote in message
> news:OvX8Md0EFHA.560@TK2MSFTNGP15.phx.gbl...
>
>>Hi Dale!
>>
>>I mean the homedir of my VFP-Dir. But I think there should be a cpzero.prg
>>in your FPD-dir too.
>>In the directory of my FPW2.6 exists a cpzero.prg. But if you cannot find
>>it I'd send it to per eMail
>>
>>--
>>
>>
>>------------------------------
>>
>>Mit freundlichen Güßen aus der Zigarrenstadt
>>
>>Wolfgang Schmale
>>
>>------------------------------------------------
>>"JaleDones" <djones_1> schrieb im Newsbeitrag
>>news:Ob1nUOwEFHA.3244@TK2MSFTNGP15.phx.gbl...
>>
>>>Thanx for the reply Wolfgang.
>>>
>>>I want to use the 2.5 version. Did you mean "in your VFP folder"? I.E.
>>>Visual FoxPro?
>>>
>>>I'm assuming the DOS 2.5 version of Foxpro has nothing to do with
>>>"Visual"?
>>>
>>>Just want to be sure I'm on your wavelength.
>>>
>>>Dale
>>>
>>>
>>>
>>>"Wolfgang Schmale" <Spamkocher@strang.lt> wrote in message
>>>news:OQW%23f9vEFHA.628@TK2MSFTNGP15.phx.gbl...
>>>
>>>>I'd try codepage 850 International DOS
>>>>To correct the codepage look for the CPZero.prg in your VFP folder
>>>>Home()+"Tools\Cpzero\cpzero.prg"
>>>>then write SET CPDIALOG ON in the command window and open the table.
>>>>Then you should be asked to choose the codepage for that dbf IMHO you'd
>>>>choose 850
>>>>
>>>>--
>>>>----------------------------------------------
>>>>
>>>>Mit freundlichen Grüßen
>>>>
>>>>Wolfgang Schmale
>>>>
>>>>
>>>>
>>>>--------------------------------------------
>>>>"JaleDones" <djones_1> schrieb im Newsbeitrag
>>>>news:OgBP3jvEFHA.3728@TK2MSFTNGP14.phx.gbl...
>>>>
>>>>>All, hope I'm in the right newsgroup. Hope I can explain my problem.
>>>>>
>>>>>I have an excel file which I've converted via DataJunction to a foxpro
>>>>>2.5 table.
>>>>>I'm having trouble with when it comes to reading foreign characters.
>>>>>MEANING: It doesn't read foreign characters!
>>>>>I've got wierd characters on a lot of the foreign records.
>>>>>
>>>>>
>>>>>I think it has to do with the codepage 437 not being able to display
>>>>>the characters correctly.
>>>>>
>>>>>If I open the original excel file, it displays fine. In foxpro 2.5
>>>>>version it does not. Depending on if I am at home or work version 6.0
>>>>>may or may not.
>>>>>
>>>>>When I open in 2.5 it opens fine but displays poorly. When I try to
>>>>>read it in with VFP 6.0 it states that the file "is not marked with a
>>>>>codepage". It asks for me to choose a codepage. I've been choosing
>>>>>437 and 1252 in different tries with varying success.
>>>>>
>>>>>What I need is for the version 2.5 to display them as well as can be
>>>>>done for DOS.
>>>>>
>>>>>Am I on the right track? Right or wrong, could someone offer any
>>>>>insight
>>>>>what might be happening?
>>>>>
>>>>>Regards
>>>>>Dale Jones
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>
>
>
If I remember right, 2.0 didn't support code pages. You may have a
problem working with non-english data with 2.0.

--
Cy Welch
Senior Programmer
MetSYS Inc
http://www.metsysinc.com

Dale
Tue Feb 15 10:34:57 CST 2005


Thanx for the response. I think you're right Cy.

Dale

"Cyrus Welch" <cywelch@hotmail.com> wrote in message
news:A9pQd.275$Pz7.178@newssvr13.news.prodigy.com...
> Dale wrote:
>> Ok Wolfgang, I get it.
>>
>> New problem tho. I mistakenly said this version of foxpro was 2.5. It =
>> is not. It is 2.0. This seems to matter. Is this version too old to use =
>> the suggestion you put forward?
>>
>> Dale
>>
>> "Wolfgang Schmale" <SpamIstSoSchön@Spamkocher.bla> wrote in message
>> news:OvX8Md0EFHA.560@TK2MSFTNGP15.phx.gbl...
>>
>>>Hi Dale!
>>>
>>>I mean the homedir of my VFP-Dir. But I think there should be a
>>>cpzero.prg in your FPD-dir too.
>>>In the directory of my FPW2.6 exists a cpzero.prg. But if you cannot find
>>>it I'd send it to per eMail
>>>
>>>--
>>>
>>>
>>>------------------------------
>>>
>>>Mit freundlichen Güßen aus der Zigarrenstadt
>>>
>>>Wolfgang Schmale
>>>
>>>------------------------------------------------
>>>"JaleDones" <djones_1> schrieb im Newsbeitrag
>>>news:Ob1nUOwEFHA.3244@TK2MSFTNGP15.phx.gbl...
>>>
>>>>Thanx for the reply Wolfgang.
>>>>
>>>>I want to use the 2.5 version. Did you mean "in your VFP folder"? I.E.
>>>>Visual FoxPro?
>>>>
>>>>I'm assuming the DOS 2.5 version of Foxpro has nothing to do with
>>>>"Visual"?
>>>>
>>>>Just want to be sure I'm on your wavelength.
>>>>
>>>>Dale
>>>>
>>>>
>>>>
>>>>"Wolfgang Schmale" <Spamkocher@strang.lt> wrote in message
>>>>news:OQW%23f9vEFHA.628@TK2MSFTNGP15.phx.gbl...
>>>>
>>>>>I'd try codepage 850 International DOS
>>>>>To correct the codepage look for the CPZero.prg in your VFP folder
>>>>>Home()+"Tools\Cpzero\cpzero.prg"
>>>>>then write SET CPDIALOG ON in the command window and open the table.
>>>>>Then you should be asked to choose the codepage for that dbf IMHO you'd
>>>>>choose 850
>>>>>
>>>>>--
>>>>>----------------------------------------------
>>>>>
>>>>>Mit freundlichen Grüßen
>>>>>
>>>>>Wolfgang Schmale
>>>>>
>>>>>
>>>>>
>>>>>--------------------------------------------
>>>>>"JaleDones" <djones_1> schrieb im Newsbeitrag
>>>>>news:OgBP3jvEFHA.3728@TK2MSFTNGP14.phx.gbl...
>>>>>
>>>>>>All, hope I'm in the right newsgroup. Hope I can explain my problem.
>>>>>>
>>>>>>I have an excel file which I've converted via DataJunction to a foxpro
>>>>>>2.5 table.
>>>>>>I'm having trouble with when it comes to reading foreign characters.
>>>>>>MEANING: It doesn't read foreign characters!
>>>>>>I've got wierd characters on a lot of the foreign records.
>>>>>>
>>>>>>
>>>>>>I think it has to do with the codepage 437 not being able to display
>>>>>>the characters correctly.
>>>>>>
>>>>>>If I open the original excel file, it displays fine. In foxpro 2.5
>>>>>>version it does not. Depending on if I am at home or work version 6.0
>>>>>>may or may not.
>>>>>>
>>>>>>When I open in 2.5 it opens fine but displays poorly. When I try to
>>>>>>read it in with VFP 6.0 it states that the file "is not marked with a
>>>>>>codepage". It asks for me to choose a codepage. I've been choosing
>>>>>>437 and 1252 in different tries with varying success.
>>>>>>
>>>>>>What I need is for the version 2.5 to display them as well as can be
>>>>>>done for DOS.
>>>>>>
>>>>>>Am I on the right track? Right or wrong, could someone offer any
>>>>>>insight
>>>>>>what might be happening?
>>>>>>
>>>>>>Regards
>>>>>>Dale Jones
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>
>>
>>
> If I remember right, 2.0 didn't support code pages. You may have a
> problem working with non-english data with 2.0.
>
> --
> Cy Welch
> Senior Programmer
> MetSYS Inc
> http://www.metsysinc.com

Leonid
Wed Feb 16 04:33:41 CST 2005

> If I am not mistaken, Excel always saves to a DBF file using a
> codepage 437 (meaning DOS-USA). However depending on the version of

No, Excel uses codepage forom the key

HKLM\System\CurrentControlSet\Control\Nls\CodePage\OEMCP

in my case it's 866. And it uses file from the key

HKLM\System\CurrentControlSet\Control\Nls\CodePage\866

to get actual codepage information.

Leonid

JaleDones
Wed Feb 16 07:16:35 CST 2005

Jeroen,

Note in another part of this ?thread I realized I was actually working with
Foxpro 2.0. See further comments below.

>>I think it has to do with the codepage 437 not being able to display the
>>characters correctly.
> That's correct, not all international symbols are represented in the
> 437 codepage, therefore they desigined Unicode
>

I don't suppose FPD would work with Unicode, would you?

>>If I open the original excel file, it displays fine. In foxpro 2.5
>>version
>>it does not. Depending on if I am at home or work version 6.0 may or may
>>not.
> The display in Foxpro Dos is partly determined by the underlying DOS
> codepage (set in config.sys/autoexec.bat).

I'm using WindowsXP. If I set up a way to variably change the codepage to
say, 850, could that be accomplished. And the go back to what the codepage
was originally set?

This data is names and addresses and will have to be output to a printer.
Given the characters display correctly will a printer render them correctly?

Regards
Dale

Jeroen
Wed Feb 16 16:16:34 CST 2005

>Note in another part of this ?thread I realized I was actually working with
>Foxpro 2.0. See further comments below.
If I'm correct FPD 2.0 does not support codepages. This means that it
will display the raw fieldinfo directly; no conversion will be done by
FPD.

>>>I think it has to do with the codepage 437 not being able to display the
>>>characters correctly.
>> That's correct, not all international symbols are represented in the
>> 437 codepage, therefore they desigined Unicode
>
>I don't suppose FPD would work with Unicode, would you?
Indeed, FPD does only work with the standaard DOS-characters.

>>>If I open the original excel file, it displays fine. In foxpro 2.5
>>>version
>>>it does not. Depending on if I am at home or work version 6.0 may or may
>>>not.
>> The display in Foxpro Dos is partly determined by the underlying DOS
>> codepage (set in config.sys/autoexec.bat).
>
>I'm using WindowsXP. If I set up a way to variably change the codepage to
>say, 850, could that be accomplished. And the go back to what the codepage
>was originally set?
You can dynamically switch codepages in dos (although I don't remember
how exactly). But you can only use 1 codepage for the entire program
But it is easier to just change the config.nt in your windows
directory to reflect the codepage you want to use. (or setup a special
config.nt file for this one program, see the advanded tab in the
shortcut properties)

>This data is names and addresses and will have to be output to a printer.
>Given the characters display correctly will a printer render them correctly?
Only if you setup the printer to use the same codepage as DOS is
using. Remember in DOS (therefore also FPD2.0) you have to send al the
controlcodes to the printer yourself to setup the correct font,
codepage, papersize, etc

>Regards
>Dale
Did you try reading back the dbf file into excel?