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.
 

Version 1.58O Release January 16, 2006

Support for Delphi 2006 Win32
PrintDAT! is now compatible with Delphi 2006 for Win 32. You will find the packages in the \PrintDAT\D2006Bin directory. Install this package like any other PrintDAT! package by opening the VclPD2006P.Dpk and compiling it. Also open the DclPD2006.Dpk and install it for Win32. With Delphi 2006 the VclPD2006P.bpl is put into your Borland Studio Projects directory and there is no need to move it to your c:\Windows\System32 directory. For more installation instructions please see the \PrintDAT\Doc\Readme.Rtf file.
 

Version 1.58N Release August 22, 2005

Support for TFmtBCD and TTimeStamp field types
PrintDAT! can now print data fields with TFmtBcd and TTimeStamp field types
 

Version 1.58M Release February 7, 2005

Support for Delphi 2005 Win32 (not .NET)
PrintDAT! is now compatible with Delphi 2005 Win32. (PrintDAT! does not support .NET) You will find the packages in the \PrintDAT\D2005Bin directory. Install this package like any other PrintDAT! package by opening the VclPD2005P.Dpk and compiling it. Also open the DclPD2005.Dpk and install it for Win32. With Delphi 2005 the VclPD2005P.bpl is put into your Borland Studio Projects directory and there is no need to move it to your c:\Windows\System32 directory. For more installation instructions please see the \PrintDAT\Doc\Readme.Rtf file.

New TpdtPrintDAT.AfterPreviewWindowOpened event
We added a new event so you have more control over the preview window. You can for example hide the output combobox to prevent users from exporting the data to a CSV file. TpdtPrintDAT.AfterPreviewOpened
 

Version 1.58L Release November 9, 2004

PrintDAT! Runs on Non-Updateable Windows Directory
Some of our customers have users that do not have write access to the Windows directory, which is where the PrintDAT.Ini file is located. In order to accomplish this all exceptions are trapped when saving to the PrintDAT.Ini file. Also it is worthwhile mentioning that back in version 1.58, if the .pxt file is read-only, the PrintDAT! report will still run, and the user can still make changes to the report options, but the report options cannot be saved back to the .pxt file, which is what you would expect when the .pxt file is read-only. This allows the PrintDAT! report to be run from a CD-Rom or other non-writeable media.

Corrected Range Check error
A range check error would occur if the user has left the computer on for more than 20 days. We had inadvertantly assigned a GetTickCount to an Integer instead of a DWord and it would produce a range check error if the computer was left on too long without rebooting. This has been corrected.

Can now print InfoPower TCustomEdit cellsInfoPower has the ability to embed an edit control like a TIWComboBox in a grid cell. PrintDAT! will now recognize the edit control and will print the control's contents rather than the contents from the underlying table.

Corrected Column Footer Total Widths
Column footers that appear on more than 1 line (because of embedded #13), would occasionally print as "****". This is because PrintDAT! incorrectly used the total footer string width instead of the string width between the #13. This has been corrected.

Corrected Column Footer losing character on 2 line footer
The column footer would occasionally lose a character after the line wraps to a new line. This has been corrected.
 

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