Well... I'm puzzled. After some more tests, my only conclusion is that 
the #include inside the macro sometimes fails to load correctly the 
included file contents, leaving there "unparseable" code.

--
jaime

Post a reply to this message