I have found this formula to be pretty useful and not too taxing in terms of affecting the speed of the report.

cdate( tonumber(         left({ANY_DATE_FIELD},4)),
            tonumber(right(left({ANY_DATE_FIELD},7),2)),
            tonumber(right(left({ANY_DATE_FIELD},10),2)))

The #1 speed problem with Sage dates and Crystal is when people create Date parameters, and have selection formula s like:

pwFormatdate({sagedatefield}) between {?FromDate} and {?ToDate}

When you do this, Crystal has to retrieve ALL the records to calculate the values.  The much better way is like this:

{SageDateField} between Tonumber(ToText({?FromDate},"yyyyMMdd")) and Tonumber(ToText({?ToDate},"yyyyMMdd"))

The #1 speed problem with Sage dates and Crystal is when people create Date parameters, and have selection formula s like:

pwFormatdate({sagedatefield}) between {?FromDate} and {?ToDate}

When you do this, Crystal has to retrieve ALL the records to calculate the values.  The much better way is like this:

{SageDateField} between Tonumber(ToText({?FromDate},"yyyyMMdd")) and Tonumber(ToText({?ToDate},"yyyyMMdd"))

"between" does not work for us, but "in" does.  Just in case anyone else has that issue.

Oops, that was a typo, you're right.  I've been coding C# and SQL Views all day, I did that Crystal syntax from memory.

for added fun, we set the Date Parameter to allow a Range input so that you only need 1 parameter.  then you can use

And {SAGEDATE} In

  ToNumber(ToText(Minimum({?DateRange}), 'yyyyMMdd'))

  To ToNumber(ToText(Maximum({?DateRange}), 'yyyyMMdd'))