>Erik
>
>>
>>This is a known problem with removing grid members. The object isn't really there, but there is some observable internal latency when reomving it. For a moment VFP thinks it's still there. Just name it something else.
>
>OK, thanks for the info...the only issue with the name-it-something-else workaround is that I am sort of sloppy about calling the method that switches the controls. In other words, I call it more than once (in fact, sometimes I have to, if the underlying data changes its columns, or increases in number of columns). What can I do then? Do I have to come up with a revolving naming scheme or sometihng? Or will VFP eventually remove the other object so I can just oscillate between a couple object names? Just fishing for ideas...in this specific case, I may be able to switch the controls once and call it good...I don't think my datasource is changing much this time...
>
>Is there a KB article on this for more detail?
>

I don't know of a KB article.

It should be enough to toggle between two names. VFP does eventually remove the object, it's just that it looks like the RemoveObject method is somewhat Asynchronous: it returns control to the calling procedure before it actually finishes. This is probably for speed. I have never seen, however an instance where one of these "phantom" objects persisted through a wait state.