ascii problem

[yellowke]

hi I want to use teh following ascci characters (200, 201, 205, 187, 188)
but when I use them I get wrong symbols.
In dos prompt when I check wit the e.g. alt + 201 I get the right character but in word and foxpro I get the wrong character.

Has this someting to do with extended ascii??
Anyone an idea how to solve this?

 

[DSummZZZ]

Ascii 200 is ascii 200. The only difference would be the way it is displayed, ie., font. Use a 'generic' font like System or FoxFont.
Dave S.

 

[ChrisRChamberlain]

yellowke

Check out INKEY() in the VFP Help file.

It provides a table of all the key combinations and their resultant values.

FAQ184-2483 - the answer to getting answered.​

Chris

 

[DSummZZZ]

Let me expand on my prior post. To experiment, do something like this in the command window:

?CHR(200) FONT 'FoxFont'
?CHR(200) FONT 'System'
?CHR(200) FONT 'Terminal'

And so on.
Dave S.

 

[yellowke]

e.g.
@prow()+1,1 say space(25)+chr(200)+replicate(chr(205),25)+chr(188) font 'FoxPro Window Font',12

This gives in an old version of foxpro the right output
But with the 6.0 it doesn't work

so the font is ok I think.

Tnx

 

[yellowke]

?CHR(200) FONT 'FoxFont'
gives the right symbol

But if I change it in the program I still got the wrong output??
So if I use it in the command box it gives the right symbol but in the program it doesn't work

 

[yellowke]

if I use this:

foxp1="font 'FoxFont',10"

is this than ok??

@prow()+1,1 say space(3)+replicate(chr(196),17)+space(20)+replicate(chr(196),20) &foxp1

Thanx
Yellowke

 

[DSummZZZ]

Using FoxPro 2.5 for Windows and VFP 6, I got exactly the same thing.(?) Garbage. If I'm not mistaken, you are trying to display a double line box.
It didn't look that way when I used "'FoxPro Window Font',12", but it did with Foxfont, Foxprint and Terminal.
Dave S.

 

[yellowke]

Indeed i'm trying to display a double line box

and foxfont gives in the command box the right output, but in the program it still doesn't work

 

[rgbean]

When you say it doesn't work in a program, where are you trying to display this data? On the screen, on a form, on a report, in a file?
Also, you are aware that the "standard" FoxFont only has 7, and 9 point natively and it isn't TrueType.

As Dave suggests you are really better off using a TrueType font in VFP.

Rick

 

[yellowke]

The program sends a report directly to a printer.
So When I use the program, the printer prints a report and there the symbols are wrong. So I don't get anything on a screen. I look to the paper and I see the bad symbols.
In foxpro 2.6a it works fine, but in foxpro 6.0 it gives problems like I discribed.

It's hard to explain

 

[rgbean]

Is this on the same system, same OS, same printer driver? Any of these may be changing things - not VFP. Is this a local printer or one on the network? (What kind of network?) When you say "direct to the printer" are you using something to bypass the Windows / Network spooler(s)?

Rick

 

[KoenPiller]

Hi,

take also a look at the function I found to convert ASCII characters read thread184-355164

Koen

 

[yellowke]

Does anyone know a true type font where I can find the symbols for a double line box?? double line like =
If I know the font then it won'b be so hard to find I think.

thx

 

[yellowke]

Hi,

I installed the font FoxPrint and that works
But now I got 1 little extra problem.
The text that is printed in courier new gives a problem with ë it gives a wrong simbol. That's the only thing that doesn't work that needs to be fixed.

But I think this time the problem is with the printer.
because when I check with ?chr(137) font 'courier new' it gives the right symbol. It only doesn't work when I print.

 

[DSummZZZ]

You should have specified you were sending these characters to the printer instead of the screen earlier in your post. We may have been better to help with the problem earlier on.
Anyway, Courier New doesn't have double line characters. The "ë" character is valid. What are you asying is the problem?
Dave S.