Vous êtes sur la page 1sur 2

ACL 9.

1 Known Issues December, 2007 Please note the existing list of issues and suggested workarounds within this release of ACL. For further information on any issues below, please contact the ACL Global Help Desk. Tracking Number

7741 7424

7253 7163 7137 6872

6602 6597

6588

6472

6372

Description and Suggested Workaround Import Excel may incorrectly interpret a numeric column as a date. This occurs only if both of the following conditions are met: Every value in that column conform to a single date format, i.e. YYYYMMDD. Every value in that column is a valid date according to that format. If encountered, modify the Excel file and insert a single record with a numeric value that does not match the above two conditions. This should be filtered out after Import. Import PDF may not align numeric values properly in some cases. The values may shift in position to the left or to the right by one or two characters. Ensure that all numeric values are captured by defining the field slightly wider than the numeric column. Running out of disk space while importing data may cause ACL to freeze. JOINs using fields from a related table is not supported. However, it is possible to JOIN on a computed field based on a related table. This can result in unexpected results and should be avoided. To execute a JOIN using a related table, first do an extract of the related table and then perform the JOIN to the new table. Importing Float Values from an ORACLE database where large values are represented by Scientific Notation produces an error when the exponent is a large value greater than 20. Ensure your data is formatted accordingly. If the percentage sign (%) is embedded in the data, it will not be exported in the XML file. If you have a standard application that has more than 350 lines, ACL can not always show it properly in the Standard Applications menu. Page width line within the View does not correspond to the Print Preview view or the printed report. The page width line on the view does not indicate what fields will be printed. It shows about twice the width of what is actually printed and what appears in the Print Preview. When the Field Notes begin with IF, ACL substitutes the condition in the Fields IF filter. If need be, begin the notes with a COMMENT on the first line followed by the IF characters. The CTOD function with no date format specified gives an error in the view if the field is empty. If the CTOD has no date format specified, the format YYYYMMDD or YYMMDD is assumed. However, if a field is blank and the CTOD function is applied, an error occurs in the field in the view and the field cannot be used in other functions. Users should specify the format when using the CTOD function. Running the SUMMARIZE command does not display related fields where the related field name is the same as the field being Summarized on. This only occurs when the related field is selected under the Other Fields option. If both fields are Summarized on, both fields will appear in the results. When you have the Automatically Profile on Open option enabled and the table has a default filter, clicking on the drill down link for the IF condition in the profile output repeats the filter condition over and over again. Running the commands separately does not show the IF condition in the results view. The Default Filter is shown in the IF syntax. Commands processing Text fields starting with the @ symbol causes error

Page 1

6297 5956

5855

5642 5537 5474

5305 5242

5104

4507

4021 2780

messages for XML output and problems in the log. The log creates a false positive entry for the command, followed by a failed entry. Users should insert a space before the @ symbol to prevent this behavior. The number of tables that can be copied from another project is limited to 56 at a time. Changing the orientation from File/Page Setup does not apply when printing the Result view. If you run a command and output the result to screen, then change the orientation to Landscape in the File/Page Setup dialog, then Print from the File menu, the report will print in Portrait mode. To print the report as formatted, navigate to the File/Print dialog and change the page orientation using the printer driver utility OR right-click on the Result View, then change the orientation, then Print. After running a Stratify without specifying any Subtotal, ACL will show the key numeric fields in the Subtotal column as well. The command syntax will not record any subtotal field. However, when you edit the command, the Stratify dialog will show that the key numeric field is also selected in the subtotal field list. If you remove it, ACL will still display Subtotal in the result. Report Fit to Page setting is not saved in the View parameters. Applying RECOFFSET() on a Static field will not display any Static fields when Extracted. If a Table has COUNT as one of the field names, performing a CROSSTAB command with the Accumulate parameter selected and Including Count will give the wrong COUNT result value. ACL confuses the reserved word COUNT and uses the value form the COUNT field instead. The Sampling Size Calculate button does not verify the user entered parameters and may result in incorrect results if the characters are input. Clicking the OK button will verify the user entered parameters and will report any errors. When you perform a STATISTICS command on a Date field, the results will display both Positive and Negative values that can be selected for drill down. If you click on these values ACL returns the error message Expression type mismatch since date can not be greater or less than zero. Running the Age command with Negative values for the Intervals returns incorrect Drill-down values when applied to a Graph. The resulting filter always displays AGE() < 0 as part of the filter regardless of which the interval the drill-down is being applied to. In addition, the Graph labels do not display this interval. Date, Logical, Date/Time Scientific Notation fields in a delimited file are not automatically defined by the Data Definition Wizard. The date fields are recognized as Numeric data type when dashes are used to separate the day, month and year. When the slash is used, ACL recognizes the field as ASCII text. Users must manually select these fields as Date format when importing the file. Multi-line View Report to HTML produces a file with all heading lines in the first row. This behavior does not occur when creating an ASCII report. Performing a Quick Sort on a Break Column in a view will output multiple instances of the key field value. This output will not occur with the Index command.

Page 2

Vous aimerez peut-être aussi