New features and enhancements:

  1. A new TpFIBDataSet event has been added:

    property AfterUpdateRecord: TFIBAfterUpdateRecordEvent 
    where 
         TFIBAfterUpdateRecordEvent = procedure(DataSet: TDataSet; UpdateKind: TUpdateKind;
         var Resume:boolean) of object;
    

    The event happens during ApplyUpdates and ApplyUpdToBase methods for every record modification sent to the server. The event handler is called AFTER the query execution.

  2. TpFIBDataSet has a new option - poRefreshAfterDelete. If it is set to True, Refresh for the modified record is called after calling of the Delete method. If the Refresh attempt has been a success (i.e. the record has not been physically deleted), this record won't be deleted from cache and will remain visible.
  3. In FIBPlusTools the Preferences tab has a new option poUseLargeIntField in
    PrepareOptions and DateTimeDisplay setting in DefaultFormats
  4. Now FIBPlus components and FIBPlusTools are compatible with Delphi 2006.

Bugs fixed:

  1. Minor fixes in SQLNavigator in FIBPlusTools: on opening SQL Navigator window in a new application project (File->New->Application; FIBPlus -> SQL Navigator) the default module (Unit1.pas) disappeared. Fixed.
  2. Minor fixes in the SQL text search in SQLEditor.
  3. An error in the Locate method (Locate on deleted row returned True). Fixed.
  4. An error of handling Field.DisplayFormat, type "#,##0.00;-#,##0.00; ;" Fixed.
  5. Incorrect work of SQL Editor with the flag "Use Selected Fiedls Only". Fixed.
  6. An error of RefreshSQL in SQL Editor occurred because of the commented text at the beginning of SelectSQL. Fixed.
  7. Incorrect work of the dcForceMasterRefresh option. Fixed.
  8. An error in poKeepSorting on trying to change the first TpFIBDataSet record. Fixed.
  9. An error in poProtectedEdit. The current record position was incorrect. Fixed.
  10. Workaround for the internal Delphi compiler error E5912, appeared on recompiling the code of the following type: FIBBCDField.Value:=1;.
  11. An error which appeared on working with memory in TFIBStringField, when fields were created at design time and SQL text was changed at run time to increment the field length. Fixed.

Preview text: Read about better library stability, 4 enhancements, 11 bug fixes and better compatibility with Delphi 2006.
Prices in Euro:

235 (1 copy)
1250 (unlimited)

Volume discounts are available...

Navigation



We are a small software company with thousands of customers delivering comany wide systems including accounting, logistics, e-commerce, POS, sales etc etc. Several years ago, when we were still a very small company, we used Delphi 3 and Paradox combined with BDE. As our system (and customer base) grew I decided to switch to Delphi 5 and Interbase. Being a huge improvement over Delphi 3 and Paradox, I encountered numerous problems with IBX: memory leaks, performance issues and other problems. Borland was not to be bothered: IBX was provided "as is" and no support was avaliable. 
Not being very eager to use third party components with Delphi at first, I decided to give FIBPlus a try. At once all problems where gone: no more memory leaks and  performance was very consistent. 
But the real advantage of switching to FIBPlus came with the upgrade to D2005: after upgrading there were some problems with the new FIBPlus version. After emailing the problem I received an update within an hour! And this was at 11 pm! A few other (smaller) errors where handled in the same way. 
Our motto is: software is as good as its support. And support of Devrace is just great!
Just a little indication of our FIBPlus use: all our software runs 100% on FIBPlus. Our customers have a total of aprox. 4.800 Firebird databases in production, with a combined size of over 130TB and over 80 million transactions a day. Every
day. And FIBPlus has not failed a single transaction. Not once. There is, however, one (minor) drawback in using FIBPlus: while debugging an application which uses and invalid SQL instruction, de Delphi Debugger returns to the FIBPlus code instead of to our calling code (where the actual error comes from), thereby complicating de debug proces a little. But that is a very small price to pay for a otherwise brilliant third party solution! >>

Bas Jordans JorSoft Ltd
FOR CUSTOMERS
Download full versions and updates in your Personal Area