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 : S0000: [QODBC] No data found (when looking up related table)Search Forum

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

 New Topic 
 
 Post Reply 
[1]  
 S0000: [QODBC] No data found (when looking up related table) 
 Author   Message 
  Reptcon 
  
 Group: Members 
 Posts: 3 
 Joined: 2007-04-06 
 Profile
 Posted : 2007-04-12 09:57:54

I'm using Progress ODBC DataServer (v9.1D) with QODBC 7.00.00.207, with Quickbooks Enterprise 7 trial version.

When I iterate on the TRANSACTION table and lookup related ENTITY, there are some records in the sample database which have non-null transaction.EntityRefListID fields but no related ENTITY records.  The read fails.  Control flow should return to the program (with an error condition) so that I can handle it programmatically.   I might want to create the missing record if not found.

However, when this happens, Progress stops as if a fatal error had occurred.

I experience the same problem whether I use Progress ABL code or SQL.

Any ideas?  I noticed "continueonerror" in some of the traces I looked at.  That's exactly what I want the driver and program to do!

Code is inserted below (Progress ABL/4GL which DataServer translates into SQL to pass to the driver)

TIA for any insight you might be able to provide. 

Chris

=====================================

FOR EACH {&QB}.TRANSACTION_:
    DISPLAY {&QB}.TRANSACTION_ EXCEPT memo
    WITH 1 COLUMN
    FRAME f-5A DOWN STREAM-IO WIDTH 500.
   
    if {&QB}.transaction_.EntityRefListID <> ? THEN DO:                           
   
    /* FOR FIRST */ FIND {&QB}.Entity
    WHERE entity.listid = TRANSACTION_.EntityRefListId NO-LOCK NO-ERROR.
   
    IF AVAIL ENTITY THEN DISPLAY entity
    WITH 1 COLUMN FRAME f-5B STREAM-IO WIDTH 500.
   
    /* END. /* for first */ */
   
    END. /* if */
END.

 

 
Report Concepts, Inc.
Far Hills, NJ 07931 
 
  Top 
  Tom 
  6c3c1_sdk-qodbc.gif
 Group: Administrator 
 Posts: 5510 
 Joined: 2006-02-17 
 Profile
 Posted : 2007-04-12 11:20:26

Sorry, you haven't shown the SQL that DataServer has generated, but not every Transaction line has an Entity. This query executed without any issues using NULL instead of <>:

SELECT * FROM Transaction, Entity where Transaction.EntityRefListID=Entity.ListID
and Transaction.EntityRefListID is not null

 

  Top 
 New Topic 
 
 Post Reply 
[1]  

Jump to