FreeTDS Development Group

[Jon Pounder <JonP AT inline.net>]

oledb was only the MS flavour of the week for a short time and got replaced 
with ADO.
Both just adding extra layers of useless overhead onto something that was 
not broken to start with.


At 02:31 PM 2/6/2003 -0500, you wrote:
> On Thu, 6 Feb 2003 12:37:31 -0500, "Craft, Steve"
> <SCraft AT LegionInsurance.com> wrote:
> >
> > Regarding the main thread  RE: freetds in win32
> >
> > Why use ODBC and not OLEDB on Win32?
>
> Just a small matter of programming.  The guts of FreeTDS compile on Win32
> now, meaning it can be adapted to other Win32 uses,  As Frank said, ODBC
> is used on unixy systems, despite its flaws, because nothing better saw
> wide adoption.  Making FreeTDS compile and run on Win32 systems involved
> making some allowances and adding some files to support the environment,
> but no (or almost no) new logic.
>
> I don't know where OleDB stands these days on the Great Strategy Radar,
> with .Net morphing from one Tuesday to the next.  To add OleDB glue around
> FreeTDS would be an interesting project for someone who likes that sort of
> thing, though.  In theory, it could provide Sybase servers as compatible
> back-ends to Microsoft servers, meaning they could be seen as "linked
> servers" and whatnot.
>
> --jkl
> _______________________________________________
> FreeTDS mailing list
> FreeTDS AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/freetds