If i type <ALT>0198 in a data entry window I get  but with a text file 
which has this symbol in textpad, the vakue shows in a display as a with a ~ 
over it.

HELP?

Steve,

> If i type <ALT>0198 in a data entry window I get Æ but with a text file 
> which has this symbol in textpad, the vakue shows in a display as a with a ~ 
> over it.

You are using different character sets in each application.  This may mean
setting LOCALE or CHARSET in Xbase++.  Take a look in the docs.

Regards,

Phil Ide

***************************************
* Xbase++ FAQ, Libraries and Sources: *
* goto: http://www.idep.org.uk/xbase  *
***************************************

It said, "Insert disk #3," but only two will fit!

It's in a single application....

The only place it works right is within an SLE...

However adding :-

SET CHARSET TO ANSI

before I read the data in fixes the problem in the display of data red in, 
but does not fix it where the program has  in PRG code, or when it is read 
in as part of a file name.

Putting tha above line into the program at start, seems to resolve the other 
issues, but I will have to see how it affects otehr areas.



Thanks


"Phil Ide" <phil@idep.org.uk> wrote in message 
news:fsy68bbwfa2t.dlg@idep.org.uk...
> Steve,
>
>> If i type <ALT>0198 in a data entry window I get  but with a text file
>> which has this symbol in textpad, the vakue shows in a display as a with 
>> a ~
>> over it.
>
> You are using different character sets in each application.  This may mean
> setting LOCALE or CHARSET in Xbase++.  Take a look in the docs.
>
> Regards,
> -- 
> Phil Ide
>
> ***************************************
> * Xbase++ FAQ, Libraries and Sources: *
> * goto: http://www.idep.org.uk/xbase  *
> ***************************************
>
> It said, "Insert disk #3," but only two will fit!

Steve,

> The only place it works right is within an SLE...
> 
> However adding :-
> 
> SET CHARSET TO ANSI
> 
> before I read the data in fixes the problem in the display of data red in, 
> but does not fix it where the program has Æ in PRG code, or when it is read 
> in as part of a file name.
> 
> Putting tha above line into the program at start, seems to resolve the other 
> issues, but I will have to see how it affects otehr areas.

Does your editor make use of ANSI as well.
Our apps are fully GUI (well, almost all of them) and we found it the very
easiest to change to ANSI on all levels, tables, source, editor etc.

Peter

> 
> SET CHARSET TO ANSI
> 
Whenever I had problems like this I tried to solve it with ConvToOEMCP()
and ConvToANSICP(). See the docs, very useful.

HTH
Sebastian