PatMcLaughlin
Programmer
We have postscript files that are produced in a Foxpro process with Crystal Reports. These files are and will always be duplex-no tumble when printed at the printer, however, with no changes we can find being made on any systems, hardware or files they are no longer created duplex. We have examined all parts of Crystal to insure that it in fact is calling for duplex. Changed printer drivers for the 'postscript' printer. Forced the driver itself to call for Duplex but all to no avail. We have determined that there is one line in each of the .ps files that sets the printer to duplex so as a last resort we have decided to try to parse the postscript file to find and change the line from
'.../Duplex false put setpagedevice'
to
'.../Duplex true put setpagedevice'
This should put these printjobs back into usable production. My problem comes from ignorance of the coding. I have searched for individual characters in a line of text (i.e. changed "'" to ""). I should be able to use a
to walk the file. I believe I can then do
Am I close at all?
but now how do I save the complete but updated file so that it can be forwarded to the print process?
'.../Duplex false put setpagedevice'
to
'.../Duplex true put setpagedevice'
This should put these printjobs back into usable production. My problem comes from ignorance of the coding. I have searched for individual characters in a line of text (i.e. changed "'" to ""). I should be able to use a
Code:
Do While ! FEOF(postscript.ps)
lcRead = FGets(postscript.ps)
Code:
IIF(substr(lcRead, 16, 47) = "/Duplex false put setpagedevice", "/Duplex true put setpagedevice"
Am I close at all?
but now how do I save the complete but updated file so that it can be forwarded to the print process?