Ken,
Thanks you tones for the answers...
I am connecting via ODBC to an SQL server that our company is just developing ( see
). The database server is called M3 (is written in MUMPS language)
What I am trying to accomplish is:
1. To select the last (newest) patients records from a database (using a certain account # as reference - in my case 6580).
2. Also I have some parameters that I am using.
I hoped that once the data is brought in by the main report, the subreport would just process it's own output (I have a selection formula there too) from the main report's data.
But I understand from whet you are telling me that this is not possible since the subreport sends its own SQL query to the database.
This explains why I always saw a double request on the SQL server...
Is this a smart concept? I am trying to learn too... Wouldn't be easyer and faster if the subreport would take the data already brought in by the main report?
Also ultimately but most important I am trying to speed up the whole process by forcing as much as I can down the server...
Right now, I receive ALL records, and only then the "Patient.Patient_# >= 6580" is applied.
I tried to override the selection formula by hand editing the SQL formula. Sometime worked, sometime not.
What I really would like to learn is some smart concepts about making my reports efficient (processing as much as it could on the server).
Thanks again for putting up with newbies like me...
Gabi.
I have an example ready to be downloaded @:
ftp://pattersongray.com/misc/dnc/New_Patient_listing_SQL.rpt