>>I've asked the question on 3 newsgroups, 11 fourms, and thus far everyone keeps telling me different ways to hide the objects. REMOVE I need to REMOVE objects.
>
>Victor,
>
>Can you explain why you must "remove" the objects and that making the object impotent is not good enough?
>
>That would certainly help us in figuring out how to do what you want. I don't believe that you will succeed in using RemoveObject as it also nulls the array reference. Any other attempt I tried to kill the object in the form failed.
>
>If you can tell us the reasoin that hiding doesn't cut it we may be able to give you a work around to get the job done.

Making a long story short....you know the problem when you have a grid's recordsource a view, and you requery the view it messes up the grid? (Same thing happens with comboboxes) Well this app I've been asked to work on has like a zillion controls and grids on the screens, uses stricly remote views. Problem is userA can't see what userB entered unless they exist the app and go back in...reason being that a lot of the non-parametrized remote views never get requeryed. My solution, for the moment anyway, is to have a 'global refresh' button (and/or a timer they can set) that will requery all these views. Problem, of course, is that the ones that are recordsources for grids and comboboxes will cause those to fry. So my idea was to simply copy all the grid and combobox objects to an array, remove the objects from the form, do the requerys, then add the objects back to the form from the array. Only thing is you cant do that with objects cause once you remove them from the form, VFP eats them from my array too! waaah! I guess the only other thing I can do is save the recordsources to an array, then wack those, do the requery, then put the recordsources back from the array. Just seems like a lot less hassle if I had the whole object instead! It's like it should only take me 3 lines of code to this and now it's turned into a major pain in the neck!