Conference orarep::nomahs::dbintegrator_public_public

1098.0. "MAPINFO and SQRDB32 don't seem to like each other" by ORAREP::GIDDAY::BURKE (S'ti Dab ot Klat Sdrawkcab) Thu Oct 03 1996 02:45

    Hello everyone,
    
    
    I have a customer that is frustrated by the following situation, and is
    considering giving on DBI altogether - even though I think this is
    	not neccessarily a DBI problem. 
    
    The configuration is AXP VMS 6.1 Rdb 6.0-1, NSDS 3.0d on the server
    , the clients are Win95 using the SQrdb32 version 2.00.1
    
    The NSDS configuration seems fine, as SQL> based queries work 
    and on the clients, MSaccess7 linked tables appear to work very nicely.
    
    The main piece of client software is one I haven't used, known as 
    MAPINFO, a table mapping and Query tool. This is the customers main
    client for ODBC.
    
    There is only one RMS database being accessed, and when displaying 
    tables through MAPinfo, no columns are being interpreted - 
    
    We configured MAPinfo to looked at the linked tables in MSACCESS on the
    client, and everything is wonderful.
    
    Sounds a bit to me like the MAPINFO product  and SQRDB32 version 2.00.1
    dont get on too well.  am unaware of any updates or ECO's to the
    SQRDB32 driver that I can tell my customer about.
    
    I have on the way the odbc client tracelogs, that may be of some help,
    but it's difficult to know what to suggest.
    
    I discovered that MAPinfo has an iSQL of sorts - we attempted a select
    from one of the tables, and received an error message
    
    "Oracle ODBC function sequence error"
    "Unable to fetch records into table"
    
    Which unfortunately LOOKs like a Oracel ODBC problem.
    
    Anyone with any suggestions about where to head next?
    
    
    Regards,
    Ben Burke
    Sydney CSC
    

    
    Hi,
    
    I cross posted this to the odbc notes conference, and will reply if I 
    get a response.  I have no idea how to debug this problem.
    
    Sorry,
    
    dan

================================================================================
Note 1242.1               ODBC function sequence error                    1 of 1
JBALOGH                                              17 lines   3-OCT-1996 19:58
--------------------------------------------------------------------------------
    In ODBC, calls need to be done in a certain order. When they are not
    done in that order, a function sequence error occurs. 
    
    This is a pretty common error. A typical case is when an application
    has 2 or more cursors open on a particular connection and does
    something to cause an autocommit. In Rdb, a commit closes ALL cursors
    associated with the connection. Commonly, an application will not
    realize they closed all cursors and they try to fetch from a cursor or
    statment that was closed. A fetch from a statement that was not
    prepared and executed is out of sequence...
    
    This is almost always a problem with the application and NOT the ODBC 
    driver. The driver and client logs hold the key...
    
    Rdb7 has hold cursors that may help for some of these...
    
    John