Interbase/Firebird - SQL Enduser Tables - Problem with Item Table
Having created a separate DB for enduser reporting and added a folder and
subfolder and a couple of reports, I found that 7.02 reported an error
"Unable to convert to integer". Looking at the data in the "rb_item"
table, iI noticed the entries for a couple of incomplete reports ( where the
"folder_id" = -2) had a null value for "item_size".
I suggest a default of 0(zero) be used in the script to avoid this problem
OR the posting always ensures that the column has a value OR a test for a
value be placed in the code. (module ppRptExp.pas - line 3424)
Thanks.
Trevor Watters
subfolder and a couple of reports, I found that 7.02 reported an error
"Unable to convert to integer". Looking at the data in the "rb_item"
table, iI noticed the entries for a couple of incomplete reports ( where the
"folder_id" = -2) had a null value for "item_size".
I suggest a default of 0(zero) be used in the script to avoid this problem
OR the posting always ensures that the column has a value OR a test for a
value be placed in the code. (module ppRptExp.pas - line 3424)
Thanks.
Trevor Watters
This discussion has been closed.
Comments
If you use the ReportExplorer component, as shown in our end user demos, to
add the folders and items, does it ever create this condition on the
database?
Cheers,
Jim Bennett
Digital Metaphors
http://www.digital-metaphors.com
info@digital-metaphors.com
I was using your Interbase IBObject enduser application to see how it worked
and given that the application did not always exit normally, it could have
partially completed a post.
My suggestions simply provide a failsafe to avoid a non detected condition
producing a show stopping error, regardless of how it was created..
Kind regards,
Trevor
Cheers,
Jim Bennett
Digital Metaphors
http://www.digital-metaphors.com
info@digital-metaphors.com