If you make the appropriate changes to the selection formula, it should not adversely affect the whole report.  What problems are you having after changing the parameter from a number to a string?

Question is more to  - Why is the error on this report only happening on certain WS not all.  Seems like a technical issue not a parameter issue and nothing in the KB was valid for this error.  Still wondering .

You post is a bit short on details as to what is happening.  I understand you are getting unspecified error.

Can you be a little more specific as to the situation?

.

I ran into this error last week, but for a converted report.  Must be something with the new CR run-time.  A report which worked in CR designer failed when run as a custom report (with the UNSPECIFIED ERROR).

My reports are custom reports for PR created in version 2018, not converted from a pervious version. (KB  89925) The same report reports run fine on certain workstations and get the error on others. IT has checked the <net versions as recommeneded by Sage THe only difference is the OS running on these machines- WIn 10 (good) or Win7 (bad)

Hi, Can you create a case with Sage Support and e-mail in the .RPT?  Note in the case to send the .RPT to John Nichols and I'll take a look.

John Nichols

Sage

Yes I have a case number already but it is any custom report that was written for new PR in 2018

All Run fine on Win 10 ws not on Win 7 or old server. Thank you for your offer to look at it John but since it is all of them not sure what we would look for.

I was getting this error on several of my reports and as you mention, I converted all parameters that were numbers to strings.  But once you do that you also need to change any formulas referring to that parameter to convert the string back to a number with tonumber().  I hope this helps.

Thanks for keeping this thread going long enough to get an answer.  I did try that with one report and it was such a pain I gave up. HOW CAN IT BE THE PARAMETER. and why would I do that much work. This is cost prohibitive when it works on another workstation fine, They have a lot of custom PR reports and most are asking for a month in the date range or some part of a fate range.

Thanks again

Try verifying that the workstations are using the same ODBC driver (some may be using CS version).  Just a thought.