>I am facing a weird problem and I am wondering if this has something to do with the fact that I am assigning a value to a property by the use of an evaluation. One property of the class is named lDeleteConfirmationMessage. Its value in the class designer is =glListDelete. So, usually, a .T. or a .F. will be placed in that property. But, this is from a COM EXE calling another EXE and after a while the property gets mixed up. Basically, before creating an instance of that object, I am showing that glListDelete is in fact .F. But, once the object gets created, sometimes, at a random process, it is .T. So, either the problem is with that evaluation or because of the COM environment. Anyone has some idea about what is going on here?

This is a SWAG, but remember that a function that doesn't return anything, actually returns .T. e.g.

LOCAL llTest
llTest = .F.
llTest = MyUDF()
?llTest  && returns .T.

FUNCTION MyUDF
RETURN

So, if you have an unhandled CASE, IF etc. it might lead to what you're seeing.