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 gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

alt-NNN key not appearing in field

Status
Not open for further replies.

foxup

Programmer
Dec 14, 2010
328
CA
Hi all,

I seem to have an issue with "alt-nnnn" keys result. When I press "Alt-159" in the vfp command window or in Notepad, I get the latin "f" symbol (ƒ) which is what I need. When i press "alt-159" in a character field in vfp , I get a "black square". Why is that and how can I get the latin f in a vfp character field.

any help would be greatly appreciated.


Thanks,
FOXUP!
 
I found out why it does that. it's the font of the table. If I use "calibri" font instead of "ms sans serif", I get the latin "F" on alt-159.

Works perfectly now. Thanks nonetheless guys :)
 
Hi,

If i try "REPLACE mytable.desc WITH CHR(159)" I get the black square and not the latin f, yet in the vfp command box when I type "? CHR(159)" it displays the latin f. The characters in tables are font sensitive.


Thanks ,
FOXUP !
 
Yes, what character is displayed does not only depend on ANSI codepage, fonts may also emulate other codepages by having characters of other codepages.
Using Terminal.ttf you can turn VFP into a DOS screen and have - besides others - all the characters for "drawing" grid lines.

The majority of fonts will display an ANSI character set in VFP, though, in which CHR(159) depends on which ANSI codepage you have, most likely 1252 in US and western europe, for which CHR(159) means Ÿ.

ALT+159 produces CHR(131) for me and displays as the latin ƒ with Courier and Arial and most fonts. this means Windows can translate that to the corresponding ANSI character. What you trigger by ALT+nnn is not ANSI codes, but codepoints of specific other codepages, not sure but codepage 850 fits this character. And by the way, this is no coincidence CHR(159) displays as latin ƒ with the Terminal font, as that also emulates codepage 850.

ALT+0159 will result in ANSI CHR(159) and is then displaying Ÿ, but ALT+159 is working for me, too, as said, in most fonts except such special VFP related fonts. Are you perhaps using foxfont within your _SCREEN?

Bye, Olaf.



 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top