Database Search
TechHome
 |
- !!NEWSFLASH!!
- 1437 or 3437 Extender Load Error
- 3132 error when using DAO
- 521 Attribute string too long
- Access SQL Update
- An SQL Tutorial
- Automated ODBC Data Source creation
- Calling a MS SQL Server 2000 Stored Procedure
- Change database then Update then count rows
- Compact an Access Database
- COMPACT_DB and Password MDB Files
- Continue a SQL Query after a Warning Message from Driver
- Create a System DSN for a TXT File Problem
- Create an SQL DSN with User name and Password
- DSN Connection Strings
- Execute an Oracle stored procedure
- Explanation of ODBC Usage
- Get Installed Driver Information
- Get Parameters from a Stored Procedure
- How Does qBindCol Work
- How to Do a Simple Sql Query
- Invalid Cursor State Error
- MDAC Invalid Object
- Microsoft SQL Server ODBC driver Info
- More on How ODBC Works
- ODBC and Services
- ODBC and SQL
- ODBC DSN Maker
- ODBC DSN Port Configuration
- ODBC Extender with WebBatch problems
- ODBC on 64 bit System
- ODBC SQLDescribeCol Example
- ODBC WHERE Syntax Blank Data
- Pervasive SQL Syntax Error
- Problem Adding System DSN for SQL Server
- Problem Using qConfigData with the Oracle ODBC Driver
- qConnect Crashes with Exit Code -1073741571
- qExecDirect and SQL Questions
- QExecDirect Second handle issue with SQL Server Drivers
- qFetch with Empty Cell
- qFetch with qBindCol and qGetData
- qGetData 50 columns limit
- qLastCode to Check these SQL Return Codes
- Read Information from Lotus Notes
- Retrieving data after a SQL JOIN
- Return Codes in ODBC Extender
- s0022 error from SQL Server Driver
- Specify SQL Server Password in qConfigData
- SQL Server SELECT SUM Statement
- SQL SUCCESS WITH INFO
- Syntax for Insert Into Access
- Updating ODBC.INI File over the Network
- Using WildCards in an ODBC SQL Statement
Can't find the information you are looking for here? Then leave a message over on our WinBatch Tech Support Forum.
SQL SUCCESS WITH INFO
Question:
Can someone remind me why we need to check the return code against both @qSuccess and @qSuccessInfo? Why the two values? What's the difference between them?Answer:
@Success is like "Hey It worked"@SuccessInfo is "It worked, but there is something you better know about"
Not sure but qError might be able to fish out the information if 2SuccessInfo is returned.
In my experience, the @SuccessInfo is benign [in terms of error]. It often is returned when fetching data with 'prepared' statements, the INFO probably reminding you it is prepared; or it may inform you that some 'null' values were returned; or it may have a timestamp 'hiccup'. Worse case might be an ODBC timeout, where everything was returned save the last row of data.
You might also see it commonly when you try to set a handle attribute which the driver doesn't support, or which is incompatible with some other attribute you set, and the driver manager changes the attributes from the ones you set. The diagnostic description is something like "attribute changed".
Article ID: W16344
File Created: 2005:02:18:12:19:56
Last Updated: 2005:02:18:12:19:56