Home

SuperFastDistinct!

    Tutorial
    Why PrintDAT!?
    3rd Party
    Quotes
    Revisions

Download

Order Form

Revision History

Version 1.75 Release March 30, 2016
Support for Delphi 10 PrintDAT! now supports Delphi 10 32-bit and 64-bit.  

Install Program The install program is more Windows 7/8/10 friendly. The PDATReg.ini file now gets put into c:\ProgramData\GrebarSystems\PrintDAT directory instead of c:\Windows directory.  

Undefined Project and .PXT files When a TpdtPrintDAT component is dropped onto a form with an unsaved project, it used to create a .pxt file for BDS.pxt or Delphi32.pxt because it thought that was the name of the running program. This has been fixed so these .pxt files are no longer created. If the project name cannot be determined, the .pxt file is set to ReadOnly so no attempt will be made to save the contents of the file to disk.   

Delphi 3 to Delphi 6 are Deprecated We no longer support Delphi 3 to Delphi 6. It was too much effort to have the PrintDAT! demo program compilable with these older Delphi versions. This has nothing to do with the PrintDAT! component itself, and PrintDAT! may still compile and run fine under these older versions of Delphi. We just don't have the time or resources to maintain single source compatibility with 19 different versions of Delphi and 38 packages. Double that number if we include our evaluation components.

Version 1.74 Release August 12, 2015  Support for Delphi XE8 PrintDAT! now supports Delphi XE8 32-bit and 64-bit, including Update #1. InfoPower Bug Fix PrintDAT! would create an empty text file when exporting an InfoPower(TM) grid. This has been fixed.

Version 1.73 Release January 23, 2015 Support for Delphi XE7 PrintDAT! now supports Delphi XE7 32-bit and 64-bit, including Update #1.

Version 1.75 Release March 30, 2016
Support for Delphi 10 PrintDAT! now supports Delphi 10 32-bit and 64-bit.  

Install Program The install program is more Windows 7/8/10 friendly. The PDATReg.ini file now gets put into c:\ProgramData\GrebarSystems\PrintDAT directory instead of c:\Windows directory.  

Undefined Project and .PXT files When a TpdtPrintDAT component is dropped onto a form with an unsaved project, it used to create a .pxt file for BDS.pxt or Delphi32.pxt because it thought that was the name of the running program. This has been fixed so these .pxt files are no longer created. If the project name cannot be determined, the .pxt file is set to ReadOnly so no attempt will be made to save the contents of the file to disk.

Delphi 3 to Delphi 6 are Deprecated We no longer support Delphi 3 to Delphi 6. It was too much effort to have the PrintDAT! demo program compilable with these older Delphi versions. This has nothing to do with the PrintDAT! component itself, and PrintDAT! may still compile and run fine under these older versions of Delphi. We just don't have the time or resources to maintain single source compatibility with 19 different versions of Delphi and 38 packages. Double that number if we include our evaluation components.

Version 1.73 Release January 23, 2015 Support for Delphi XE7 PrintDAT! now supports Delphi XE7 32-bit and 64-bit, including Update #1

Version 1.72 Release June 20, 2014 Support for Delphi XE6 PrintDAT! now supports Delphi XE6 32-bit and 64-bit   Enhancements PrintDAT! forms such as Form Options and Preview will now remember their size and location from the last time they were displayed. Secondary monitors are also supported. Should the secondary monitor not be available when the PrintDAT! form is opened, the form will be displayed on the primary monitor instead

Version 1.71 Release December 28, 2013

Support for Delphi XE3, XE4, XE5
PrintDAT! now supports all versions of Delphi from version 3 to XE5.

Evaluation component updated
PrintDAT! evaluation components are now available for Delphi XE3, XE4, and XE5.

Version 1.70 Release July 1, 2012

Unicode Support for Delphi 2009
PrintDAT! now supports Unicode for Delphi 2009, as well as 2010, XE, and XE2.

Bug Fixes
Some bug fixes including InfoPowerTM related.
Demo program updates.

Enhancements
Speed improvements
Improvements to Preview window (opens to full screen)

Version 1.60 Release April 1, 2012

Delphi XE2 & XE Compatible
PrintDAT! Packages are now available for Delphi XE and XE2 (VCL).

32-bit & 64-bit Version for Delphi XE2
PrintDAT! now compiles in Delphi XE2 for 64bit or 32bit. No code changes are necessary and it uses the same source code as PrintDAT! for 32 bit. There are separate packages for 64bit and 32bit Delphi.

Unicode Support
PrintDAT! now supports Unicode output. A "Unicode Support" option on the Styles page under Include Options enables PrintDAT! to use a standard fixed spaced font like "Courier New" to generate the line draw characters. This means the "Letter Gothic Line PD" font is not needed and does not need to be installed on the client's machine before running a report. Unicode output can be turned on or off at runtime for each report so you have Unicode output when you need it, and standard ANSI output as well. So you can have your cake and eat it too.

Unicode (or ANSI) output can be sent to the:

  • preview screen
  • printer
  • text file
  • exported to a CSV text file

