Re: VB5 with Oracle. Hangs because of transactions

Chris is right to tell you to avoid Jet overhead. If you're going to be working with Oracle, you want to get as close as you can to native operations. If that can be done with ODBCDirect, okay, but you'll do better with Objects for OLE, which is sometimes abbreviated OO4O (in case you want to search the archives for discussions on its relative merits). Unless you are not prevented by other considerations from doing so, such as the need to support multiple data sources, I would recommend switching to Oracle's Objects for OLE, as Elliot also recommended. It used to be available separately; it's included with PersonalOracle and can also be found among the client software on the OracleWorkgroup CD. We've had very good results with it.

Tim Romano
-- former denizen of Schmiedgasse in Passau (gruessGott! Christian)
but now to be found in Swarthmore PA

smoore_at_accordhr.com wrote:
>
> In article <6hcfma$q3n$1_at_einstein.pnm.net>,
> "Christian J. Bauer"
> <christian.bauer_at_passau.netsurf.de> wrote:
> >
> > Domingues wrote in message

 <01bd69cf$0d7db1d0$320281ac_at_pdo8brg>...
> > > ...
> > > Set Wks =

 CreateWorkspace("ManutWorkspace", "prodata", "prodata",  dbUseODBC)
> > > Set

 Conn = Wks.OpenConnection("ManutConnection", dbDriverNoPrompt,
> > False,

 odbcWinCP + ";")
> >
> > You should avoid those DAO Workspace stuff when
 connecting to external
> > (ODBC) databases. In your case, the workspace is
 handling the Transactions
> > and this could be the reason for your "deadlock".
 You should use RDO
> > instead. DAO is only neccessary when you want JET. You
 should use DAD only
> > when connecting to local Databases (dBase,Access,
 Paradox etc...) and dont
> > want to use the ODBC overhead.
> >
> > When using DAO

 you can also avoid the workspaces using "OpenDatabase".
> >
> > Chris
> >
> >
>
> I
> don't think that is the case. When you create a workspace using
> ODBCDirect,
> you don't invoke all of the Jet overhead. I've doing something
> similar and
> use the following lines to connect:
>
> 'Establish an ODBC connection.
> Set
> wkODBC = CreateWorkspace("ODBCWorkspace", "", "", dbUseODBC)
> DBEngine.Workspaces.Append wkODBC
> Set cnODBC = wkODBC.OpenConnection("",
> dbDriverNoPrompt, True, _
> "ODBC;DATABASE=" & sService & ";UID=" & sUserName
> & _
> ";PWD=" & sPassword & ";DSN=oracle;")
>
> -----== Posted via Deja News, The Leader in Internet Discussion ==-----
> http://www.dejanews.com/ Now offering spam-free web-based newsreading
Received on Tue Apr 21 1998 - 00:00:00 CDT