Database Search
If you can't find the information using the categories below, post a question over in our WinBatch Tech Support Forum.
TechHome
ODBC
 |
- !!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.
Calling a MS SQL Server 2000 Stored Procedure
Question:
I've got a stored procedure that does some complex query work and returns a rowset. I do all the allocations, and connections just fine, and then try:
retcode = qExecDirect(hstmt,'ExpressPassDays')
If (retcode != @QSUCCESS) && (retcode != @QSUCCESSINFO)
Message("qExecDirect failed", retcode)
Exit
EndIf
It hits the error and terminates. I've tried making the SQL statement argument an Execute() statement with a variety of
quote formats; no joy.
The stored procedure works fine from SA with the same credentials and from Excel with the same ODBC datasource, just not from Winbatch.
Answer:
I recommend calling qError(hstmt, 2) and displaying the output. It should explain why it doesn't like that stored procedure (SP).Maybe try:
retcode = qExecDirect(hstmt,'{call ExpressPassDays}')
Or
retcode = qExecDirect(hstmt,'{execute ExpressPassDays}')
User Reply:
That got me there. For anyone who needs to do this:Even though the ODBC datasource points to the database where the stored procedure lives I had to call the fully qualified name. Before I added the fully qualified name the error message indicated that the ODBC driver was unable to find the stored procedure. That is, given that the stored procedure exists in a DB named 'JHMR_Custom':
retcode = qExecDirect(hstmt,'ExpressPassDays')failed, but
retcode = qExecDirect(hstmt,'JHMR_Custom.dbo.ExpressPassDays')succeeded.
Thanks!
Article ID: W16835
File Created: 2007:07:03:14:26:28
Last Updated: 2007:07:03:14:26:28