Hi Jörg:

Yes, that could happen. If the binary file (scx,vcx,etc) have some type of corruption that let you run it but beshaves, then the compiled code can conflict, making the execution behave erroneous some times.

You said you use Source Control for your project. What are you using for the binary conversion to text and vice-versa?



>Yes, i checked this already, bud I couldn't see any difference that would raise this error.
>
>Maybe this is a compiler malfunction?!
>
>Because: today the error occurs again, bud i didn't do any change in that class!
>
>:-0
>
>>If you kept the erroneous version in source control (marked "kaputt"), you could compare the ascii-versions to the now errorless version to find out if the vcx had a temporary breakdown in the semi-structural-logical fields.