>If your timer creates objects and assigns them to class properties, then you're in trouble.

no.. it doesn't do that.. only call the methods of my main object (that one named oapros)... some of the data validation it is there... humm better gives you more details about the logic:

. its an application with the purpose to create communication with IP's micro terminals
. so, the timer run every 100ms searching any data typed by the end user... and produce all cicle of get/display data to produce the interaction.
. Some (most of) data received needs data validation.
. That data validation it is on OAPROS object.. for i.e. product's code validing... client's code validing

all of this run fines... since sometime ago (I'm not sure exactly when) that error starts on the end

>
>You would need to set these objects to null then.
>

humm... I tried to empty string ""

>There is an article by Christof Wollenhaupt that explaines it in all details.

Please, Do you have a link??
>
>Give me a sec.
>
>>I'm already doing this... I'm not sure about who needs to die first
>>>
>>>But I think the problem may lay somewhere else, not in interaction between these two classes.
>>
>>Yeah.. this is also my bet... but, there ins't so many objects there... the basic is the timer that call others objects that use a bunch of resources available at my main object named oapros (public variable of a custom object) called like this:
>>
>>

>>oapros   = createobj("sistema")
>>oapros.do("mainform")
>>
>>procedure oapros.do
>>lParameters lcAction
>>If  type("lcAction")="O"
>>Else
>>    lcAction = newOBJECT(lcAction)
>>
>>    lcAction.Show()
>>    luRetVal = lcAction.uRetVal
>>    If  lcAction.uRetVal=1
>>
>>        Read EVENTS
>>    Endif
>>endif
>>