pg.ddx.io pgsql-interfaces@postgresql.org mailing list archive
help / color / mirror / Atom feedwhoops: VB RDO works just fine with new odbc driver....
6+ messages / 4 participants
[nested] [flat]
* whoops: VB RDO works just fine with new odbc driver....
@ 1998-05-30 14:52 Tim Bosinius <tim@bosinius.de>
0 siblings, 0 replies; 6+ messages in thread
From: Tim Bosinius @ 1998-05-30 14:52 UTC (permalink / raw)
To: pgsql-interfaces
I am really sorry for saying that the new VB RDO does not
work with the new ODBC driver - that is not true.
I installed the postdrv.exe (v243) on a cleanly installed win95
client and my sample VB RDO program can update, delete and
insert new recordsets.
I am not quite sure where the problem is on my NT workstation,
but it is definitly not the ODBC driver.
The performance problem with Access97 still exists on the
win95 system though.
I guess I really should order the postgresql CD now ;)
Regards,
Tim Bosinius
^ permalink raw reply [nested|flat] 6+ messages in thread
* RE: [INTERFACES] whoops: VB RDO works just fine with new odbc dri ver....
@ 1998-06-01 20:26 Jackson, DeJuan <djackson@cpsgroup.com>
1998-06-01 20:48 ` Re: [INTERFACES] whoops: VB RDO works just fine with new odbc dri ver.... Byron Nikolaidis <byronn@insightdist.com>
0 siblings, 1 reply; 6+ messages in thread
From: Jackson, DeJuan @ 1998-06-01 20:26 UTC (permalink / raw)
To: Tim Bosinius <tim@bosinius.de>; pgsql-interfaces
Has anyone tested with ADO? I just ask because it's supposed to be the
new Microsoft "standard".
-DEJ
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: [INTERFACES] whoops: VB RDO works just fine with new odbc dri ver....
1998-06-01 20:26 RE: [INTERFACES] whoops: VB RDO works just fine with new odbc dri ver.... Jackson, DeJuan <djackson@cpsgroup.com>
@ 1998-06-01 20:48 ` Byron Nikolaidis <byronn@insightdist.com>
0 siblings, 0 replies; 6+ messages in thread
From: Byron Nikolaidis @ 1998-06-01 20:48 UTC (permalink / raw)
To: Jackson, DeJuan <djackson@cpsgroup.com>; +Cc: Tim Bosinius <tim@bosinius.de>; pgsql-interfaces
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
^ permalink raw reply [nested|flat] 6+ messages in thread
* RE: [INTERFACES] whoops: VB RDO works just fine with new odbc dri ver....
@ 1998-06-01 21:15 Jackson, DeJuan <djackson@cpsgroup.com>
0 siblings, 0 replies; 6+ messages in thread
From: Jackson, DeJuan @ 1998-06-01 21:15 UTC (permalink / raw)
To: Byron Nikolaidis <byronn@insightdist.com>; Jackson, DeJuan <djackson@cpsgroup.com>; +Cc: Tim Bosinius <tim@bosinius.de>; pgsql-interfaces
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
^ permalink raw reply [nested|flat] 6+ messages in thread
* RE: [INTERFACES] whoops: VB RDO works just fine with new odbc dri ver....
@ 1998-06-01 21:38 Krasnow, Greg <gak@hnc.com>
0 siblings, 0 replies; 6+ messages in thread
From: Krasnow, Greg @ 1998-06-01 21:38 UTC (permalink / raw)
To: 'Jackson, DeJuan' <djackson@cpsgroup.com>; Byron Nikolaidis <byronn@insightdist.com>; +Cc: Tim Bosinius <tim@bosinius.de>; pgsql-interfaces
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
^ permalink raw reply [nested|flat] 6+ messages in thread
* RE: [INTERFACES] whoops: VB RDO works just fine with new odbc dri ver....
@ 1998-06-02 17:33 Tim Bosinius <tim@bosinius.de>
0 siblings, 0 replies; 6+ messages in thread
From: Tim Bosinius @ 1998-06-02 17:33 UTC (permalink / raw)
To: 'Krasnow, Greg' <gak@hnc.com>; +Cc: pgsql-interfaces
> RDO offers more functionality than its predecessor DAO but at the cost
> of speed.
This is only partly correct. DAO/Jet is faster on Jet Databases, but if you use
it to connect to an ODBC datasource is much slower.
(see: Hitchhiker's Guide to Visual Basic & SQL Server, Microsoft Press,
ISBN:1-57231-567-9)
IMHO Remote Data Objects are the best and fastest way to connect you VB
apps to a database. I have tried to use ODBCdirect and ADO but did not get
very far with it. ODBCdirect is really hard to implement and ADO is not really
an option yet. I have heard rumours that ADO will be the only supported
database access method in VB 6.0, but I do not really believe it.
Right now ADO lacks a couple of things:
- there is now information on it in the VB 5.0 documentation, but I found
a Microsoft Website that explains most of it.
- right now it only exposes a small subset of the RDO 2.0 functionality
(OK - it will encompass RDO & the rest someday and will be the
'all-in-one" interface - at least from a Microsoft point of view)
This will change with the next releases of ADO.
> In RDO and DAO you couldn't have a combined statement that used
> SELECT with INSERT, UPDATE, DELETE, or ALTER (very annoying).
You can use the RDO EXECUTE method to submit any SQL statement you like.
The drawback is that it does not return anything (error / success) so you
have to rely on the ODBC driver to handle error messages correctly.
These error messages differ from ODBC driver to ODBC driver, which makes
it a little more work to handle those.
Regards
Tim Bosinius
^ permalink raw reply [nested|flat] 6+ messages in thread
end of thread, other threads:[~1998-06-02 17:33 UTC | newest]
Thread overview: 6+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
1998-05-30 14:52 whoops: VB RDO works just fine with new odbc driver.... Tim Bosinius <tim@bosinius.de>
1998-06-01 20:26 RE: [INTERFACES] whoops: VB RDO works just fine with new odbc dri ver.... Jackson, DeJuan <djackson@cpsgroup.com>
1998-06-01 20:48 ` Re: [INTERFACES] whoops: VB RDO works just fine with new odbc dri ver.... Byron Nikolaidis <byronn@insightdist.com>
1998-06-01 21:15 RE: [INTERFACES] whoops: VB RDO works just fine with new odbc dri ver.... Jackson, DeJuan <djackson@cpsgroup.com>
1998-06-01 21:38 RE: [INTERFACES] whoops: VB RDO works just fine with new odbc dri ver.... Krasnow, Greg <gak@hnc.com>
1998-06-02 17:33 RE: [INTERFACES] whoops: VB RDO works just fine with new odbc dri ver.... Tim Bosinius <tim@bosinius.de>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox