Overly Persistent Linked Oracle Tables

  • Thread starter Thread starter David
  • Start date Start date
D

David

I'm helping to design an Access application that
include Linked Tables with an Oracle 8i backend.

When a user opens a query, form, or report that makes
use of that table, he/she is prompted for his Oracle ID
and passwork. Fine and dandy.

When the user closes that query/form/report, the
connection to Oracle persists, and the user is not prompted
again. That's not necessarily a bad thing, but our Oracle
DBA is complaining that that from the Oracle point of
view, the connection is persisting, and needs to be closed
when it's not in use.

So that the user isn't reprompted to reenter Oracle
account information, the plan is to store the user's
Oracle account information somewhere in Access, either a
hidden table or a static global variable.

Any suggestions?

(BTW, one of the requirements I've been given is that I
can't use DAO, but may use ADO.)

David
 
I would not use Access with those requirements.
Switch to .Net to get connection pooling.
 
Back
Top