• Replies 7 replies
  • Subscribers 337 subscribers
  • Views 30 views
  • Users 0 members are here
Related

Fighting with Infomaker

Frances O'Connell
$organization

Hi All,

I'm having a Friday afternoon fight with Infomaker.  Here's the situation - 

A Development staff member noticed a column in one of our customized reports malfunctioning this morning.  The column is an ask_amt on a customized Solicitation Report, and the report was presenting dollar amounts that were no where in the constituent record.

I am, to say the very least, an Infomaker rookie, but preferred fixing this one column instead of building the entire thing in SSRS, so I opened up the report template.  I checked the column specifications, and the column in question was still pointing toward the correct db field.  I deleted the column from the report and the column specifications, and reinserted to both.  I tried R-click, Retrieve to preview the report, and Infomaker shut down.  I reopened, and was able to preview, and there was incorrect data in the Ask Amount column I had added.  Different incorrect information than before.

I executed the SP that is the data source, and the Ask Amount is behaving perfectly in fine in SSMS.  

While testing this I've tried running the report out of the application a few times and have had varying bad results - the client will crash, or the report will generate, with totally incorrect information in this one column. 

What am I missing??? 

Any help MUCH appreciated!

Frannie

Parents
  • $organization

    Hi, Frannie:

     

    When I’ve had this issue, it’s because the data being pulled by InfoMaker doesn’t match what’s coming out of the stored procedure.

     

    Make sure that the Infomaker report’s column specifications screen lists all the fields, in the same order, as the stored procedure’s output. If not, your data misbehaves.

     

    Lucie

     

    ______________________________
    Lucie Spieler
    IT Development and Training Manager

    FLORIDA GRAND opera

Reply
  • $organization

    Hi, Frannie:

     

    When I’ve had this issue, it’s because the data being pulled by InfoMaker doesn’t match what’s coming out of the stored procedure.

     

    Make sure that the Infomaker report’s column specifications screen lists all the fields, in the same order, as the stored procedure’s output. If not, your data misbehaves.

     

    Lucie

     

    ______________________________
    Lucie Spieler
    IT Development and Training Manager

    FLORIDA GRAND opera

Children
  • $organization in reply to Lucie Spieler

    Lucie,

    Thank you so much.  I will never be so cavalier with my column specification order again.  I was about to put my fist through the screen. Everything is working now in Infomaker Preview - but it's still not functioning in Tess.  Report Set-Up all looks ok, but the client crashes when I run the report.  Have you had this?  Either way thank you so much for the tip!  Thrilled I can see it working somewhere.