Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Mailing Lists -> Oracle-L -> RE: VB/ADO/RDO/DAO/OHNO/UHOH and transactions
The default for all these is that transactions are handled "stupidly". =20
In both ODBC and OLE DB (which all these API's are built on), the default is to autocommit, so every successful SQL statement is automatically committed. All these API's will have an option to disable autocommit, in which case you will have to call an explicit commit procedure.
Justin Cave
Distributed Database Consulting, Inc.
http://www.ddbcinc.com/askDDBC
-----Original Message-----
From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Jesse, Rich
Sent: Thursday, May 13, 2004 9:45 AM
To: oracle-l_at_freelists.org
Subject: VB/ADO/RDO/DAO/OHNO/UHOH and transactions
Hey all,
After an interesting TAR on why an SMON process would be eating up 250MB =3D of memory, I find that we may need to adjust the transactions on our VB =3D programs. Seeing as the only VB I've done consisted of a full-screen =3D button that said "Click Me", I have no clue as to how transactions are =3D handled in the various DB interfaces like ADO, RDO, DAO, or whatever =3D we're using.
Anyone know a good online resource for this? Google has oodles of =3D fragments, but I don't know enough to know which might be "better". It =3D would also help if I knew what DB library(ies) we're using... = <blush>
TIA,
Rich
Rich Jesse System/Database Administrator rich.jesse_at_quadtechworld.com QuadTech, Sussex, WI USAPlease see the official ORACLE-L FAQ: http://www.orafaq.com
----------------------------------------------------------------
![]() |
![]() |