Hi Bryan,

>First off I'd ask what type of problems?

There is only one instance of the application, used only by one person. I re-wrote it last April when the system was upgraded and would no longer load the FPW2.6 app. In fact I couldn’t even install FPW from the diskettes onto that system. Tried about everything to get the old app running, couldn’t and re-wrote the app in VFP6.

The problem involves report printing. To begin with the (new) application functioned as it should. In fact, everything short of the reporting still works fine.

Note: Every time I was called to see the problem I would take the application and place it on another system and print the report without error.

The reports are between 50 and 80 pages long. In the beginning they would print completely. At some point, about three months, the system was unable to print to the printer directly. The NT folks did some stuff and fixed that. Initially they made a network shareable printer to that same printer on another system and printed from the application printer to that shareable printer and it printed fine. They later went in and messed with the app system and made it once again able to print directly to the printer.

A month or 6 weeks after that it started printing up to a certain point and then start the print job over again from the beginning. (The report would print up to page 42, start over a page 1 and print to page 23, start over and print to page 18, start over and print to page......) This seemed like an NT problem, the print job would be in queue and get re-sent from the system level. I had the NT folks look at it and they claim there is nothing wrong and therefore it’s my application....

The fix was to loop through the report and have it send five pages at a time. If a particular job would be re-sent it would only reprint a small section of the report. This worked until about a month ago. I took the entire application and copied it to a shared network location, tried to print it and got the aforementioned results. I went to another system, accessed the network location and printed the report with out problem. I have printed from six other systems without problem.

Two days ago I got a call that the reports wouldn’t print again. One report was printed and the second failed. ( It’s same report, different data ) It would print to a specific page and then the printer would appear as it the print job was completed, though the report was not complete, and the application would be locked up. I am guessing it stopped at one of the 5 page jobs and the system was having some problems. They said that they exited out and when NT (4.0 sp6) started again an audio mixer GUI showed up and could not be terminated. They shut down and waited for me to show up.

Yesterday I went to look at it. Exact same behavior, printed part of the report and the app was completely locked forcing us to shut down. It came up once like mentioned (the mixer appeared). We shut down again and this time a very nasty blue screen came up showing many ntoskrnl.exe (sp?) errors. They are currently reinstalling NT.

The application has limited testing on 6 other systems and seems to work fine. Once again I would like to mention the garage upgrade that took place. Perhaps that has me looking in the wrong direction.

There is no chance of getting a replacement system to see if over time the same behavior will surface. Any ideas?

Thanks!