> >
> > sorry,I dont understand correctly your english!
> > As i said in example above the cursor (its a table) stores the ascII characters (from 33 to 255).
> > If you make simply a browse you show one thing
> > If you make browse font "symbol" or
> > browse font "foxfont" you see another things completly different.
> > then for reading as you want these characters you must add mandatory the font.
> >
> >
> >
> > Dont rate please.its only for the pleasure to help.Give me only a feed back.
> > Yousfi Benameur
>
> *******************************************************************
> *******************************************************************
>
> My table looked like this:
>
> -------------------------------------------
> dmi study_number
> -------------------------------------------
>
> ³19 12345
> 18-32 56789
> 319 23456
>
> -------------------------------------------
>
> Pay attention to the dmi column in the table above. DMI column is a character field in a table. The first row is a "superscript 3" character and it concatenances with the "19" characters to make "³19" as a whole. Now look at the 3rd row which is incorrect because that "3" character should be the "superscript 3" character. I don't know why some of the tables we have, store the data correctly and some don't. Even when I copied from the "superscript 3" character from table1 and pasted into table2, a character field in table2 converted that "superscript 3" character to a "3" character. A "superscript 3" character should be a "Greater than or Equal to" sign to show either on the report or GUI. Please let me know if you still confuse. I wish I could post some images on here like you did. Not so sure what software I could use to do that.
>
> ps: I went online to search in hoping to illustrate my point of saying more clear. Take a look at this diagram. Scroll it down until you see a "superscript 3" character at 179 code.
>
> http://cwashington.netreach.net/main/library/ascii_chart.html
>
> Tai Nguyen.


Tai,

Maybe we are not talking about the same thing.
But anyhow I would not advise you to concentate the field dmi with the chr(163) and something else, put the chr(163) in a separate field. ( cGreaterOrLess seems to be a good fielddescription )
chr(163) is shown in Symbolfont the requested sign, in FoxFont however it is shown a completely different character, a '3' superscripted and in other font it shown again something else. In Tahoma e.g. you will see the British Currency sign.
So if you asign your GreaterThanAndEqualTo or LessThanAndEqualTo to a special field, you can always print that field in your Report just see to it the correct Font is applied to that field only. You cannot, at least how I know it, apply 2 different fonts to one and the same field.
There should also be a possibility to leave everything in one field, but than you shall have to chrtran the GreaterThanAndEqualTo to a readable sign in your applied font. I would not advise you to do that.
Regards,
Koen