L
Lester Lane
Hi all,
I have some procedures that are called by other routines that are
themselves churning through recordsets. As these called procedures
open a recordset, manipulate data, save data, and close the recordset
it must be quicker/slicker to do this once instead of for each
record. So rather than call these procedures for each record (if and
when it is required by the calling proc) which is the best method to
bundle up the data and send it once at the end of the calling proc
once it has completed processing its own recordset? Hope you're still
with me!
- Global array based on a User Defined Type
- Build a recorset and then send it as a parameter (I don't get this
as a recordset is physically linked to a table and not just memory -
is that right?)
- something else
I'm using DAO 3.6 and would also like a view on whether I should try
ADO instead even though it would be to linking a split mdb file, and
of course a different language that I have not tried yet! Thanks in
advance.
I have some procedures that are called by other routines that are
themselves churning through recordsets. As these called procedures
open a recordset, manipulate data, save data, and close the recordset
it must be quicker/slicker to do this once instead of for each
record. So rather than call these procedures for each record (if and
when it is required by the calling proc) which is the best method to
bundle up the data and send it once at the end of the calling proc
once it has completed processing its own recordset? Hope you're still
with me!
- Global array based on a User Defined Type
- Build a recorset and then send it as a parameter (I don't get this
as a recordset is physically linked to a table and not just memory -
is that right?)
- something else
I'm using DAO 3.6 and would also like a view on whether I should try
ADO instead even though it would be to linking a split mdb file, and
of course a different language that I have not tried yet! Thanks in
advance.