DBLib in Yukon?

We use the Microsoft/Solomon ERP product and it uses
DBLib, a SQLServer 6.5 (maybe 16bit) DLL for its access
to SQLServer. DBLib is supported in SQL 7 and SQL2000 as
a legacy tool. Will DBLib will be supported in Yukon?
How can I find a definitive answer to this question?Since Yukon is still in Beta, definitive statements about its functionality
are somewhat limited and may be subject to change. However SQL2000 BOL says:
"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."
http://msdn.microsoft.com/library/en-us/dblibc/dbc_pdc00b_589v.asp
The official info on Yukon is here:
http://www.microsoft.com/sql/yukon/productinfo/default.asp
--
David Portas
--
Please reply only to the newsgroup
--|||I feel your pain. We still use DbLib as well and we are worried.
I've heard that it will be provided as a separate download and a separate
setup.
Anyway it sucks to use such an old technology. We have issues with DbLib and
NAT and other issues we did not have any explanations for since MS does not
support it anymore.
"Price Brattin" <pbrattin@.buenosw.com> wrote in message
news:075e01c3ce1f$f5e06de0$a501280a@.phx.gbl...
> We use the Microsoft/Solomon ERP product and it uses
> DBLib, a SQLServer 6.5 (maybe 16bit) DLL for its access
> to SQLServer. DBLib is supported in SQL 7 and SQL2000 as
> a legacy tool. Will DBLib will be supported in Yukon?
> How can I find a definitive answer to this question?|||Price - I'm not familiar with the Solomon product, but are you telling me that
the latest version (whatever that may be), shipped with the "MS" Logo on it,
still uses db-lib!?!?
> We use the Microsoft/Solomon ERP product and it uses
> DBLib, a SQLServer 6.5 (maybe 16bit) DLL for its access
> to SQLServer. DBLib is supported in SQL 7 and SQL2000 as
> a legacy tool. Will DBLib will be supported in Yukon?
> How can I find a definitive answer to this question?
>
Neil Pike MVP/MCSE. Protech Computing Ltd
Reply here - no email
SQL FAQ (484 entries) see
http://forumsb.compuserve.com/gvforums/UK/default.asp?SRV=MSDevApps
(faqxxx.zip in lib 7)
or www.ntfaq.com/Articles/Index.cfm?DepartmentID=800
or www.sqlserverfaq.com
or www.mssqlserver.com/faq|||Daniel,
MS certainly aren't doing any more development on it, but they still "support"
it. Have you reported bugs to them via PSS and not received a work-around or
fix?
> Anyway it sucks to use such an old technology. We have issues with DbLib and
> NAT and other issues we did not have any explanations for since MS does not
> support it anymore.
> "Price Brattin" <pbrattin@.buenosw.com> wrote in message
> news:075e01c3ce1f$f5e06de0$a501280a@.phx.gbl...
> > We use the Microsoft/Solomon ERP product and it uses
> > DBLib, a SQLServer 6.5 (maybe 16bit) DLL for its access
> > to SQLServer. DBLib is supported in SQL 7 and SQL2000 as
> > a legacy tool. Will DBLib will be supported in Yukon?
> > How can I find a definitive answer to this question?
>
Neil Pike MVP/MCSE. Protech Computing Ltd
Reply here - no email
SQL FAQ (484 entries) see
http://forumsb.compuserve.com/gvforums/UK/default.asp?SRV=MSDevApps
(faqxxx.zip in lib 7)
or www.ntfaq.com/Articles/Index.cfm?DepartmentID=800
or www.sqlserverfaq.com
or www.mssqlserver.com/faq|||Are you sure they still support it?
I remember I saw some info on MS site that it is not supported anymore. We
have a client that uses one of our apps and he cannot use NAT. The client
had to use static IP addresses in order to use the App over internet and a
VPN connection.
I'll look into MS site again for more info.
Thanks!
"Neil Pike" <neilpike@.compuserve.com> wrote in message
news:VA.00006190.022d20cf@.compuserve.com...
> Daniel,
> MS certainly aren't doing any more development on it, but they still
"support"
> it. Have you reported bugs to them via PSS and not received a work-around
or
> fix?
> > Anyway it sucks to use such an old technology. We have issues with DbLib
and
> > NAT and other issues we did not have any explanations for since MS does
not
> > support it anymore.
> >
> > "Price Brattin" <pbrattin@.buenosw.com> wrote in message
> > news:075e01c3ce1f$f5e06de0$a501280a@.phx.gbl...
> > > We use the Microsoft/Solomon ERP product and it uses
> > > DBLib, a SQLServer 6.5 (maybe 16bit) DLL for its access
> > > to SQLServer. DBLib is supported in SQL 7 and SQL2000 as
> > > a legacy tool. Will DBLib will be supported in Yukon?
> > > How can I find a definitive answer to this question?
> >
> Neil Pike MVP/MCSE. Protech Computing Ltd
> Reply here - no email
> SQL FAQ (484 entries) see
> http://forumsb.compuserve.com/gvforums/UK/default.asp?SRV=MSDevApps
> (faqxxx.zip in lib 7)
> or www.ntfaq.com/Articles/Index.cfm?DepartmentID=800
> or www.sqlserverfaq.com
> or www.mssqlserver.com/faq
>|||Yep. Microsoft Business Solutions/Solomon is still based
on DBLib.
>--Original Message--
> Price - I'm not familiar with the Solomon product, but
are you telling me that
>the latest version (whatever that may be), shipped with
the "MS" Logo on it,
>still uses db-lib!?!?
>> We use the Microsoft/Solomon ERP product and it uses
>> DBLib, a SQLServer 6.5 (maybe 16bit) DLL for its
access
>> to SQLServer. DBLib is supported in SQL 7 and SQL2000
as
>> a legacy tool. Will DBLib will be supported in
Yukon?
>> How can I find a definitive answer to this question?
> Neil Pike MVP/MCSE. Protech Computing Ltd
> Reply here - no email
> SQL FAQ (484 entries) see
> http://forumsb.compuserve.com/gvforums/UK/default.asp?
SRV=MSDevApps
> (faqxxx.zip in lib 7)
> or www.ntfaq.com/Articles/Index.cfm?DepartmentID=800
> or www.sqlserverfaq.com
> or www.mssqlserver.com/faq
>
>.
>|||Price Brattin (pbrattin@.buenosw.com) writes:
> We use the Microsoft/Solomon ERP product and it uses
> DBLib, a SQLServer 6.5 (maybe 16bit) DLL for its access
> to SQLServer. DBLib is supported in SQL 7 and SQL2000 as
> a legacy tool. Will DBLib will be supported in Yukon?
> How can I find a definitive answer to this question?
You can connect to SQL Server Yukon with DB-Library. However, no DLL
from DB-Library comes with the current beta, and I would not expect
this change for the RTM version. So you should take well care of your
NTWDBLIB.DLL.
I should also add that you cannot use all new features in SQL Server
Yukon with DB-Library. For instance, when I attempted to access a
column of the new xml datatype, I got an error message saying that
this was not supported. (You get this already in SQL7 for ntext columns,
by the way.)
--
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|||Daniel,
As it's shipped with SQL 2000, and fixes to it have been produced in at least
one SQL 2000 SP, then I'd say they still do support it.
I can't see why db-lib would break under NAT as I don't recall seeing any IP
addresses inside it's data frames when I've looked at traces of it in the past
for debugging. But I've never knowingly run a db-lib app through a NAT
router/device myself.
If you can do a network trace of a working (non-NAT) connection and a
non-working (NAT) connection, I'll be happy to look at the traces for you.
> Are you sure they still support it?
> I remember I saw some info on MS site that it is not supported anymore. We
> have a client that uses one of our apps and he cannot use NAT. The client
> had to use static IP addresses in order to use the App over internet and a
> VPN connection.
> I'll look into MS site again for more info.
> Thanks!
Neil Pike MVP/MCSE. Protech Computing Ltd
Reply here - no email
SQL FAQ (484 entries) see
http://forumsb.compuserve.com/gvforums/UK/default.asp?SRV=MSDevApps
(faqxxx.zip in lib 7)
or www.ntfaq.com/Articles/Index.cfm?DepartmentID=800
or www.sqlserverfaq.com
or www.mssqlserver.com/faq|||Actually what happens may be due to the application architecture as well.
One instance on the app works fine through NAT but when the second instance
is launched from a machine behind the NAT then the first app looses its
connection.
The app opens the connection when it is launched and it keeps it open till
the end. Yes, I know this is really bad but the app is pretty old and big
and I cannot improve it (read I'm not allowed to!).
"Neil Pike" <neilpike@.compuserve.com> wrote in message
news:VA.00006192.0065f62e@.compuserve.com...
> Daniel,
> As it's shipped with SQL 2000, and fixes to it have been produced in at
least
> one SQL 2000 SP, then I'd say they still do support it.
> I can't see why db-lib would break under NAT as I don't recall seeing any
IP
> addresses inside it's data frames when I've looked at traces of it in the
past
> for debugging. But I've never knowingly run a db-lib app through a NAT
> router/device myself.
> If you can do a network trace of a working (non-NAT) connection and a
> non-working (NAT) connection, I'll be happy to look at the traces for you.
> > Are you sure they still support it?
> >
> > I remember I saw some info on MS site that it is not supported anymore.
We
> > have a client that uses one of our apps and he cannot use NAT. The
client
> > had to use static IP addresses in order to use the App over internet and
a
> > VPN connection.
> >
> > I'll look into MS site again for more info.
> >
> > Thanks!
> Neil Pike MVP/MCSE. Protech Computing Ltd
> Reply here - no email
> SQL FAQ (484 entries) see
> http://forumsb.compuserve.com/gvforums/UK/default.asp?SRV=MSDevApps
> (faqxxx.zip in lib 7)
> or www.ntfaq.com/Articles/Index.cfm?DepartmentID=800
> or www.sqlserverfaq.com
> or www.mssqlserver.com/faq
>|||Ahh. So is the NAT a HIDE-NAT, and it's the application "complaining" about
seeing two connections coming at it from the same IP address then?
That would make sense - db-lib won't care about that.
The workaround for that, if you're in control of the NAT, is to set-up a NAT
pool instead of a static hide-NAT. Put enough addresses in the pool to cater
for the number of concurrent connections you're going to get.
> Actually what happens may be due to the application architecture as well.
> One instance on the app works fine through NAT but when the second instance
> is launched from a machine behind the NAT then the first app looses its
> connection.
> The app opens the connection when it is launched and it keeps it open till
> the end. Yes, I know this is really bad but the app is pretty old and big
> and I cannot improve it (read I'm not allowed to!).
Neil Pike MVP/MCSE. Protech Computing Ltd
Reply here - no email
SQL FAQ (484 entries) see
http://forumsb.compuserve.com/gvforums/UK/default.asp?SRV=MSDevApps
(faqxxx.zip in lib 7)
or www.ntfaq.com/Articles/Index.cfm?DepartmentID=800
or www.sqlserverfaq.com
or www.mssqlserver.com/faq