Crystal for VS 2010 SP5, vb.net, winform.
I am changing the ODBC DSN in code that worked in SP4 but now is failing.
Tracing the table properties in debug mode shows that the table properties change as expected after this line:
TableN.LogOnInfo.ConnectionInfo = My_ConnectionInfo
But after calling the next line:
TableN.ApplyLogOnInfo(TableN.LogOnInfo)
All properties immediately revert to their original values, as shown in the picture below. Is this a known regression?
There are prior posts about this problem in past threads and on the web. For example:
http://scn.sap.com/thread/3201919
http://scn.sap.com/thread/1096512
After calling ApplyLogOnInfo, all properties revert to their original values:
Note: some past threads suggest building the Connection Properties collections completely from scratch. I can't pursue that strategy because my application can be used by different users for different types of ODBC connections. It seems reasonable to assume that we should be able to simply change the ODBC DSN without going through a process of recreating all connection properties. Or am I too optimistic... 