Query-A-Recordset - ActiveX DLL/DLL (.NET Ready) - V2.0.2

Présentation | Prix et licences | Évaluations et téléchargements | Compatibilité | Infos éditeur | Revues | Forums | Récapitulatif

Veuillez noter que les informations sur les produits ne sont pas disponibles en français.
Execute SQL queries on ADO Recordsets as if they existed as Tables in a Database. Query-A-Recordset lets you perform SQL Joins between Recordsets or Group and Aggregate fields in a Recordset. You can perform full SQL queries on any ADO Recordsets and return the results to your application. No more complex filter and find routines. No more expensive round trips to the Server to obtain a subset of data that already exists.

Nos prix standard sont montrés ci-dessous. Veuillez vous connecter pour voir vos prix.

Query-A-Recordset V2.0.2

Nos prix comprennent le support technique ComponentSource et, pour la majorité des produits téléchargeables, une sauvegarde en ligne ainsi qu'une mise à niveau GRATUITE si la nouvelle version est parue pendant les 30 jours consécutifs à votre achat.  Toutes les ventes sont sujettes à nos Termes et Conditions standard à notre Politique de renvoi. Veuillez nous contacter si vous avez besoin d'une option de licence (licence de volume et versions précédentes) qui ne figure pas sur la liste ci-dessus.

Nos prix standard sont montrés ci-dessus. Veuillez vous connecter pour voir vos prix.

What's New for Version 2.0x?

• Improved Performance - Tests have shown version 2 to be 5 - 6 times quicker than previous versions. Once the Recordset has been added to the collection, subsequent queries on added Recordsets are much faster. With previous versions it was necessary to declare optimization in advance in order to achieve this performance enhancement
• No Longer Case-Sensitive - Recordset query SQL criteria is no longer case-sensitive, i.e. 'SBS DEVELOPMENT' or 'sbs development' will return all 'SBS Development' records regardless of case
• Simplified Component Model - Version 2 now consists of 2 simple Objects. The RecordsetCollection Object responsible for storing the Recordset(s) that you wish to query, and the Execute Object used to perform the query and return the results in the form of an ADO Recordset

Using the Query-A-Recordset dll component couldn't be easier, just add the ADO Recordsets that you wish to query, declare an alias for each Recordset for identification, decide on the Cursor and Lock Types, add your SQL (MS Access SQL Syntax) and execute the query. Successful execution of the query will return a disconnected ADO Recordset representing the query results that will reflect the Cursor and Lock Types as defined. That's all there is to it.

When would you use the Component?

1. Filtering Data (Subsets of data)

Use the component to obtain a subset of the original data in an ADO Recordset.

Possible scenarios

You have already created an ADO Recordset containing the data required by your application and the initial population of the Recordset takes a considerable amount of time. Therefore you wish to utilize this data source in your application to avoid further round trips to the Database Server.

The original ADO Recordset contains a subset of data from the Database that you wish to filter further in an application based on user selections or application requirements. The applications filtering functionality is such that conventional Database querying techniques would be extremely difficult to manage. i.e. the need for complex nested queries.

Advantages

• Limits the number of round trips to the Database Server by utilizing data already available to the client
• Quicker than re-querying the Database. (Depending on size and complexity of Database)
• Improved application development productivity, Scalability, functionality and reliability
• Removes the need for complex nested queries

2. Data Aggregation

Use the component to obtain an aggregated result of data that already exists in an ADO Recordset.

Advantages

• Limits the number of round trips to the Database Server by utilizing data already available to the client
• Quicker than re-querying the Database. (Depending on size and complexity of Database)
• A good solution when connections to the Database are not available or have limited access for security or concurrency reasons

3. Joining Data

• As long as the data source can be represented in an ADO Recordset you can use it to perform a Join
• Join data from different Databases i.e. SQL Server and Oracle
• Join data from other non-Database sources i.e. Text and application derived data
• There maybe situations when you need to Join data from different sources when conventional database methods are not possible

Possible scenarios

• No database connection i.e. disconnected data source
• External data not contained in a Database i.e. Text file, or other data obtained from outside of the local business environment

4. Application with no Database

Use the component to provide SQL querying capabilities to an application without a Database

Possible scenario

Simple client application that doesn't warrant a complicated Database i.e. (uses a saved ADO Recordset as a data store), however the application still has a requirement to provide the user /developer with querying capabilities that are beyond the functionality offered by the ADO Recordset i.e. Sort, Filter and Find.

Advantages

• Offers a flexible solution to providing querying capabilities on saved ADO Recordsets
• No need to include a Database with the application to provide SQL querying capabilities

5. Application derived data

Use the component in an application that uses application derived data or a mixture of database and application derived data that requires querying capabilities to aid in the construction of ADO Recordsets consumed by the application.

Advantages

• Reduction in the complexity of code normally required to manipulate application derived data
• Improved application development productivity, Scalability, functionality and reliability