Friday, February 10, 2012
BDE Connection via ODBC to MS SQL Server fails
I have a strange problem accessing a MS SQL Database from my network.
I'm using an application that is based on BDE which uses ODBC to connect to a MS SQL DB.
When I tried to connect from the network with BDE,I got this error message:
BDE Error : 13059
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server does not exist or access denied.
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen (Connect()).
On the server side I'm using W2003 EE ,MS SQL 2000 Standard with SP4, BDE5.11.
On the client side it's an XP SP2 with MS SQL Client installed, same BDE 5.11
When I create an alias using ODBC and mapping to my server, it connects and the communication with the Database Server succeds:
TESTS COMPLETED SUCCESSFULLY!
When I'm trying to connect using BDE Admin and double clicking on the + sign of the alias I created usind ODBC admin I get the message I listed above.
Any help would be appreciated,
Thanks.May check this http://support.plato.com/kb/tip.asp?psid=23252 link fyi.|||Thank you for replying me...in the meantime i solved the problem.
It was the incorrect settings in the registry for BDE. After erasing the keys from the registry and having reinstalled the BDE everything worked fine.
There are some files used by BDE when connecting to SQL server which are not installed when using Delphi 5 or later :(
However thank you for the usefull link.
best regards,
Sanyi|||Glad the issue is resolved and appreciate your feedback on posting the solution, that helps.
BDE and ODBC
My question is:
What is the relationship between ODBC and BDE? For connectivity purposes, are they independent from each other or do they interact with in some way? As far as I can tell they have the same function.
thanks for your help! i'll be spending a lot of time on this board as i begin a DB crash course.
RyanHi,
A little bit late, and probably have worked this out, however SalesLogix uses BDE as a layer in between SalesLogix and the Microsoft Database Communication layer. This is used in SalesLogix 6 as a direct communication cutting out BDE.
ODBC sits also on top of the Microsoft Database Communcation layer so both are near enough the same. However BDE can communication directly to this layer as well as to ODBC, so allowing a more open environment for development. So allowing communication with lots of different database and data sources.
The main reason why SalesLogix uses BDE as it also uses Delphi programming language, so you can write additional background scripts that get executed when updates / deletes etc... happen. So creating the tefs that are needed for synchronisation.
Hope that helps a lot...
BDE admin connecting problem, How do I connect via IP address.
I can connect locally fine to the server and log in using the sa account, however for BDE admin i HAVE to use the server name instead of ip address. If i try to use the ip address of the server, the connection dosnt get established. *this is all happening localy on our own network.
How to I use ip address to connect instead of the server name? I will need to connect remotely outside of our network later on, and i dont think I can use the servername. Does anyone have a solution? thanks.BDE = borland database engine|||I suggest creating an ODBC DSN and using that from BDE rather than the SQLLINK driver|||thanks for the input, we figured out the problem though, it seems the server uses a proprietary listening port, say.. "3314" set up for their server. we were able to connect after setting up an alias for sql server.|||I have more questions
1) does SQL server 2005 come with a client only tool?
2) is there a way to connect via an alias with an application without installing sql server 2005?
thanks in advance!|||
1/ Yes its called SQL Server Management Studio (or Express Edition of SSMS) for management and there are dev tools, config tools etc
2/ you need to install SQL Server Computer Manager to config alias's
BDE 5.01 not connecting to SQL2K after patching
I am experiencing unusual behaviour with a number of desktops (3 of 20) running the BDE and the SQL connectivity option from the sql cd. For reasons unknown the BDE suddenly stops connecting to the database and cant be fixed without a reimage. Appears t
o be a key or dll that is causing interoperability issues.
No idea what o/s patch is causing trouble at this stage but its a recent phenomena.
has anyone seen this type of behaviour with third part software using BDE/SQL connectivity ?
Brian in AU
+61 431 479 751
What error do you get?
Could the problem be something along these lines?
259569 PRB: Installing Third-Party Product Breaks Windows 2000 MDAC Registry
http://support.microsoft.com/?id=259569
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.