From: rcoates@telerama.lm.com Newsgroups: comp.lang.basic.visual,comp.databases.oracle Subject: Re: VB -> ORACLE on UNIX Followup-To: comp.lang.basic.visual,comp.databases.oracle Date: 9 Sep 1994 06:45:54 -0400 Organization: Telerama Public Access Internet, Pittsburgh, PA Lines: 26 Message-ID: <34ped2$7t4@africa.lm.com> References: <34eick$4b0@mydear.csl.sni.be> <34f8ad NNTP-Posting-Host: africa.lm.com X-Newsreader: TIN [version 1.2 PL2] I have used the Oracle solution, SQL*Net and Oracle Glue. This solution provides no GUI for creating SQL statements. Oracle Glue provides the programmer with a set of functions (ex/ GlueRegisterControl(), GlueGetString(), GlueGetNumber(), ExecSQL(), etc.) with which commands are sent to and data is received from Oracle. The programmer communicates through these functions, through SQL, and through some additional statements which Glue requires. These additional statements allow the programmer to establish "status" variables within what might be called an Oracle Glue workspace. For example, (I'm not sure if the string text is exactly correct) sqlerr = ExecSQL("SET ROWINDICATOR :numrows:") would establish a Glue variable called "numrows" as a place into which the number of rows returned from a query would go. I could then say later in the program Dim nrows% nrows = GlueGetNumber("numrows", 0) MsgBox Str$(nrows) + " rows returned from the query." We chose Glue over ODBC and some other tools we tried because of Glue's speed and because, as far as our vision now goes, we do not see ourselves using any other databases than Oracle. Randy Coates rcoates@telerama.lm.com