Error: Class does not support Automation or does not support expected interface. when using report parameter lookups
The following are examples of error messages that may occur:
- Class does not support Automation or does not support expected interface
The following error can occur in when using the Report Parameter Lookup buttons to retrieve parameter lookup information: -
Error Number : 
Description : [Item cannot be found in the collection corresponding to the requested name or ordinal.]
Source : [ADODB.Fields]
The error only occurs with certain ODBC drivers and when using Alchemex parameter Lookups based on Expressions defined in the Administrator tool that use the "Assumed from Base Table" Lookup Type. The problem has currently been identified when working with Oracle and Transoft systems but may occur with others as well. The problem does not occur for SQL Server, Pervasive or MS Access Databases.
Alchemex have confirmed this to be a problem and a fix will be available in the next release of Alchemex. Until the fix is available a workaround is outlined below: -
Locate the Expressions in the Container that are being used for the report Parameters and change the Lookup Type to "Customised SQL Statement" and press the Apply button. A property field called "Lookup SQL Select Statement" will appear. The statement will look similar to this example: -
SELECT DISTINCT "OrderDate" FROM "Orders" ORDER BY "OrderDate"
Fully qualify the fields in the SQL statement by prefixing both of them with the table name and a full stop. In this example change the SQL to : -
SELECT DISTINCT "Orders"."OrderDate" FROM "Orders" ORDER BY "Orders"."OrderDate"
Apply the changes by pressing the Apply button. This will rectify the problem.
- Alchemex Administrator