We are working with a system that delivers Crystal Reports via the web using ASP and IIS on an NT server. We have test and production systems set up. We are reporting on Oracle 8 and FoxPro 2 or 3 databases.
Recently we have been struggling with reports that query both databases and have become quite familiar with the limitations and possible work-arounds.
Then all of the sudden, any report that hits just the FoxPro tables on the test server seems to bring IIS to its knees. The only way to bring the website back up is to reboot the entire server.
Reporting problems with disparate databases I can understand...but why should any reporting on FoxPro suddenly become the kiss of death. We recoil at the thought of our prduction server catching this desease.
Does anyone have any ideas?
Recently we have been struggling with reports that query both databases and have become quite familiar with the limitations and possible work-arounds.
Then all of the sudden, any report that hits just the FoxPro tables on the test server seems to bring IIS to its knees. The only way to bring the website back up is to reboot the entire server.
Reporting problems with disparate databases I can understand...but why should any reporting on FoxPro suddenly become the kiss of death. We recoil at the thought of our prduction server catching this desease.
Does anyone have any ideas?
