Thanks for the reply. I agree with you in the implementation part, i can sometimes forget that the objects always go by reference and not for value ... sho when i get red errors always check the object constructor/destructors code.

However, is very frustating that somethings VFP crash and go-out ... without having opportunity to correct the things (This happend if the object run code with null references, destroying with ciucular references, etc...), no able to debug VFP COM servers is a problem... maybe runing with class not problem but if you go to reality... A good error-handling support is a good help. In this area, VFP is best than VB (VB Always crash in each simple error if you no put the old On Error Goto blabla) VPF by default show a box with the error ... but again, this have problems with COM objects. For example, i use MS Toolbar, Stinga BeeGrid and other Activex control. If a run a form with MS Toolbar, without exeptional code, and close it, then chek the class code Uopps! the code is lost!, i ALWAYS need do CLEAR ALL for not code lost...

However, this is the fun part of programing!!! (if this is a simple task, everybody do it).

Thanks for the suggestion, i chek (again) the implementation...