Connect to the Microsoft SQL Server from PowerBuilder)

Product: PowerBuilder version: 6.0; 5.0
Platform: PC operating system: Windows 3.1, Windows 95, Windows NT
File:
Overview This document is designed to provide assistance in establishing your contact with Microsoft SQL Server 6.0 or 6.5 using the local drive interface from PowerBuilder on the Intel Platform. The Local interface of PowerBuilder is subject to SQL Server 7.0 but is not improved to provide access to new features of SQL Server 7.0. For PowerBuilder 7.0 and later, the recommended interface provides a OLE-DB interface for access to SQL Server 7.0.
This file is supplemental to the information provided in the PowerBuilder instruction file
"Connect to your database" guide.
Microsoft SQL Server Client Software
Microsoft Client software needs to be installed as appropriate platform, 16-bit, 32-bit, or two before all contacts may be established with Powerbuilder and your target database.
Verify the number of connections to your Microsoft SQL Server
Once you have installed the necessary client side software provided by Microsoft, you are sure that you can connect outside PowerBuilder before you try to connect from inside PowerBuilder. It is necessary to confirm that you can establish a connection from your workspace using the client software. From this point it should be easy to connect from PowerBuilder.
Compliant with the drive at connection time

You select a particular PowerBuilder local drive when you provide the DBMS value in the database configuration file. This is the DBMS attribute used to fill in the transaction processing object. To connect to and use the specified DBMS value, you must have installed the associated PowerBuilder local drive and the related Microsoft Client Network to Support DLLs.
The following table shows the relationship between DBMS values and related PowerBuilder and Microsofts DLLs. If a DLLs is missing from the relevant DBMS, you cannot connect it.
This template describes the 16-and 32-bit plans for PowerBuilder 5.0, 6.0, 7.0 interface and SQL Server 6. X DLL's:
16Bit 32Bit
Microsoft PowerBuilder
PB5.0

MSDBLIB3.DLL PBMSS050.DLL NTWDBLIB. DLL PBMSS050.DLL
PB6.0

MSDBLIB3.DLL PBMSS60W. DLL (unique configuration) NTWDBLIB. DLL PBMSS60.DLL
PB7.0 16-bit PowerBuilder 7.0 does not support NTWDBLIB. DLL PBMSS70.DLL

Debugging
When PowerBuilder is connected to Microsoft 6. X database, the transaction processing object and value passing can not be properly set and give you problems. If your DBProfile or transaction processing object ranks your arrangement in "DBMS" and tracks MSS "and tries to connect, the tracking log starts. File Name "PBTRACE. The log will be created and will be located in the main directory of the window. When you first run the application and try the connection information box will appear and will state PBTRACE. Logs are created in your WINDOWS Directory (e.g., C:/WINDOWS ). If the message box does not appear, repeat your step to verify that you have placed the word "tracking" in front of the MSS, between spaces.
Common Problems
1. Many common problems customers use a mixture of 16 and 32-bit platform products together or use improper pathing to cause connection conflicts.
2. A common problem will be the multi-copy of the above dll's, which may lead to many version problems and the platform conflict with the improper pathing and incorrect configuration.
3. You cannot connect from a 16-bit PowerBuilder (version 5.0 or 6.0) If you have only installed 32-bit Microsoft Client edge software and a visa versa.
Public Error
Dbms mss (Msoft) SQL Server 6.0 is not supported in the current installation
This error may occur in any of the following situations:
1. You have not installed an appropriate version or platform SQL Server 6. X DLLs
A) the platform for installing the appropriate version of the client software is provided by Microsoft.
2. SQL Server 6. X DLLs is missing or not in the path.
A) verify that you can connect to the PowerBuilder and use the Microsoft Client utility ISQL_W.
B) Check the valid items in the registration settings. (For: MS SQL Server 6.5 client software and 32-bit PowerBuilder ).
C) Check the PATH environment variables and be sure that the/sql60/box directory (ms SQL Server 6.0) or/mssql/box directory (SQL MS Server 6.5) is in the path. (Only applicable to 16 bits ).
3. pbmss dll files are missing or not in the path
A) Make sure that you have installed the specified PowerBuilder interface properly and it may be located in the path. Install it again.
4.32-bit PowerBuilder development application or executable application try to connect to 6 through 16-bit SQL Server. X client.
5. The 16-bit PowerBuilder development application or the executable application attempts to connect to the 32-bit SQL Server 6. X client.
Unable to connect: the SQL server cannot be obtained or does not exist. The specified SQL statement is not found.
This error may occur in the following situations:
1. You provide the server name option for incorrect information in the configuration file
A) correct the error and provide the correct server name.
2. You have incorrectly set the net library information for use by Microsoft when installing the client software.
A) correct the error and run the SQL Server Client Configuration Utility to find it in your ms SQL client solution group. In the net Library tab (6.5 software) or in the net Library Section (6.0 software), perform correct changes to reflect what services your Administrator provides, E. G. If you are set to use the name pipe connections, you must specify this as the purpose of the net Library drive.
Note: contact your ms SQL Server administrator for required information about connectivity from your workspace on your special network. They will know if they set a service named pipe or TCP/IP, and so on.
The dynamic Connection Library <DLL Name> cannot be found in the specified path.
This error may occur in any of the following situations:
1. (16/32 bits) DLL is missing.
2. The directory contains DLL not in the path. (If you search for a copy)
3. If you search for multiple copies, pathing may be the result of using your connections in an invalid 16/32 bit version.

Translation is really awkward. Connecting SQL server requires Pb-level dynamic libraries and SQL Server Interface libraries. In addition, pay attention to the differences between 16-bit and 32-bit systems and the MDAC version.

Files required by pb90
Dbnetlib. dll,
Dbnmpntw. dll,
Ntwdblib. dll,
Dbmssocn. dll,
Pbmss90.dll,
Libjcc. dll,
Libjsybheap. dll,
Pbvm90.dll,
Pbdwe90.dll
Alternatively, you can use the cliconfg.exe and ntwdblib. dll files in sql7 To Go To The program directory and execute cliconfg.exe to configure the client and add PB to provide the dynamic library.