Agreed - wrong/weird.  To work around it for your client, try changing your report to use two separate parameters rather than a Range parameter, and see if it behaves normally.  To troubleshoot to convince Sage to look into it, try creating a very simple report to run in SAMINC or SAMLTD with a date range parameter.  If that works fine, then the range parameter is not the issue.  If it has the same problem, that confirms that it's not about your report - so MAYBE Sage would be willing to investigate....

It definitely worked to change the report to use two parameters and eliminate the date range parameter. Still, there are a large number of crystal reports that worked in the old version and now need to be modified, so it is not a great solution. 

It definitely worked to change the report to use two parameters and eliminate the date range parameter. Still, there are a large number of crystal reports that worked in the old version and now need to be modified, so it is not a great solution.