After a library user searches the CML's database for specific items, the search results are displayed to the user through RDS and ADO. The table created as a result of this search is also saved into the FmLib database.
The existence of these tables speeds performance because it lets users page back to see the results of previous queries without re-executing those queries. Caching data on the client computer in this manner minimizes data traffic to the server computer, which increases performance not only for this library user, but for all others connected to the server where the CML application is running.
Note Generally it is not necessary to store query results in temporary tables unless the original query is expensive to perform. For example, the query for selecting titles written by a particular author does require a complex join, but since it uses primary key indexes it can be performed quickly. On the other hand, a full-text search (FTS), especially if it includes several tables, can be very time consuming. For this reason, the CML only stores the results of FTS queries in temporary search tables.