I have a pass through query that clears records on oracle table.
The connection string is long...and includes USerID and Password for access to the Oracle Table.
It works as intended.
However, down the road, the passwords will change and I will need to update about 150 pass-through queries from Access.
I know how to do this by concatenating a new Connection string with the new password embedded and then access the QueryDefs collection to find all my pass-throughs.
So I have a VBA script to this. So far, so good.
However I noticed that once I execute the Passthrough query in the Passthrough SQL environment in Access I can change the password in the string manually, or remove it completely and the PT query still executes successfully; I can write some other SQL code (to clear some other table) and it still works.
I find this very odd. Usually the problem is, "I can't connect"...what am I doing wrong. In this instance the password must be held in memory.
Anyone have an experience like this?
JayGBardo1