Description
This bug is normally hidden from view because the function ODBCCPlApplet() found inside of odbccp32.dll doesn't do anything visual to the user. But if you place a MessageBox() within the function, the behavior becomes quickly apparent. What happens, is that the applet (odbccp32i.cpl) doesn't first check to see if the user has clicked on it or not (CPL_DBLCLK from uMsg) and therefore runs ODBCCPlApplet() without user input. I have provided a patch that should fix this issue, along with tabs->spaces.