Member Login

Username
Password
Forget Password
New Sign Up
Search Forum

Buy Support
Incidents

If you can't find your answer in the FREE PUBLIC QDeveloper Forum, require URGENT Priority Support, or you need to send us private or confidential information:

Click Here
If you can't login and post questions or you are having trouble viewing forum posts:
 Click Here
Callback
Support

If you live in USA, UK, Canada, Australia or New Zealand, you can leave us details on your question and request us to call you back and discuss them with you personally  (charges apply).

Click Here
 
Buy Support
Incidents
If you can't find your answer in the FREE PUBLIC QDeveloper Forum, require URGENT Priority Support, or you need to send us private or confidential information:
Click Here

Forum : Alpha Five active link with Quick Books ProSearch Forum

Forum Home > QODBC - ODBC Driver for QuickBooks > QODBC v8 Forum

 New Topic 
 
 Post Reply 
[1]  
 Alpha Five active link with Quick Books Pro 
 Author   Message 
  Bill Semitekol 
  
 Group: Members 
 Posts: 4 
 Joined: 2008-10-05 
 Profile
 Posted : 2008-10-05 04:31:19

I am running Alpha Five Version 9 Platinum Edition and Quick Books Pro 2008.  When I Create a database from linked data in Alpha Five with the customer and vender files in Quick Books and try to update fields I get the following error message in both files.  The customer file has 1,856 records and the vendor file has only 3 records.

Server side error updating row.
Databse API specific error

Your databse has returned the following error code and descriptoin to Alpha Five.
Consult your database documentation for further information.

11015 - '[QODBC] Expected lexical element not found:)
SQL State is: 42000'
Refresh the data to see the current server values.

 

 

  Top 
  Tom 
  6c3c1_sdk-qodbc.gif
 Group: Administrator 
 Posts: 5510 
 Joined: 2006-02-17 
 Profile
 Posted : 2008-10-05 12:39:55
"Expected lexical element not found" simply means there's a syntax error in the SQL Statement being used. Look at the bottom of the QODBC log file in the Messages Tab of the QODBC Setup Screen for possible causes. 

  Top 
 New Topic 
 
 Post Reply 
[1]  

Jump to