I tried something different to get away from IF...THEN, or CASE...modifying the WHERE to use OR conditions (X, Y, and Z), but that didn't work either. Again, it does on SQL Server but the performance dropped off exponentially; query ran for 29 minutes in SQL Server before it displayed the dataset. Prior to using this method, it took 2-3 minutes using the IF....THEN statement on the server side.
Even if it worked in Crystal, this modification just isn't going to cut it either...its way too slow and my user's aren't going to want to sit around waiting for 30 minutes for a report that used to take 3.
Thanks for responding and trying to assist by sending me the link though. I already knew that about the parameters and double-clicking.... I deleted the DECLARE statements (variables) awhile back and am just using references to the prompt {?ReportType}. It didn't matter though...nothing works when using the {?ReportType} prompt.
It should not take 16 hours to work on this issue when it's so damn simple in logic. That shows how ineffective (or the lack of robustness) Crystal really is as a dynamic development tool.
I am very disappointed in Crystal as a report development product, but what else is there really (other than Access which too has extreme limitations in performance and scalability).
Anyway... I'm done bitching about this today...the frustration simply wore me out!
:0(