Anyone viewing the Unicode report does NOT need the "Letter Gothic Line PD" font installed because the standard "Courier New" font is used for Unicode reports (or any other fixed spaced Unicode font of your choosing). Unicode reports sent to a text file will display properly in any Unicode compatible text editor or wordprocessor. If the text editor or wordprocessor does not support unicode, then the report line draw characters are displayed as ASCII line draw characters and the report is still quite readable.

Note: Unicode is activated automatically for Delphi 2010 or later. If you wish to turn Unicode off you need to comment the "{$DEFINE UseUnicode}" line in \PrintDAT\Source\PDAT.Inc before compiling the PrintDAT! packages. See the Readme.Pdf for installation instructions.

Optimized Font Installer inside of the TpdtPrintDAT component
For those of you who do not need Unicode output, we have optimized the "Letter Gothic Line PD" font installation method so the TpdtPrintDAT component installs the font to the user's temporary directory instead of the Windows Font directory. This eliminates the need to have administrator rights for your Delphi application or to pre-install the font.

New Font Installation Program
For those of you who do not need unicode, PrintDAT! now has a new font installation program called PDATAnsiFontInstall.exe. This will manually install the "Letter Gothic Line PD" font onto the computer either:

  • permanently in the Windows font directory, or
  • temporarily in the user's temp directory

This font install program can be run either from the GUI or from a batch file using parameters without user intervention. This program can also uninstall the font. The program will run on 32bit or 64bit Windows and requires no additional files (the font is embedded into the .exe).

Exporting Data File Extension Changed
When exporting data the default file name extension has been changed from ".ASC" to ".CSV" which is the industry standard for comma delimited data.

Status bar warning message is displayed if Delphi project not saved
If the report is generated from inside the Delphi IDE by double clicking on the TpdtPrintDAT component, and the Delphi project (*.DPR) has not yet been saved by the user, PrintDAT! can't save the report settings to disk because it doesn't know the name of the project. The report will still run correctly but a yellow warning message will be displayed in the Report Options status bar saying the report options are read-only and the Report Options Save button is disabled. This message is a reminder to let the user know he or she shouldn't put too much effort into adjusting the report settings because the report settings can't be saved. Of course to avoid this message just save the .DPR file prior to double clicking on the TpdtPrintDAT component. This message will not be displayed if the report is run from an .exe. Note: The .exe file should be created in the same directory as the .DPR file or you will need to specify a ReportSettingsFileName or ReportSettingsDataset in the Object Inspector.

