Sergey,

Thanks for the idea. Here's something new I just realized was going on. It's NOT just using SELECT statement that crashes at that point, it doesn't matter what statement is in that spot, it crashes one time, then after that you can step right over it and it works fine. Even if I leave that statement out and just make the END SCAN the next statement, that crashes, too. It just doesn't matter what is there. Because of this, I am leaning towards thinking that it has nothing to do with that table.

I've even suspended the code and manually chosen the table (and any other open table, too) at that point, and that crashes with teh same error.

I didn't know what else to do so at this point I am catching the error and just resuming and it works fine. It only will crash one time, then it works fine.

I will still gladly accept any ideas to really fix this...