dbnmpipe.exe for MS-DOS

I recently purchased sql 2000.
I need connectivity for an old DOS program.
I see that I need the file DBNMPIPE.EXE
I can't find this file anywhere on my CD's or on
Microsofts website.
Where can I get it?
"Cash Woodward" <cash@.grandtarghee.com> wrote in message
news:1f67801c457c1$bfc79810$a501280a@.phx.gbl...
> I recently purchased sql 2000.
> I need connectivity for an old DOS program.
> I see that I need the file DBNMPIPE.EXE
> I can't find this file anywhere on my CD's or on
> Microsofts website.
> Where can I get it?
I believe you are in non-supported territory here (from the SQL Server web
site):
Client Support:
.. Windows 955, Windows 98, Windows Me, Windows NT Workstation 4.0, Windows
2000 Professional, Windows XP Professional, and Windows XP Home Edition are
supported.
Steve
|||Actually it states that older clients will still work with sql 2000.
"Steve Thompson" wrote:

> "Cash Woodward" <cash@.grandtarghee.com> wrote in message
> news:1f67801c457c1$bfc79810$a501280a@.phx.gbl...
> I believe you are in non-supported territory here (from the SQL Server web
> site):
> Client Support:
> .. Windows 955, Windows 98, Windows Me, Windows NT Workstation 4.0, Windows
> 2000 Professional, Windows XP Professional, and Windows XP Home Edition are
> supported.
> Steve
>
>
|||Sent by email
Neil Pike MVP/MCSE. Protech Computing Ltd
Reply here - no email
SQL FAQ (484 entries) see
http://forumsb.compuserve.com/gvforu...?SRV=MSDevApps
(faqxxx.zip in lib 7)
or http://www.ntfaq.com/Articles/Index...partmentID=800
or www.sqlserverfaq.com
or www.mssqlserver.com/faq
|||Older DOS based clients? Can you send a reference?
Thanks, Steve
"Cash Woodward" <Cash Woodward@.discussions.microsoft.com> wrote in message
news:7ECE2A36-195D-4120-9D4F-A94142E311A0@.microsoft.com...[vbcol=seagreen]
> Actually it states that older clients will still work with sql 2000.
> "Steve Thompson" wrote:
web[vbcol=seagreen]
Windows[vbcol=seagreen]
are[vbcol=seagreen]
|||See the reply #4 from Neil Pike.
This is from archive file SQL7DBLIBSUPPORT.TXT
This is what I have read from Microsofts website also.
Q. Does SQL 7/2000 support DB-Library? What about 16-bit clients - DOS
etc.?
A. Yes it does, but DB-Library is functionally stabilised at the 6.5
level. Therefore if a DB-Library client on whatever platform worked
against a 6.5 database it should work against the same database migrated
to SQL 7.0/2000.
None of the SQL 7.0 features like unicode, character columns greater
than 255 characters etc. are in DB-Library though. So if you utilise
any SQL 7.0 features then these can only be accessed by ODBC 3.7 or
OLE-DB clients.
Similarly for 16-bit clients. These are supported, but only with the
6.5 levels of ODBC/DB-Library code. 16-bit clients cannot access new
SQL 7.0 features either.
The 16-bit client code is not supplied with 7.0/2000 - you will have to
get it from the 6.5 CD-ROM. This includes DOS and Win 3.x drivers.
===
v1.03 2000.04.28
Applies to SQL Server versions : 7.0, 2000
FAQ Categories : Connectivity
Related FAQ articles : n/a
Related Microsoft Kb articles : n/a
Other related information : n/a
Authors : Neil Pike
*** Sent via Devdex http://www.devdex.com ***
Don't just participate in USENET...get rewarded for it!
|||Thank you Cash -- very interesting!
"Cash Woodward" <cash@.grandtarghee.com> wrote in message
news:%23ggDDuSWEHA.1164@.tk2msftngp13.phx.gbl...
> See the reply #4 from Neil Pike.
> This is from archive file SQL7DBLIBSUPPORT.TXT
> This is what I have read from Microsofts website also.
> Q. Does SQL 7/2000 support DB-Library? What about 16-bit clients - DOS
> etc.?
> A. Yes it does, but DB-Library is functionally stabilised at the 6.5
> level. Therefore if a DB-Library client on whatever platform worked
> against a 6.5 database it should work against the same database migrated
> to SQL 7.0/2000.
> None of the SQL 7.0 features like unicode, character columns greater
> than 255 characters etc. are in DB-Library though. So if you utilise
> any SQL 7.0 features then these can only be accessed by ODBC 3.7 or
> OLE-DB clients.
> Similarly for 16-bit clients. These are supported, but only with the
> 6.5 levels of ODBC/DB-Library code. 16-bit clients cannot access new
> SQL 7.0 features either.
> The 16-bit client code is not supplied with 7.0/2000 - you will have to
> get it from the 6.5 CD-ROM. This includes DOS and Win 3.x drivers.
> ===
> v1.03 2000.04.28
> Applies to SQL Server versions : 7.0, 2000
> FAQ Categories : Connectivity
> Related FAQ articles : n/a
> Related Microsoft Kb articles : n/a
> Other related information : n/a
> Authors : Neil Pike
>
>
> *** Sent via Devdex http://www.devdex.com ***
> Don't just participate in USENET...get rewarded for it!

