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