Sage 100

 View Only
  • 1.  Sage 100 v4.4 to Sage 100c 2016 - I'm getting quit

    Posted 09-19-2016 07:35
    Sage 100 v4.4 to Sage 100c 2016 - I'm getting quite a few ""this report must be converted"" for canned reports (standard). This is new behavior as I've only previously seen the message for custom reports.


  • 2.  RE: Sage 100 v4.4 to Sage 100c 2016 - I'm getting quit

    Posted 09-19-2016 07:46
    Do you usually run the Crystal mascrcw.exe utility? You shouldn't have to. I wonder if they installed properly?


  • 3.  RE: Sage 100 v4.4 to Sage 100c 2016 - I'm getting quit

    Posted 09-19-2016 08:43
    I haven't found that Standard reports require MASCRCW. This customer is getting the prompt in numerous standard reports which is different than what I've experienced in prior upgrades.


  • 4.  RE: Sage 100 v4.4 to Sage 100c 2016 - I'm getting quit

    Posted 09-19-2016 08:58
    They shouldn't. Just a comment. Looking at the standard reports, do they say ""converted to v5.3? Also, this is 100c. Could this be the issue? Maybe a bug limited to c conversions?? When c was released, I had issues importing into PR. Revert to Classic and the problem went away.... Go figure.


  • 5.  RE: Sage 100 v4.4 to Sage 100c 2016 - I'm getting quit

    Posted 09-19-2016 09:01
    It could be a c issue. This customer had their keys dynamically changed when we migrated from 100 to 100c before the upgrade was live. I'd be willing to bet that the pool of people who are doing an upgrade at the same time as they have the keys automatically updated is fairly small.


  • 6.  RE: Sage 100 v4.4 to Sage 100c 2016 - I'm getting quit

    Posted 09-19-2016 10:09
    What triggers the conversion is a difference between the Key= in mascrcw.INI and the version number from the Keywords in the Rpt file. Maybe the INI file changed with PU2.