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.
Pervasive SQL Syntax Error
Question:
I'm having trouble with my script and would appreciate help on trouble-shooting it. Here is part of my script.
MyTableName="Order Master" ... ... retcode = qExecDirect(hstmt, "SELECT ORDNUM, PRTNUM FROM %MyTableName%")
My script uses ODBC functions to help me access the Order Master file for specific data. It keeps crashing with the error message "37000 [Pervasive][ODBC Client Interface][....]Syntax Error:SELECT ORDNUM, PRTNUM FROM Order<<>> Master"
I used the sample script that came with the ODBC extender. I know it works because it successfully displays the messages that appear before the script that is giving me the above error message.
Answer:
My guess is the problem is due to the ‘table name’ having a space in it. The format of "statement" will depend on the data source and driver. You will need to handle for the space in the ‘table name’, in the SQL string that you pass to qExecDirect.Other SQL Strings to try:
;retcode = qExecDirect(hstmt, "SELECT SHOPORDERNUM, PARTID FROM [%MyTableName%]") ;retcode = qExecDirect(hstmt, "SELECT SHOPORDERNUM, PARTID FROM '%MyTableName%'") ;retcode = qExecDirect(hstmt, 'SELECT SHOPORDERNUM, PARTID FROM "%MyTableName%"')
User Reply:
The last of line of your example is the correct one.retcode = qExecDirect(hstmt, 'SELECT SHOPORDERNUM, PARTID FROM "%MyTableName%"')Table names with spaces in them must be enclosed in double quotes within the query string. Literals, on the other hand, need to be in single quotes (apostrophes).
Article ID: W16342
File Created: 2005:02:18:12:19:56
Last Updated: 2005:02:18:12:19:56