Yeah, we saw this over a year ago on some user-written reports. Customized stock reports are all fine, unless you add another non-Sage parameter.  I suspect it's because Sage reports like to have string parameters.  Look inside any xxRPT.INI, even dates are YYYYMMDD strings.

Yeah, we saw this over a year ago on some user-written reports. Customized stock reports are all fine, unless you add another non-Sage parameter.  I suspect it's because Sage reports like to have string parameters.  Look inside any xxRPT.INI, even dates are YYYYMMDD strings.

Thanks for confirming, Jay.  I had one last year and two in the last 2 months.  But my date parameters are working fine; it’s just numbers.  I usually use real date parameters for user input, and then convert them to numbers before using them for selection criteria.  But I can still take a date parameter and pop it onto the report, and it runs fine.  If i do that with a number parameter, even if there is no other reference to it in the report, that’s enough to cause unspecified error.