VB interfaces with Oracle 8i?
DBAsupport.com Forums - Powered by vBulletin
Results 1 to 6 of 6

Thread: VB interfaces with Oracle 8i?

  1. #1
    Join Date
    Nov 2000
    Posts
    162

    Unhappy

    Does anyone know if VB interfaces with O8i? If it does can you tell me how does it work? Thanx.

  2. #2
    Join Date
    Nov 2000
    Location
    greenwich.ct.us
    Posts
    9,092
    Most definitely.

    Typically, you will access Oracle through either an ODBC driver or throught another product such as Oracle Objects for OLE.
    Jeff Hunter
    marist89@yahoo.com
    http://marist89.blogspot.com/
    Get Firefox!
    "I pledge to stop eating sharks fin soup and will not do so under any circumstances."

  3. #3
    Join Date
    Nov 2000
    Posts
    162
    Thanks Jeff, that is helpful!

  4. #4
    Join Date
    Nov 2000
    Posts
    162
    By the way, what is OLE? What is it for?

  5. #5
    OLE=Object Linking and Embedding
    I think OO4O (Oracle Objects for OLE) uses ODBC.
    If you want to avoid ODBC (a little slow) you can use OCI (Oracle Call Interface)
    OLE was a Windows way to link processes (I guess now is ActiveX) Excel is an OLE Server and can embed a Powerpoint slide (another OLE Server)
    Ramon Caballero, DBA, rcaballe@yahoo.com

  6. #6
    Join Date
    Aug 2000
    Location
    Belgium
    Posts
    342
    OO4O uses OCI and not ODBC

    extract from metalink :

    Q: What is Oracle Objects for OLE?

    Oracle Objects consists of three components:

    * An OLE 2.0 Automation (InProcess) Server which provides an OLE
    Automation interface to applications that support OLE automation
    scripting such as Visual Basic (VB). This means that it can be used in
    place of the database function calls normally used in VB and the syntax
    used is as close as possible to VB's own database function calls
    for easy porting. (Porting is not required as it can exist side-by-side
    with exiting VB database code) Unlike VB's normal database function
    calls which use ODBC, Oracle Objects for OLE is implemented using the
    Oracle Call Interface. Because ODBC is not used, users are not subject
    to the very serious limitations that ODBC places on Oracle users. (See
    below for a description of these ODBC limitations.)


    * The Oracle Data Control, which is a Visual Basic custom control (VBX).
    This is designed to be a clone of Visual Basic's built-in data
    control. The data control can be used in tandem with "Data Aware
    Controls" (Grids such as Apex TrueGrid, or VB's Image Control for
    example) which allow funneling of data to and from the data aware
    control to the database with little or no coding. Rather than using
    ODBC however, the Oracle Data Control uses OCI. You can replace the
    VB data control used in exiting apps with the Oracle data control very
    easily.


    * Two C++ Class Libraries, one for Microsoft Foundation Classes (MFC)
    and the other for Borland (OWL). These libraries encapsulate the
    OLE Automation Server interface and objects, and also provide a
    "Binder" class. These libraries do not require OLE knowledge nor
    the OLE development kit. Their classes, members, and functions
    are virtually identical to the ones found in Visual Basic.
    The "Binder" classes are a significant improvement over the
    Microsoft ODBC classes; the Microsoft classes force "early binding"
    which means you must know your select statement at design time
    before you can bind an object to it, while the Oracle classes will
    allow "late binding" where the select statement is not known until
    runtime.


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width