Subject Re: [ib-support] Best lanquage
Author Paul Schmidt
On 19 Nov 2001, at 9:24, Bernhard Doebler wrote:

> ----- Original Message -----
> From: "Paul Schmidt" <paul@...>
> To: <>
> Sent: Friday, November 16, 2001 4:55 PM
> Subject: Re: [ib-support] Best lanquage
> > On 15 Nov 2001, at 13:34, AdPay-Systech wrote:
> >
> > features, so if you wrote a program for V2.0 it was broken by (and
> > rewritten for ) 3.0, 4.0, 5.0, 6.0 and .Net. I have heard that .Net
> > is really good at this, it breaks almost all existing code.
> >
> Hi,
> as a part-time VB programmer I'd like to state that no rewrite from VB
> 5 to VB 6 was really needed since they're fully code-compatible. VB 5
> was extended by VB 6 with many usefull features but the syntax didn't
> change in any way. >From VB 6 to VB.NET a total rewrite (oat 100 %
> bjectoriented) is needed. That's true.

Okay so you dodn't need to rewtite from 5 to 6, I gave up after 4,
because the only thing that seems to survive intact were some of
the bugs. There are bugs in VB 2 that were still alive and well in
VB 4, even though VB 4 was a complete rewrite (they moved from
assembler to C code at that point). I think VB peaked with V3 it's
been all downhill since then.

The other point, and this brings it back to on topic for this group,
the only way to access a real database from VB is through ODBC,
and other then maybe the expensive EasySoft one, none of the IB
ODBC drivers are "production" quality. A couple of them look
promising, but they still need a lot of work. On this point, does
anyone know what happened to the IBPhoenix ODBC driver? The
binaries are from July, has nothing happened since July, or are the
binaries way behind the CVS tree?


Paul Schmidt
Tricat Technologies