I have a Crystal report that causes a database issue when I run it. The database is on a SQL server, and when the report runs, it causes the memory on the SQL server to rapidly decrease until I stop the report.
I originally had a subreport in this report, and thinking this may have been causing the issue, I totally redesigned the report without the necessity of a subreport. However, I am still having the problem.
I have isolated the issue to be the addition of a "third table" (GenVouchInfo) to the report which is part of the record selection formula. This "third table" is essential to the report, and cannot be excluded. However, whenever I add this table along with the selection formula, it creates the above issue.
Could I have an issue with how my tables are linked or how the formulas are structured? (see attached screenshots)
My joins are all "inner joins" to the "patient number".
Also, I am not using any commands, stored procedures or universe in my report. "Use Indexes or Server For Speed"
is turned on.
Thanks.
