C
cefrancke
Is it better, in terms of memory and cpu processing time, to send a
form's .RecordsetClone to a report instead of reopening the same form
query/table by using the report's Record Source property?
I figure, in the case where the filtered forms recordset is what is
going to the report, why reopen the recordset, when it's available
through .RecordsetClone.
Attach that to the report, use the form's filter, and run the report,
no?
Thanks for any insight.
form's .RecordsetClone to a report instead of reopening the same form
query/table by using the report's Record Source property?
I figure, in the case where the filtered forms recordset is what is
going to the report, why reopen the recordset, when it's available
through .RecordsetClone.
Attach that to the report, use the form's filter, and run the report,
no?
Thanks for any insight.