<= Previous | Next => | Table of Contents | DataVision FAQ |
Yes. Use the comma- or tab-separated export formats. Excel can easily read either one. A hint: use the extension ".csv" for comma-separated files and ".txt" or ".tab" for tab-separated.
This question and its answer have moved.
Not directly. You can modify the query's where clause by using the "Select Records" dialog, modify the sort order of columns by using the "Sort By" dialog, and modify record grouping by using groups.
To add your own SQL to the SELECT clause, create a user column and edit its code. The code you put in the user column becomes a column in the SELECT clause of the SQL query. For example, if you define a user column with the text "my_stored_proc({?My Parameter})" then the SQL query will look something like
select col1, col2, ..., my_stored_proc(the param value)
from table1, table2, ...
where ...
When you create an image field using the DataVision GUI, the absolute (full) path name of the file is saved and will be inserted into the HTML image tag's "src" attribute.
If, however, you edit the report XML manually and use a relative file path, that relative file path will be used in the image tag. If you save the HTML output in a different directory than the DataVision application, the image won't be displayed because the relative path name will be incorrect.
I plan to fix this in a future relase. For now, you can edit the HTML and fix the image tag.
Sometimes fields that are displayed from left to right correctly in the Swing report window don't come out in the same order when you use the HTML or character (comma- and tab-separated) layout engines.
Because those layout engines can't place columns visually, the fields are sorted first by their Y coordinate (height) and then by their X coordinate (left-to-right position). That means if one of your columns is even one pixel higher than the others, it will be output first.
Make sure all the fields in a section have the same Y coordinate. You can either use the "Align" feature of the GUI to align the fields' tops or you can edit the report XML file directly.
Fixing DataVision to handle this situation would be non-trivial. I'd have to add some fuzzy logic that said "this column is close enough to all the others that I shouldn't output it first just because it is only one pixel higher."
<= Previous | Next => | Table of Contents |