Re: COM with Thread Pool API

From:

"Igor Tandetnik" <itandetnik@mvps.org>

Newsgroups:

microsoft.public.vc.atl

Date:

Wed, 7 Jun 2006 20:59:22 -0400

Message-ID:

<OgqpCbpiGHA.4056@TK2MSFTNGP02.phx.gbl>

"Sarge" <Sarge@newsgroups.nospam> wrote in message
news:eyn24SpiGHA.4044@TK2MSFTNGP03.phx.gbl

"Igor Tandetnik" <itandetnik@mvps.org> wrote in message
news:eT4UFSoiGHA.4912@TK2MSFTNGP03.phx.gbl...

Sarge <Sarge@newsgroups.nospam> wrote:

Thanks, Jeremy. I prefer to avoid COM, and have been doing so until
the boss decided to move from PostgreSQL to MSSQL. No way around
COM now

You can use ODBC to connect to MSSQL without COM.

Using MFC & DAO?

DAO is considered obsolete and not recommended for use in new projects.
Anyway, DAO can work on top of any ODBC data source, including one that
points to a MSSQL database.

Is your application using DAO to connect to PostrgreSQL? If so, most
likely you already connect via an ODBC data source. Chances are your
application can work with little or no changes if you simply configure
your ODBC source to connect to MSSQL instead. The amount of work
required depends mainly on how many PostgreSQL-specific features you are
using above and beyond standard SQL.
--
With best wishes,
Igor Tandetnik

With sufficient thrust, pigs fly just fine. However, this is not
necessarily a good idea. It is hard to be sure where they are going to
land, and it could be dangerous sitting under them as they fly
overhead. -- RFC 1925