bnormal program termination - Memory protection fault

[FoxAl]

Upon printing any report within the system, the Foxpro application will return a message to user saying 'Busy... Please Wait whilst printing'. This is one of my programmed messages and is fine.This flashes and continues to flash until:-

However after a few seconds the whole application 'moves up the screen a few lines' and in the blank part of the screen at the bottom an error message appears 'bnormal program termination: Memory protection fault CS:EIP: oooFh:0002DDC2h

The only way we can exit the application from here is to CTRL-ALT-DELETE. The clock stops, the mouse and keyboard are inactive, the X to close the window is inactive. All 3 PC's are running under O/S of Windows XP and application is written in Foxpro 2.6a for DOS. The application lives on a Windows2000 server.

Despite all 3 PC's using the application being identical in hardware/software/set up 1 of the 3 PC's can always print from the application without any errors. The 2nd can print sometmes, othertimes it gets the same error as above and the 3rd PC always gets the above error and cannot print.

To add more confusion to all of this, there is a 2nd Foxpro for DOS applicaiton on another part of the server to which again all 3 PC's are connected. The bad pc above can usually print from there successfully and the other 2 have no problems at all from printing. All 3 PC's are new, have been completely rebuilt and several checks and runs such as scandisk and defrag have just recently been done on them

To me the problem has all the symptoms of faulty hardware, possibly bad sectors in the PC, but on the advice of 2 senior IT persons I am reassured this is not possible with these PC's.

Thanks for your help........

 

[DSummZZZ]

What method are you using to print?
A report form, @...SAY, ?/??/???, or some sort of spooler app?


-Dave Summers-

Even more Fox stuff at:

http://www.davesummers.net/foxprolinks.htm

 

[FoxAl]

it calls a procedure library which through various sys and function calls checks that the printer is on-line, is networked or local etc.

Having done that, it then checks the user input as to whether it is a detailed or summary report, whether or not to page eject before and/or after report.

In printing the report it uses ??? chr(12) to page eject (if required) and report form myreport ro printer - to print

 

[DSummZZZ]

You may want to avoid printing directly to the printer first (using the ???chr(12)), then printing the report form. That could cause some problems with the driver sing the port. Maybe use an IIF() in the report form as a separate field to eject if needed.
Also, be sure and use a 'Generic/Text only' for the report and not a printer specific driver.


-Dave Summers-

Even more Fox stuff at:

http://www.davesummers.net/foxprolinks.htm