(Warning: very low level of knowledge....)
I have a problem with PS drivers on Win2k producing much more complex PS than their NT4 equivalents. I need to find a Win2k driver which will produce nice simple PS.
We have a legacy system which deals with concatenation and pagination of reports which are produced as a number of PS files by Windows applications which print to file using PS drivers (mostly HP).
To insert a client name and page number, the legacy program looks for showpage operators, assumes these indicate a new page and inserts what amounts to a footer to appear on the previous page.
The problem is that Win2k drivers seem to produce lots of showpage operators, which I guess are called conditionally. Hence the legacy program puts its footers in the wrong places - the file still prints, but the footer does not appear.
My choices are:
1. Learn lots of PS and re-engineer the program to insert its footers correctly (unlikely before the deadline)
2. Find a simpler driver - but there are too many for trial and error
3. Design a whole new way of doing this (deadline problem again)
Can anyone suggest a driver to try?
Many thanks in advance
Bill.
I have a problem with PS drivers on Win2k producing much more complex PS than their NT4 equivalents. I need to find a Win2k driver which will produce nice simple PS.
We have a legacy system which deals with concatenation and pagination of reports which are produced as a number of PS files by Windows applications which print to file using PS drivers (mostly HP).
To insert a client name and page number, the legacy program looks for showpage operators, assumes these indicate a new page and inserts what amounts to a footer to appear on the previous page.
The problem is that Win2k drivers seem to produce lots of showpage operators, which I guess are called conditionally. Hence the legacy program puts its footers in the wrong places - the file still prints, but the footer does not appear.
My choices are:
1. Learn lots of PS and re-engineer the program to insert its footers correctly (unlikely before the deadline)
2. Find a simpler driver - but there are too many for trial and error
3. Design a whole new way of doing this (deadline problem again)
Can anyone suggest a driver to try?
Many thanks in advance
Bill.