DB-Library vs. OLE DB

Are there any benefits in choosing OLE DB interface instead of using the native DB-Library connectivity?
What is recommended?
Thanks,
AdamSupportability would be the #1 reason for choosing OLEDB over DB Library.
DB Library is considered an a legacy interface and as such was not updated
from what shipped with SQL Server 6.5 and 7.0.
--
--Brian
(Please reply to the newsgroups only.)
"Adam Ticktin" <anonymous@.discussions.microsoft.com> wrote in message
news:AD2D6770-2EBF-4886-BD6D-550AF7D6E6E7@.microsoft.com...
> Are there any benefits in choosing OLE DB interface instead of using the
> native DB-Library connectivity?
> What is recommended?
> Thanks,
> Adam|||Thanks Brian! Any known loss of available functionality in 2000 that can't be accessed DB-Library?
Adam|||Adam,
> Any known loss of available functionality in 2000
> that can't be accessed DB-Library?
Well, basically everything that was added to SQL Server after
version 6.5 is not supported by DB-Library.
DB-Library became obsolete years ago. Don't even think about using
it.
Linda|||I would not recommend using DB-Library. Yukon, the next release of SQL
Server, will not include the files needed to develop DB-Library
applications. The following warning has been in the readme of every SQL
Server 2000 service pack and in every update to the SQL Server 2000 Books
Online:
Warning 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 Microsoft
ActiveX® Data Objects (ADO), OLE DB, or ODBC to access data in SQL Server.
Also, this topic in the SQL Server 2000 Books Online outlines the types of
features not available to DB-Library applications:
http://msdn.microsoft.com/library/?url=/library/en-us/bldgapps/ba_highprog_56pc.asp?frame=true
And a third point against DB-Library: the SQL Server client components used
in ADO.NET, ADO, OLE DB, and ODBC are also native interfaces for SQL Server.
The SQLClient managed provider, the SQLOLEDB provider, and SQL Server ODBC
driver all use the native SQL Server protocol (TDS) to send their requests
to the database engine. DB-Library will not have an inherent performance
advantage over any of these APIs.
--
Alan Brewer [MSFT]
Lead Programming Writer
SQL Server Documentation Team
This posting is provided "AS IS" with no warranties, and confers no rights|||=?Utf-8?B?QWRhbSBUaWNrdGlu?= (anonymous@.discussions.microsoft.com) writes:
> Thanks Brian! Any known loss of available functionality in 2000 that can't
> be accessed DB-Library?
Quite a bit.
I have a list on
http://www.sommarskog.se/mssqlperl/mssql-sqllib.html#restrictions_with_new_datatypes
This text is in the context of two Perl modules that I have.
DB-Library is a very nice interface, fast and simple that does not
do things behind your back. Unfortunately, Microsoft does not at all
share my opinion on this matter.
--
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp