I think you underestimate your product. Give it a native ADO driver to
flourish in other technologies such as ASP or even within MS development
tools such as VB/VC. I believe MS developers will adopt it pretty quickly as
Access engine is too pathetic and MSDE is too limited :)
Warm regards
Tauseef Shazad
--
Jeff Overcash (TeamB) | Talk about failure
(Please do not email | To fall is not to fail
me directly unless | Failure isn't about falling down
asked. Thank You) | Failure is staying down (Marillion)
Will this not create another incompatibility among different software. i.e
if I write software using one OLE DB driver, will it work on another OLE DB
driver ?. Have you a defined minimum functionality defined for these OLE DB
developers. How can a developer make sure that his software will work
accross multiple ODBC/OLE DB drivers without "feature not implemented" sort
of messages for different ODBC drivers. Or do you want each developer to
load his own version of ODBC driver on a single client machine.....
Comeon guys, give a single standard OLE DB accessibility layer for
Interbase.
"Jeff Overcash (TeamB)" <over...@onramp.net> wrote in message
news:3A16AF88...@onramp.net...
Tauseef Shazad wrote:
>
> Which ODBC drivers TeamB officially recommends and how to get hold of these
> drivers ?
>
I don't use ODBC or OLE DB so I won't recommend a driver.
>
> Comeon guys, give a single standard OLE DB accessibility layer for
> Interbase.
>
Borland has never written these drivers, they have always been furnished by
third parties. They will continue to be furnished by third parties.