Help on crystal
User Gary Kwok (email@example.com) posted:
I am using a java viewer to view a report. After click on the export
button and Export format drop down list appear, I selected a .csv
format. It is not working when the scripts is running, and I get the
Command Failure on line 34 of 'test' -
This is the part where user select the type of format to export:
Window SetContext, "Caption= Export", ""
ComboBox Click, "ObjectIndex=1", "Coords=150,13"
ComboListBox Click, "ObjectIndex=4", "Text=.csv"
EditBox Click, "ObjectIndex=1", "Coords=153,12"
PushButton Click, "Text=OK"
If anyone has any idea why this is not working properly, please let me
Re: Help on crystal
User (firstname.lastname@example.org) posted:
I've worked with the Crystal Viewer and the Crystal Web Viewer, which has
the same interface/functionality. I'm not sure if the java viewer you are
using is the same or not.
With the regular Crystal Viewer, when any of the export file filter DLL's
are missing you'll get a non-fatal error when the Export button is
clicked. I don't know why they don't wait for the user to select an
output file format, then just check for the required DLL.
In any case, here's how I test reports generated using either viewer:
1. Run report from "benchmark" environment that generates the expected
output and export to a place where master compare files are stored.
2. Open the report and find all lines that contain report DATE and TIME
(they are always the same on every line). Use Find/Replace to globally
replace all of these with wildcard values, e.g., "03/13/2002" to
"##/##/####", and "12:00:00PM" to "##:##:##?M". Note that date and time
formats are determined by Windows the date and time "style" settings (on
Windows 95, they're in the Regional Settings Properties dialog). If any
of these are specified using a single digit (e.g., for the HOUR), you will
need to use the "*" wildcard (e.g., "*:##:##:##?M").
3. Run report on the "test" environment and export to a place where output
files are stored.
4. Use the file compare function I wrote (with some options for ignoring
LINEFEED characters, which do not fall in the same place every time) to
compare the two files one line at a time, and print diffs to the test log.