Re: Access 2003
I have an access app that connects to two Oracle tables via VBA only
and retreives data via SQL and loads it into recordsetA. The
retreival from Oracle only takes about 10-25 seconds.
My goal here is to not leave anything "connected under the rug" to the
production Oracle backend DB after my data is collected that I
need. I just don't want my app to cause any slowdowns with the
Oracle back end DB.
Which is more efficient:
1) Use RecordsetA with Oracle to get the data, then use RecordSetA
throughout the application (which leaves the Oracle connection open
after I received all of my data)
OR:
2) Use RecordsetA with Oracle. When the data extract is done, dump
all of the data from RecordsetA into RecordsetB, close and destroy
RecordsetA and continue working with RecordsetB throughout the life of
the application.
I'm guessing that with this option here, when RecordsetA is closed and
destroyed, the entire link to Oracle is truly "disconnect ed",
correct?
Thanks.
I have an access app that connects to two Oracle tables via VBA only
and retreives data via SQL and loads it into recordsetA. The
retreival from Oracle only takes about 10-25 seconds.
My goal here is to not leave anything "connected under the rug" to the
production Oracle backend DB after my data is collected that I
need. I just don't want my app to cause any slowdowns with the
Oracle back end DB.
Which is more efficient:
1) Use RecordsetA with Oracle to get the data, then use RecordSetA
throughout the application (which leaves the Oracle connection open
after I received all of my data)
OR:
2) Use RecordsetA with Oracle. When the data extract is done, dump
all of the data from RecordsetA into RecordsetB, close and destroy
RecordsetA and continue working with RecordsetB throughout the life of
the application.
I'm guessing that with this option here, when RecordsetA is closed and
destroyed, the entire link to Oracle is truly "disconnect ed",
correct?
Thanks.