buppcpp wrote:

> I'm talking about a driver that "most" developers can use.

Most windows only lemmings you mean? ;)
I have no need to use anything to do with .NET and can still support
both Windows and Non-windows environments.
And on those sites that insist that ADODB is the way to go, the ODBC
driver off the firebird site seems to work fine, no complaints from the
two sites that 'insisted', alternatively they use the Jaybird driver and
JDBC access which other sites are using fine!

> You can use OLEDB in .NET now and in the future and so can VB
> developers,
> Web developers, Delphi, etc..
>
> .NET is to specific, Firebird needs to start catering to the masses
> first.

Now you have lost me - which masses?
If we are NOT talking .NET, then there are several other ways of
accessing Firebird - using Interbase or Firebird specific drivers. I use
PHP quite happily, and while the Builder? 'driver' I use is commercial
(IBO) I had to switch to that because the alternative I had already paid
for in Builder simply did not work - but there are free alternatives to
that and IBO only costs if(when) you start making money using it.

> That's how Firebird's adoption rate will grow the fastest.

The problem is there are too many 'target areas' and keeping everyone
happy takes effort. Many of us are where we are today through avoiding
.NET and so that is a 'target' that has not had as much support as many
of the alternatives :)

--
Lester Caine
-----------------------------
L.S.Caine Electronic Services