The other thing to note is that RDO was intended to be a VB class wrapper
around ODBC and that DAO is best used with Microsquish JET (Access)
databases, but doesn't work very well with ODBC databases. Also ADO (as far
as I have heard) right now works best with SQL Server, and is moving along
with Oracle but not with much else.
- Greg
> -----Original Message-----
> From: Jackson, DeJuan [SMTP:djackson@cpsgroup.com]
> Sent: Monday, June 01, 1998 2:16 PM
> To: Byron Nikolaidis; Jackson, DeJuan
> Cc: Tim Bosinius; pgsql-interfaces@postgresql.org
> Subject: RE: [INTERFACES] whoops: VB RDO works just fine with new
> odbc dri ver....
>
> There are 3 main standard that Micro$ has developed to interface with
> ODBC (age before beauty):
> DAO - Database Access Objects
> RDO - Remote Database Objects
> ADO - ActiveX Database Objects
> All three are implemented using OLE (Object Linking and Embedding) at
> one level or another. Their interface and tools only differ slightly
> between each one. DAO is the oldest and offers the least amount of
> functionality.
> RDO offers more functionality than its predecessor DAO but at the cost
> of speed. ADO was an attempt to utilize the new COM/ActiveX interface
> as a speed boost to RDO as well as standardizing features between DAO
> and RDO. One major bonus in ADO over RDO or DAO is that you can have a
> statement that updates the database and selects from it (think about
> it). In RDO and DAO you couldn't have a combined statement that used
> SELECT with INSERT, UPDATE, DELETE, or ALTER (very annoying). All three
> standards will work in Visual Basic 4.0 and 5.0 as well as Visual Basic
> for Applications.
>
> Forgive me for any inaccuracies, I'm not a MSCE.
> -DEJ
>
> > Jackson, DeJuan wrote:
> > > Has anyone tested with ADO? I just ask because it's supposed to be
> > the
> > > new Microsoft "standard".
> > > -DEJ
> >
> > What is ADO, and RDO, and RDX anyway. I dont use Visual Basic at all.
> >
> > Byron