[Quickfix-developers] (no subject)

[David P. <dpa...@pd...>]

 I am trying to get quick fix  working with Microsoft SQL Server 2005 and
Visual studio 2005. This package does not seem to have ntwdblib.lib with it.
Nor does it have stlfront.h or sqldb.h. I found the following information in
the Visual Studio 2005 documentation. It seems to indicate that support may
have run out for the DB-Library used by quick fix. Do you know if I am
correct on this? Do you have any ideas on how I should proceed? (Note I
searched the mailing lists and FAQ's for info but could find nothing) Also
joined the developer mailing list, but did not see how to post a message
there. 

 

Here is the documentation fro VS2005:

DB-Library is a Call Level Interface that allows C applications to access
MicrosoftR SQL ServerT 2000. DB-Library was the original application
programming interface (API) that allowed applications to access SQL Server,
and remains specific to SQL Server.

The DB-Library API has not been enhanced beyond the level of SQL Server
version 6.5. All DB-Library applications can work with SQL Server 2000, but
only as 6.5 level clients. Features introduced in SQL Server 2000 and SQL
Server version 7.0 are not supported for DB-Library applications.

SQL Server 2000 does not include a programming environment for DB-Library
for Microsoft Visual BasicR. Existing DB-Library for Visual Basic
applications can run against SQL Server 2000, but must be maintained using
the software development tools from SQL Server version 6.5. All development
of new Visual Basic applications that access SQL Server should use the
Visual Basic data APIs such as Microsoft ActiveXR Data Objects (ADO) and
Remote Data Objects (RDO).

While the DB-Library API is still supported in Microsoft SQL Server 2000, no
future versions of SQL Server will include the files needed to do
programming work on applications that use this API. Connections from
existing applications written using DB-Library will still be supported in
the next version of SQL Server, but this support will also be dropped in a
future release. When writing new applications, avoid using DB-Library. When
modifying existing applications, you are strongly encouraged to remove
dependencies on DB-Library. Instead of DB-Library, you can use ADO, OLE DB,
or ODBC to access data in SQL Server.

 

 

 

 Best

 

 

David P