Saving Report Settings to .PXT file Simplified
When PrintDAT! was first created back in Delphi 3 days (when Win'95 dinosaurs ruled the earth), we overcame the 64k limit of .ini files by writing our own TpdtFileMgr class to store the report settings to a text file, and implemented our own file locking mechanism. This worked well over the years but now that PrintDAT! supports Unicode, we had to replace this ANSI text file storage class because it has to store the report headers and footers. There is no point generating Unicode reports if the report titles and footers couldn't be Unicode as well.

In this version of PrintDAT!, we rewrote TpdtFileMgr class to use TFileStream to save the report settings to a text file, which supports Unicode if needed. This also makes it backward compatible to your existing ANSI .pxt files so you don't have to lift a finger to do any file conversions. It just works! :-)  Keep in mind that if you use a text editor to manually edit this .pxt file and you have Unicode report headers/footers for some of these reports, then you need to use a Unicode capable text editor, otherwise the text editor will save Unicode titles/footers as ANSI text. PrintDAT! can still read the ANSI .pxt file but your (non-English) Unicode report headers/footers will show up as "?" because the ANSI text editor converted them back to ANSI characters. A good free Unicode text editor is Notepad++.

A few versions earlier we also implemented the ability to store report settings to a TDataset, avoiding the .pxt text file altogether. The TDataset works much better on a network where there are a lot of users printing reports. We still include a utility program called PRSUtils.exe that will convert your .PXT files over to a TDataset of your choosing. The PdtPrintDAT component has a property where you can specify the dataset for storing the report settings. Keep in mind that if you use Unicode in your reports, your database table must be capable of storing Unicode data. So if you are using dbISAM to store the report settings and you want Unicode reports, you will need to upgrade to ElevateDb or another database that supports Unicode.

New Help Files
We had the help files converted to .CHM from .HLP. PrintDAT! can display the CHM help files automatically on older operating systems like Win'95. See \PrintDAT\Source\PDAT.Inc and Readme.Pdf for more information.

New Readme.PDF File
We switched to a PDF readme file with more screenshots to make the installation easier.

Updated Tutorial.Pdf
The tutorials have been updated. The tutorial is found in \PrintDAT\Doc\Tutorial.Pdf.

Updated Demo Program
Our PrintDAT! demo program has been updated to reflect the new features in PrintDAT! v1.60. It can be found in \PrintDAT\Demo directory with complete source code. A fully compiled Demo program is also available for download from http://www.grebarsys.com/html/download.html in case you don't have Delphi 2010 (or later) for Unicode. This Demo program can also print or export XML files which you may find useful (see Unicode example).

Bug Fixes
Fixed a minor problem with ASCII line draw on a TStringGrid with fixed columns. PrintDAT! used to draw a vertical line of "+" symbols instead of "|" after the fixed column. This has been corrected.

Corrected memo creep in the report titles and footers. When the report settings were saved, an extra blank line may have been added to the header or footer. This has been fixed.

Version 1.59d Release November 11, 2009

Bug Fixes
When printing a page range not all pages were printed. This has been corrected

Version 1.59c Release October 10, 2009

Doesn't use .ini Files (optional)

Network users were having problems granting access rights to Printdat.ini files. Since these ini files only have default values and stores the last screen positions, we decided to make them optional. PrintDAT! will only use .ini files if the component is compiled with the conditional directive "UseIniFile" turned on (uncommented). See the \PrintDAT\Source\PDAT.Inc file for more information.

If you have modified the c:\Windows\Printdat.ini file to use different line draw characters, or if you want PrintDAT! to remember the position and size of the preview window, then uncomment the "UseIniFile" in PDAT.Inc and this will activate the use of .ini files.

Version 1.59b Release October 1, 2009

Bug Fixes

Corrected a compiler bug when compiling with InfoPower support. We inadvertantly left in the reference to the old Bookmark method where it should have been PDBookmark.

Corrected a memory leak.

Support for Delphi 2010

PrintDAT! now supports Delphi 2010.

New Events: OnLoadReportSettings and OnSaveReportSettings

These events will allow you to store and retrieve report settings from your database (or other sources) rather than using a .PXT file. This will make it easier to maintain the report settings over a network. This code was contributed by one of our users.

TpdtPrintDAT can now use a Dataset to store report settings

We liked the previous idea so much, we created dataset support for storing report settings. It is now as simple as assigning a dataset to the TpdtPrintDAT.ReportSettingsDataset property.

PRSUtils Program
We also created a PRSUtils.exe program to import your existing .PXT files into the dataset. For more information please see the PRSU_Readme.Pdf and PD_Dev.Hlp file. The PRSUtils program is in the \PrintDAT\Utils directory. You can of course continue to use .PXT files to store the report settings, but a Dataset will make it easier to store the report settings on a network.

The PRSUtils program supports database engines: BDE, DBISAM, ElevateDb, NexusDb and Advantage. Complete source code is included and can be modified to handle other database engines.

Version 1.59d Release November 11, 2009

Bug Fixes
When printing a page range not all pages were printed. This has been corrected
 

Version 1.59c Release October 10, 2009

Doesn't use .ini Files (optional)

Network users were having problems granting access rights to Printdat.ini files. Since these ini files only have default values and stores the last screen positions, we decided to make them optional. PrintDAT! will only use .ini files if the component is compiled with the conditional directive "UseIniFile" turned on (uncommented). See the \PrintDAT\Source\PDAT.Inc file for more information.

If you have modified the c:\Windows\Printdat.ini file to use different line draw characters, or if you want PrintDAT! to remember the position and size of the preview window, then uncomment the "UseIniFile" in PDAT.Inc and this will activate the use of .ini files.

Version 1.59b Release October 1, 2009

Bug Fixes

Corrected a compiler bug when compiling with InfoPower support. We inadvertantly left in the reference to the old Bookmark method where it should have been PDBookmark.

Corrected a memory leak.

Support for Delphi 2010

PrintDAT! now supports Delphi 2010.

New Events: OnLoadReportSettings and OnSaveReportSettings

These events will allow you to store and retrieve report settings from your database (or other sources) rather than using a .PXT file. This will make it easier to maintain the report settings over a network. This code was contributed by one of our users.

TpdtPrintDAT can now use a Dataset to store report settings

We liked the previous idea so much, we created dataset support for storing report settings. It is now as simple as assigning a dataset to the TpdtPrintDAT.ReportSettingsDataset property.

PRSUtils Program
We also created a PRSUtils.exe program to import your existing .PXT files into the dataset. For more information please see the PRSU_Readme.Pdf and PD_Dev.Hlp file. The PRSUtils program is in the \PrintDAT\Utils directory. You can of course continue to use .PXT files to store the report settings, but a Dataset will make it easier to store the report settings on a network.

The PRSUtils program supports database engines: BDE, DBISAM, ElevateDb, NexusDb and Advantage. Complete source code is included and can be modified to handle other database engines.

Version 1.59 Release January 30, 2009

Support for Delphi 2007, 2009 (Win32)

PrintDAT! is now compatible with Delphi 2009 for Win 32. You will find the packages in the \PrintDAT\D2009Bin directory. Install this package like any other PrintDAT! package by File Open >  VclPD2009P.Dpk and compiling it. Also open the DclPD2009.Dpk and install it for Win32. You will still need to copy the VclPD2009Bin package to your Windows System directory.
 

For a list of all the revisions in prior PrintDAT! versions download the help file from our download page here.

Contact webmaster with questions regarding this site.
copyright © Grebar Systems Inc. All rights reserved.

Site updated Wednesday, October 18, 2017