I did a sbmerge on a project a couple o'days ago.
It needed a new odbc-source so I included odbcad32.. ill post the complete entrypoint here, its a nice tip
http://Virtual ODBC Administration.exe
Source=%SystemSystem%\odbcad32.exe
Shortcut=
Anywho, the new ODBC-source (user) was then marked with isolationmode "sb_only" in hkcu.txt. When was this isolation mode introduced? (im using 4.0.3)
I thought that then this new odbc-info would only be read if it was located in the apps sandbox (for some reason) but no.
So whats the advantage with sb_only versus Full?
In my case the app had to be locked to a special odbc-source, pointing to a "test-database", therefore its critical that no physical-odbcsettings can be read since the production database looks the same/same credentials.