You and someone else suggested me to use CHR(167)
I think my problem can be coming on how the computer "understand" the
extended ASCII Codes
If in this text I enter <ALT 167 the character that is displayed is º and
not §
I have not yet found which combination on my own PC gives the character §
At the moment I am looking at the internet site
(http://www.lookuptables.com/) that present the supposed most popular usage
of the Extended ASCII codes... I have tryed most of them but no one
correspond to the char § while all are clearly provide me with the expected
Character...
I have the real feeling it should come form taht point - Have you an idea on
how to control/access the extended ASCII Codes used in the MS VBA Editor -
Is it directly under the control of vba or coming from the Regional
Parameters or perhaps both?

Alain (France)

"William Benson" wrote in message
...
Sorry Alain, I do not know -- I will eagerly watch the rest of this thread
unfold as experts respond, which I know they will. This is the most
responsive forum in the known universe... and any unknown universes
probably
couldn't match it either :-)

Bill
"Alain79" wrote in message
...
Why not - good idea indeed
But have you an idea about why one specific machine present this strnge
behaviour
Because as long as I do not understand the reason I can have to face the
same problem with other characters such as with "é"
Thanks for your suggestion
Alain

"William Benson" wrote in message
...
Would it help to search for CHR(167) instead of actually identifying
the
"§"
symbol?


"Alain79" wrote in message
...
In a big Excel xla application I have some functions that goal is
just
to
detect if the character "§" is not in a string inside a specifc
cell -
up
to
now no problem...

This .xla Addin application is distributed on several countries -
most
of
PC
running the application are
= either Win2000 US plus Office 2000 US
= or Win 2000 US plus office 2003 US
= or Win XP US plus Office 2003 US

Problem description: on some machine (only a few), the xla
application
cannot be compiled, in fact if you open the microsoft visual basic
editor,
you can see that the "§" character has been replaced by a "?" that
produces
the compiler problem...

Have you an idea for the reason of this behaviour?
We have already made an analysis of the code page conversion table of
the
PC
that have the problem and have seen that its content was identical to
another PC without any problem...

Thanks if you can help
Alain