vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hi! I'm updating a Windows application that we develop that uses a DB2 database. We switched from using Microsoft Developer Studio 6 to Visual Studio .Net 2003 to build our app and since that switch, we've been getting a function sequence error with this SQLSTATE: State:S1010,Native:0,Origin:[Microsoft][ODBC Driver Manager] Here is a sample query we're running that generates the error UPDATE TOM.USERS SET TYPE=TYPE WHERE 1 = 0 The strange part is the Microsoft ODBC driver manager is reporting the error even though we're using the IBM ODBC driver. Any ideas on where to start troubleshooting this? Thanks! Peace... |
| |||
| tommydkat@gmail.com wrote: > Hi! I'm updating a Windows application that we develop that uses a DB2 > database. We switched from using Microsoft Developer Studio 6 to > Visual Studio .Net 2003 to build our app and since that switch, we've > been getting a function sequence error with this SQLSTATE: > > State:S1010,Native:0,Origin:[Microsoft][ODBC Driver Manager] You might want to consider using the DB2 CLI driver. From what we read here once in a while, the MS driver shows some strange problems once in a while. If the DB2 CLI driver is not an option, you should ask your question in a MS newsgroup. > The strange part is the Microsoft ODBC driver manager is reporting the > error even though we're using the IBM ODBC driver. Any ideas on where > to start troubleshooting this? If it says MS ODBC driver, then you are not using the IBM driver. -- Knut Stolze DB2 Information Integration Development IBM Germany |
| ||||
| Well, I've got this problem figured out. It wasn't the Microsoft driver at all. It was a change to the MFC CDatabase::ExecuteSQL() function. In DevStudio 6, it didn't throw a CDBException when a query returned an empty result set. In Visual Studio .net 2003 it does. Peace... |