WinSpool/400 PDF Converter Revision History

From Support

1.0.35

2002-06-11

Added the ability to handle zero line spacing when using the AS/400 LPI/CPI page scaling.

1.0.34

2002-05-01

Added the ability to handle zero line spacing and truly combine data lines for viewing. This should allow any report with zero line spacing to view correctly.

1.0.33

2002-03-12

Added new routines to convert PDF files and allow them to be saved after processing.

1.0.32

2002-03-12

Added debug code to resolve AS/400 page scaling issues causing report files not to open. Commented out after testing.

1.0.31

2001-08-13

Added initial coding to allow PDF files to be saved. Code still needs to be tested fully. Not implemented for production yet.

1.0.30

2001-07-24

Added/removed German String translation option to replace German characters. Discovered WinANSIEncoding works better.

Added WinANSIEncoding to correctly display German characters.

1.0.29

2000-08-07

Resolved Error Type Mismatch 13 on foreign systems. gblFontWidthScaleFactor has a decimal in it, so we now use Val() to convert the value correctly when the INI settings get loaded.

1.0.28

2000-08-03

Added new Font property to handle font sizes 150- 198 columns. The use can also choose the column threshold before the 198 column setting is used. The default threshold is 150.

1.0.27

2000-07-12

Added new Font property to handle font sizes > 198 columns.

1.0.25-1.0.26

2000-02-15

Set number of header lines to scan

1.0.24

1999-12-29

Implemented 400 byte record length for our native writer. The Adobe PDF Writer already supports 400 byte records

1.0.22-1.0.23

1999-12-07

Implemented PPP Licensing. Timelock licensing was removed.

1.0.20-1.0.21

1999-11-26

Added VSVIEW control to handle printing when printing via the Adobe Distiller. When we used the VB printer object under Windows NT, printing to the Adobe Distiller printer would usually give us incorrect font results and then would sometimes work without reason.

Note: When installing this version, the entire setup for the WinSpool/40 PDF Report Converter must be downloaded and installed.

1.0.19

1999-11-06

Changed PDFObjOffsets and PDFPageObj to handle up to around 200000 pages. Customer had reported a "Error 9, subscript out of range" error message occurring in a 80000+ page report.

1.0.18

1999-11-01

Added Adobe Distiller functionality for those who want to use it.

Requirements: Adobe Acrobat Distiller V4.0.

1.0.17

1999-10-01

Description of change: Added StrCheckPairedVal2() for last record. A customer ran into a problem where the last report line had an unmatched parenthesis pair, thus causing the following problem: The "There was an error processing a page. Too few operands." error occurs when a page is encountered with wrongly orientated parends.

1.0.16

1999-09-22

Implemented CPI/LPI page scaling setting. If this setting is enabled, we use the AS/400 CPI/LPI values and page rotation values to determine how to scale the report page.

Did initial code implementation of page scaling based on AS/400 page length although this code has not been enabled for the end user yet.

1.0.15

1999-09-15

Implemented CPI/LPI page scaling setting. If this setting is enabled, we use the AS/400 CPI/LPI values and page rotation values to determine how to scale the report page.

Did initial code implementation of page scaling based on AS/400 page length although this code has not been enabled for the end user yet.

1.0.14

1999-05-19

We now handle line spacing correctly on the last record. The last record wasn't line spacing correctly.

1.0.13

1999-05-18

Scan the end of a string for a back slash character and replace with a period. If a line ends with a back slash the Adobe Acrobat Reader will have problems reading data from a page. This problem does't occur when the Adobe PDF Writer is used.

1.0.12

1999-04-20

Scan string for the ANSI vertical line character Chr(166) and replace with a vertical line character Chr(124). This fix prevents vertical lines from looking like an italic "f" character in the PDF. This problem does't occur when the Adobe PDF Writer is used.

1.0.11

1999-04-09

Changed PDFObjOffsets and PDFPageObj to handle up to around 64000 pages. Customer had reported a "Error 9, subscript out of range" error message occurring in a 11000+ page report.

Also changed version numbering to 1.0.11

1.10

1998-09-26

The following error was occurring from the Acrobat viewer if a page had unpaired parenthesis() on a line: "There was an error processing a page. Too few operands." We now scan for paired parends and then replace them if we find unpaired parends.

1.09

1998-09-26

The following error was occurring from the Acrobat viewer if a page had unpaired parenthesis() on a line: "There was an error processing a page. Too few operands." We now scan for paired parends and then replace them if we find unpaired parends.

1.08

1998-05-26

Reworked native PDF creation logic. We had some problems with some corrupted PDF files with the previous coding. The new implementation should stabilize the PDF file creation now. This means the NATIVE PDF Writer capability is now ready to go. Yeah !!!!!

1.07

1998-04-08'

Added standard text file conversion.

1.06

1998-04-08

Page contents objects were not changing, so we weren't jumping to the correct page when the user selected a new page. We were always displaying the first page. This was a major hole.

1.05

1998-04-07

We currently only support Courier New font when not using the Adobe PDF Writer. Acrobat expects some special information when using fonts such as Lucida Sans Typewriter, Letter Gothic, etc...

1.04

1998-04-07

Implemented code to automatically create the PDF Files without using the PDF Writer. The PDF Writer can be used optionally if the setting is enabled.

1.03

1998-03-06

Resolved overprinting problem noted by Chuck Ackerman. In a case where there are many lines with zero-spacing, characters were getting overlayed, thus causing a loss in data on the reports.

1.02

1998-02-02

Changed to recognize the Windows 95 and NT PDF Writers.

1.01

1998-01-31

Changed timelock code to only show our custom message the first time the program is started up. After the first time starting up, our custom startup dialog is displayed if running from command line. If calling the OLE Server, we will not display a timelock dialog again until the software expires.