Hi Michel,

So, is it SET TALK or SET EXACT?

>Well, after a long day of investigation to check every line in order to detect what was happening exactly, I finally found a major breakthrough in that quest.
>
>Under WIN2K SP3, at least, for my setups on several servers, I have found that when SYS(2335,0) is invoked, SET TALK becomes ON. So, that was affecting WWC eval object MergeText() method which evaluate a lot of = values and was returning a blank instead. For areas where a lot of evaluations was taking place, it was a big mess seeing the result that this was given.
>
>I have no SET TALK anywhere in the code. Magically, under that environment, memory has decided to turn it ON. So, in my error event, I have put the following:
>
>

>* This is needed under Win2K SP3 as,
>* after a SYS(2335,0) has been issued,
>* the value of SET EXACT is changed.
>SET EXACT OFF
>

>
>For those interested, you may take note of that.
>
>I know a lot of people have unauthorized the installation of WIN2K SP3 on several servers.
>
>Additionnaly to that, we also faced the WAM account desynchronization problems as well from the Components Service.