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;
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),
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.
During a re-write of a very large software system we were having some difficulties utilizing a 3rd party grid that we had chosen. The dataset connectivity was very flaky due to the complex joins and updates we were using which caused the grids to behave very sketchy. FIBPlus was the perfect solution for us. After implementing it everything became so much easier. The grid functionality stabilized, data retrieval was much faster, and we were pleasantly surprised by many of the unique features of your components. We were especially impressed with your pFIBUpdateObject components which allowed us to very easily update the multiple tables we were using in our joins. Many thanks for your great components.>>