DAO QueryDef refresh

[ATD]

Hi

I can easily use DAO to update the Connect value for a passthrough QueryDef
object in my database.

However, no matter what I "Refresh" (QueryDefs, TableDefs, Containers, etc),
the new Connect value is not actually used by Access until I reload the
application (not just the database, but the entire application)

Is there a way to force a full refresh?

If I make the change manually, everything works ok - however, I need to be
able to do this in VBA as I need to loop through thousands of external
databases, and changing the setting manually and/or reloading the application
is just not an options

Any thoughts?

 

[Stefan Hoffmann]

hi,

I can easily use DAO to update the Connect value for a passthrough QueryDef
object in my database.

However, no matter what I "Refresh" (QueryDefs, TableDefs, Containers, etc),
the new Connect value is not actually used by Access until I reload the
application (not just the database, but the entire application)

Is there a way to force a full refresh?

If I make the change manually, everything works ok - however, I need to be
able to do this in VBA as I need to loop through thousands of external
databases, and changing the setting manually and/or reloading the application
is just not an options

Any thoughts?

The question is: What kind of refresh or change of the connect string
are you talking about?

Connections or session are cached by Jet. The problem is te way Jet
identifies these sessions.

Consider this scenario: You are using a connection to an Oracle backend
using user name/password authetification. Then you can change the user
name and password combination in the connection and it is stored. But it
will only be used when this connection was not used before with another
user/password combination. Otherwise this existing session will be used.
The only way to "drop" these sessions is to close Access, not only the
current database.


mfG
--> stefan <--

 

[ATD]

Thanks, Stefan

There is no username/password for the connections as they are just thousands
of standalone FoxPro databases in numerous folders across our network.

Surely, there must be some way of getting Access to use the new Connect
setting? I don't particularly want to *manually* change the setting for each
database - that would take years!