2good2btru
Programmer
i am developing a scheduler which would mail reports to clients
i am using RDC 7 with VB6, i am taking all the records available for all the clients and am preparing a report which would contain details of them all. i am using a clientside, static type recordset, and attaching this recordset to the datasource of the RDC component. the recordset is produced by a stored procedure, i have prepared the report using field definitions(ttx),
I am reading the records once for the first time, then am filtering the data according to a dynamic selection formula.
I want to reduce the database hit since i could be having about 10000-20000 clients to send reports to.
So the idea of clientside recordset. but still whenever i change the selection formula and read records, there is still a database hit, this i could realise by making an entry in a temp table whenever the procedure is called, there was always an entry on the table when i read the report changing the selection formula.
what could be the reason, where am i going wrong, what can be done to minimise the database hit.
i am using RDC 7 with VB6, i am taking all the records available for all the clients and am preparing a report which would contain details of them all. i am using a clientside, static type recordset, and attaching this recordset to the datasource of the RDC component. the recordset is produced by a stored procedure, i have prepared the report using field definitions(ttx),
I am reading the records once for the first time, then am filtering the data according to a dynamic selection formula.
I want to reduce the database hit since i could be having about 10000-20000 clients to send reports to.
So the idea of clientside recordset. but still whenever i change the selection formula and read records, there is still a database hit, this i could realise by making an entry in a temp table whenever the procedure is called, there was always an entry on the table when i read the report changing the selection formula.
what could be the reason, where am i going wrong, what can be done to minimise the database hit.