Question: Why donít FindFirst and FindNext methods work?

Answer:  There are two types of filtering in FIBPlus:


1. Data filtering on the server. It is done by executing the corresponding query.

This type of filtering has its advantages:
it does not use the client computer and reduces network traffic as the server restricts the number of required records;

and disadvantages:
the dataset can keep only a part of filtered data. When you need to change filtering conditions, you need to change the query and execute it anew on the server. Previous data will be lost.
FIBPlus has a very powerful mechanism for filtering on the server:

  • a query in the property,

  • an ability to insert conditions (in design or runtime time),

  • macros, etc

2. Data filtering in the dataset. It is totally different from data filtering on the server:
FIBPlus retrieves all data from the server (taking into consideration filtering restrictions of the SQL query), and then filters it in the dataset. The effect is the same as after data filtering on the server, BUT it is done locally and does not require network. So this type of filtering extends the features of type 1.

3. FIBPlus can also search for required records, but this is not filtering. FIBPlus has Locate and LocateNext methods, they do not filter any records. They set the pointer of the current record to a record which corresponds to the defined parameters. To find the next record you should call the LocateNext method.

If you need records which satisfy some condition, you can use Type 1 or Type 2. Methods FindFirst and FindNext are not supported by FIBPlus.


Preview text: 
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