>Wow, you sure are getting your share of these! I'm delighted that you are >taking the time to post the incident/information here.

It's becoming a constant maintainence issue, a real headache. I wonder if Microsoft will give me a refund for VFP8 :)

>As regards the previous one, I thought that it too happened in the >automated process. Is that correct?

Yes the previous one did happen there too, but not all of them.

>As regards the code below, is it all of the code or just the code related >to the table that got the error (just wanting to be clear).

That is only part of the code. It's the only part that opens that table.

>I'll look at the code and maybe 'characterize' it again in another reply to >this one, and if I see something I'll yell for sure.
>I hope also that MS folks are watching this thread and do likewise.
I have considered re-coding that sequence, but just havent had the time. I wrote that back in my earlier days, so I was definitely a novice. But it has been working for years. I wonder, If I set Tablevalidate to 0 will all my problems go away?