A
andrewsharpe
Guest
Thanks for the reply, Brody. Good suggestions. Your suggestion to supply the database name in the connection string makes sense, unfortunately I can't use it because the DSN is controlled by another application, so I have to rely on whatever value of the Database name has been set by that application (which my application doesn't know or control). I am connecting with Dotnet using the System.Data.Odbc.OdbcConnection class. I am simply doing: OdbcConnection conn = new OdbcConnection(); conn.ConnectionString = "SourceType=DBF;DSN= "; conn.Open(); ... conn.Close(); conn.Dispose(); In between calls to this block of code, another application may change the registry value mentioned in my first post. I put a breakpoint on the above conn.Open() call and check the registry value. It is always as it should be, therefore I know the issue is not with writing the value to the registry. But once I step over the line, the conn.Database property is sometimes the expected new value, but it is sometimes the old value. Is the DataDirect driver caching the database name? If so, can I control this via a connection string attribute? I know some drivers cache "meta data" so it doesn't have to be retrieved from the registry every time. If DataDirect is doing this, I need a way to turn it off... Thanks for your attention Brody! Andrew
Continue reading...
Continue reading...