Common Errors

Why are my runtime parameters not being passed though?

Check that the report's CLS file is in the default Exo Clarity directory (Custom or Masters, depending on which report you're trying to run).

Check that you don't have spaces in your parameters, e.g /S = MYPARAM = 12 will not work; you must remove the spaces: /S=MYPARAM=12.

Why do I get the message "Can't find Report Clarity.EXE"?

You can get this message when trying to run a Clarity report from a button or from a menu option if you have entered "Clarity.EXE" in the Command Line or Parameters field when setting it up. In the case of menu items and custom buttons, these fields should contain the report name and parameters only. 

Why do reports with the /I parameter still go to the default printer?

Check that you are using a valid UNC pathname, e.g. \\PRINTSERVER\PRINTER NAME. If an invalid printer definition is given, Exo Clarity will always resort to the default printer.

UNC names are derived from the list of available printers on the network as they appear in Windows Explorer.

You may also need to specify the Direct to parameter (/D) when using the /I parameter on a command line to tell Exo Clarity to skip the printer/file window that it calls by default.

What does the error "Invalid SQL statement, Ambiguous column name" mean?

This error occurs when you enter a query that is not able to recognise which table the field belongs to, usually because you have only specified the field name, and there are two or more fields with the same name in the tables that you have selected for the data source. In this case you must explicitly specify the table name, e.g.

Sum(dr_trans.subtotal / dr_trans.exchrate)