Just wanted to reply to this, sorry for the delay. But no, there is no Fox8 specific code anywhere. It has to be some oddball combination of events that we're doing that is creating the problem with Fox8 and not Fox7 or Fox6. We've ultimately decided to abandon further development on that project (It's an old application that has run well since 97, but we're rewriting it in .NET/SQL and there isn't much point in putting man hours into trying to get it to run well under Fox8.) I was just curious if anyone else had ever run into such strange behavior, but it's probably due to the size and age of our application.

Thanks
Kevin