Hi Wayne:

Apparently the problem was a combination of things - network related and anti-virus related. One of the things that was happening was that the anti-virus software, Norton, was set to automatically update itself on login, and then every 2 hours after a user logged into a workstation. We changed that to uupdate itself every 10 hours. So far this week, it seems to be helping our problem.

We are in a funny situation with this app. We are a large division, part of a large agency. When the agency's IS division was concentrating mostly on mainframe issues, our division created its own little subset of IS to work on mostly pc applications. There's been sort of an "us vs them" relationship ever since. These old apps were created by a co-worker initially in FoxBase, and then when FoxPro 2.6 was the cutting edge. A few years ago our division management decided that our pc development should be turned over to the agency IS division. (We are still allowed to do minor development for small apps) The IS division is bent on getting rid of all FoxPro apps in the agency. When we have a problem with the app, we don't have ready access to the code to see if we can pinpoint a problem. So we call the IS people who are supposed to be supporting this app, and they say "we haven't changed anything, the program is fine, not our problem". Their standard answer is "We need to get rid of FoxPro". They want to rewrite the app in VB, using Access for the data container. They just haven't gotten around to doing it yet.

Last week I got more answers in one day from this forum that we've gotten from them in the last month. I appreciate your help so much. This long story is just to tell you how much it helps alleviate frustration just to know a direction to look in to solve the problems that crop up.

Thanks again to you and to everybody.

Kim Hughs
IL Dept of Revenue