I have implemented an external config file that contains client specific ODBC connection strings for the data loads.
Utilizing the QVScrambler.dll I can programatically scramble the username and password and store these values.
My fear is that someday QVScramler.dll might go away, and I'll be left with unscrambled data (short of keeping a local version of the dll and distributing it).
My question is: Is the code that scrambles/unscrambles just some .net method? or is it some proprietary QV routine?
I find it strange that externalizing the connection string isn't a commonly requested feature, eliminating the need to open up a qvw and modify it during deployment.
