I don't know if it's relevant to your problem but an expresion in a property gets evaluated only the first time object gets instantiated. After that FoxPro uses cached values on consequent object creations for the same class.

>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?