Hi!

I always make control not visible when removing it. There is something like internally cached Windows events or repainting requests inside of VFP that are not purged properly when you remove visible control. When you make control invisible, these seems correctly purged from memory. It is possible it exists only for grids and certain other complex control - I do not know. I met this problem in other circumstances: Refresh grid a few times in code, remove it, then add grid with the same name as it was before. It would not add saying that object with such name already exists, that indicates previous grid is still not removed (in memory). ts quite strange, but when I make grid invisible before removing - all goes ok :))

I do not know if it is catalogued at MS as a bug - it was discussed a few times here without much attention...

>Hi Vlad...
>
>>

>>procedure thisformset.menu_options
>>lparameter oObject
>>cGrdobj = oObject.name
>>oObject.Visible = .F. && <===== NEW
>>This.myform.RemoveObject(cGrdobj)  && <======== it causes the message bellow
>>endproc
>>

>>
>
>Works greeeaaat.. Many thanks !!
>
>btw, is this was properly cataloged as bug by Microsoft ?
>
>
>Claudio