Conference orarep::nomahs::odbc_rdb_driver

    
    	The latest drivers is 2.10.1100 and you can get it from either
    	MetaLink or http://www.oracle.com/products/servers/rdb/html/odbc
    	on the web, or out of SQLSRV$ODBC on a server running Rdb7 7.0
    	(if it is prior to 7.0 they'll be an older version there).
    	  
    	Run the self-extracting executable you download with the -d 
    	switch (e.g. RDBNTX86.EXE -d) in a directory with nothing else 
    	in it and then run the SETUP program out of the \install directory 
    	where you unpacked it.
    
    	If things don't work out better for you let us know.
    
    	Regards,
    	rcs
    

    Hi, I have installed version v2.10.11 of the RDB ODBC driver and this
    has had no impact on the poor performance with visual Basic 5.0. Do you
    know who the oracle/odbc contact is for Digital ? thanks,
    Irene

    Since the upgrade to Visual Basic has caused the problem, I hope you
    are talking to Microsoft about this.
    
    Visual Basic's data objects have never been terrible efficient. They
    were at least 4 times slower than direct calls to ODBC routines in VB3.
    
    Rdb7 has an option to allow cursors to be kept open across a commit.
    This was added specifically for tools like Visual Basic and MS Access,
    to improve performance when multiple tables are being accessed.
    
    Peter

    
    If DAO is slow, have you tried comparing it to RDO or native ODBC ?
    What about running the same SQL through the ODBC test program ?
    
    Regards,
    rcs
    

    the odbctest program seems to retrieve the data in acceptable timeframe
    for up to 100 row chunks.
    I've also attached the rdb tables using Access 7.0 and the same
    performance issue exists there. I am already using RDO in my vb code.
    Another person in the group is using the remote data control to
    retrieve his data and is also experiencing a similar degradation in
    performance going to VB5.0. 
    I'm really not wild about the idea of redoing my code to use native
    odbc calls given my schedule for deliverables and the fact that it
    performs well using VB4.0. The advertisements for VB5.0 state that
    performance would improve. That was my motivation for going to VB5.
    Any other ideas? thanks,
    
    Irene

    You should look at SQL trace files to see exactly what statements are
    being issued. If the performance went down as far you you have stated,
    it sounds like VB has changed your SQL statement and could possibly be
    retrieving the table sequentially and performing sort operations on the
    PC. This has been a problem with VB and Access in the past. You may
    want to try the query with dbSQLPassThrough (64). 
    
    As someone stated earlier in this string, if the performance problem
    began by upgrading Microsoft VB, why are we blaming the Oracle ODBC 
    driver. You need to work with Microsoft... I saw the sales hype for 
    VB5 too. They are saying it is up to 20 times faster. Your observations 
    seem to indicate this is not the case...
            
    John
    
    

    Thanks John,
    
    I have contacted microsoft about this problem and they told me they
    would get back to me. I'm also already using sqlpassthrough. I was
    hoping someone else in this conference had tried vb5.
    
    Irene

    Mistery Solved with John Howard's help. The ODBC manager "don't trace
    option button" is clicked and yet tracing was still going on. Must
    click apply before closing for it to work correctly. 
    
    Irene