Sage 100

 View Only
  • 1.  Sage 100 Standard V2015 PU3 - recently upgraded.

    Posted 06-21-2016 11:20
    Sage 100 Standard V2015 PU3 - recently upgraded. Customer goes into report manager - can run and view report with data. Attaches to menu. Goes to run off the menu - no data. Tried: - Remove report from menu - Re-add report from menu - No luck - Add some static text to report to be sure running same report - checks ok Thoughts as to why the report shows no data when run from Sage 100 Custom menu?


  • 2.  RE: Sage 100 Standard V2015 PU3 - recently upgraded.

    Posted 06-21-2016 11:26
    ODBC security?


  • 3.  RE: Sage 100 Standard V2015 PU3 - recently upgraded.

    Posted 06-21-2016 11:30
    Do you have parameters that link to data in a sub report? I think that will cause what you are seeing


  • 4.  RE: Sage 100 Standard V2015 PU3 - recently upgraded.

    Posted 06-21-2016 11:38
    Looks like it may be a formula problem on the customer side


  • 5.  RE: Sage 100 Standard V2015 PU3 - recently upgraded.

    Posted 06-21-2016 11:43
    For some reason the full version of Crystal is evaluating a formula that extracts the year as 2016. When we view it off the Sage menu that same field becomes 2,016.00. We set the default for numbers to be -1234 but seems to ignore in the runtime/reports menu


  • 6.  RE: Sage 100 Standard V2015 PU3 - recently upgraded.

    Posted 06-21-2016 12:01
    As a work around, might suggest re-writing the formula to use Totext() function on the extracted year... you can set the parameters for number of decimals and thousands separator and end up with a string of '2016' --- perhaps that will serve your needs?


  • 7.  RE: Sage 100 Standard V2015 PU3 - recently upgraded.

    Posted 06-21-2016 12:04
    Thanks, Randy - he was using the ToText formula which made the whole thing a bit weird. There appears to be some difference between what the default numeric field mask will be with full Crystal vs the Run Time. At least that's the closest I can come to explaining the issue. He is going to look at it further now that we figured out the initial issue.


  • 8.  RE: Sage 100 Standard V2015 PU3 - recently upgraded.

    Posted 06-21-2016 12:06
    My experience with Totext() is you are always better off specifying the number of decimals and separator. They are optional, but I never leave them out... too much weird crap can happen!!!