P
Pierre
Hi all,
I have a form that is displaying data from a table A.
When the user is filling the form, i have to make a seek in an another
table B to fill a certain field.
Actually, each time the seek is made, we create a recordset from table
B, perform the seek, then close the recordset.
(This is based on example of program we saw in documentation.)
My question is:
Would it be better to open the recordset B when the form is loaded
let it open and made the search when necessary and simply close it when
the form is closed?
I saw number of example where recordset are open and close immediately
after an operation. Is there a reason?
I use to program in clipper where you open the files one time at the
beginning of a module and close them when the module terminate.
Table B is shared with an other application.
Regards
Pierre
I have a form that is displaying data from a table A.
When the user is filling the form, i have to make a seek in an another
table B to fill a certain field.
Actually, each time the seek is made, we create a recordset from table
B, perform the seek, then close the recordset.
(This is based on example of program we saw in documentation.)
My question is:
Would it be better to open the recordset B when the form is loaded
let it open and made the search when necessary and simply close it when
the form is closed?
I saw number of example where recordset are open and close immediately
after an operation. Is there a reason?
I use to program in clipper where you open the files one time at the
beginning of a module and close them when the module terminate.
Table B is shared with an other application.
Regards
Pierre