>While performing the Execute statements do you create an other
>object references that are not release properly, or do you create
>any other references to loMyObj that haven't been set to null
>before releasing the last time?
>
No, no other references to the loMyObj. And this was something that was working fine from Friday... I don't know exactly what happened, but when I applied SET STEP ON even earlier in the program to check where other "dangling" objects might be, it started crashing back even farther....

It ended up that, it was crashing when it was making reference to another work area. During the Execute method, we have a table to log activities processed. as soon as it would try to SELECT MYLOGTABLE ... C5. I since disabled all references to the MYLOGTABLE and no more C5... Don't exactly understand. Maybe a corrupt file header even though the table was previously opened even before the SELECT???

Just chalk-it-up to the generic pitfall of C5 error with no rhyme or reason.