Good to hear you got it solved. I see your point, but I believe that parameters benefit you in many ways so I encourage you to use them. One idea that may come handy: Derive your own class from OleDbCommand and use that for database operations. If you need to see the statement and the values for parameters, create a helper method in derived class (of course you can separate this to a helper class). In that method list all the info you need to the output window. Something like:
public void WhatsInside() {
Debug.WriteLine(this.CommandText);
foreach (OleDbParameter param in this.Parameters) {
Debug.WriteLine(param.DbType + param.value + ...);
}
other possible info...
}
Added: This method can be called from immediate window while debugging so calls to it doesn't have to exist in code. Also this should be included only in debug builds. Mika
modified on Wednesday, September 10, 2008 4:41 PM
