>I'm listening :).
>
>I have found in the very base class of that grid(4 levels deep) that it does reference a property .inCurrentRecordNumber. It has methods in that base class to set, change, and reference that variable. I'm still confused though..even if this record number was still stuck on say, 20, even though I had zapped the table and there were no longer any records in it, wouldn't I still have to set the record pointer to that variable(i.e. be in my code) to induce the Error 5? I think I understand that we're talking about properties and things that initialize/refresh in the VFP native code, which explains why I would be getting this error even when sitting on 'read events'..but I can't make the connection to how, even if these properties were incorrect, I would be getting the error where I am instead of from the code that actually sets the record pointer on that table to outside the range..
>
>Anyways..I'll keep looking, thanks for the input.
Hey, it was just a hunch. I don't know, really - this is one of those murky water cases, where the grid still somehow exists and its legs twitch while it's actually in a limbo, being destroyed, along with the rest of the form.
Did you try to set the grid's recordsource to "" before zapping the table? If I'm anywhere near right, that may make some difference.