网站公告列表

  没有公告

加入收藏
设为首页
联系站长
您现在的位置: 网络学院 >> 程序设计 >> PowerBuilder >> 文章正文
  PB连接Microsoft SQL Server          【字体:
PB连接Microsoft SQL Server
作者:佚名    文章来源:不详    点击数:    更新时间:2007-7-3    
Connecting to Microsoft SQL Server from PowerBuilder

 

SUMMARY: This document is designed to provide assistance in making your connection to Microsoft SQL Server 6.0 or 6.5 from PowerBuilder. This information is a supplement to the Connecting to your Database manual.
Document ID: 44510 Last Revised: 04/12/99
Topic: Connectivity Document Type: Tip
Product: PowerBuilder Version: 6.0; 5.0
Platform: PC Operating System: Windows 3.1, Windows 95, Windows NT

Document:

  Overview

  This document is designed to provide assistance in making your connection to Microsoft SQL Server 6.0 or 6.5 using the native driver interface from PowerBuilder on the Intel platforms. PowerBuilder's native interface is compliant with SQL Server 7.0 but has not been enhanced to provide access to new features of SQL Server 7.0. For PowerBuilder 7.0 and later, the recommended interface for accessing SQL Server 7.0 and subsequent releases is the OLE-DB interface.

  This document is a supplement to the information provided in the PowerBuilder Documentation
"Connecting to your Database" manual.

  Microsoft SQL Server Client Software

  Microsoft Client software needs to be installed for the proper platform, 16-bit, 32 -bit, or both before any connections can be made with PowerBuilder and your target database.

  Verifying your Microsoft SQL Server Connection

  Once you have installed the necessary client-side software provided by Microsoft, make sure that you can connect outside of PowerBuilder before you attempt to connect from within PowerBuilder. This is necessary to determine that you can establish a connection from your workstation using the client software. From this point it should be easy to connect from PowerBuilder.

  Matching the drivers at connect time

  You select a specific PowerBuilder native driver when you supply the DBMS value in the Database profile. This entry is used to populate the DBMS property of the transaction object. In order to connect using the specified DBMS value, you must have installed the associated PowerBuilder native driver and the related Microsoft client side network support dlls.

  The following table shows the relationship between the DBMS value and the related PowerBuilder and Microsofts DLLs. If one of the DLLs associated with the DBMS specification is missing, you will not be able to connect.

  This template describes the 16- and 32-bit scheme for PowerBuilder 5.0, 6.0, 7.0 interfaces and SQL Server 6.x DLL'S:

  16Bit   32Bit
  Microsoft PowerBuilder Microsoft PowerBuilder
PB 5.0 MSDBLIB3.DLL PBMSS050.DLL NTWDBLIB.DLL PBMSS050.DLL
PB 6.0 MSDBLIB3.DLL PBMSS60W.DLL
(deployment only)
NTWDBLIB.DLL PBMSS60.DLL
PB 7.0 16-bit not supported by PowerBuilder 7.0 NTWDBLIB.DLL PBMSS70.DLL
 

  DEBUGGING

   When PowerBuilder connects to a Microsoft 6.x database, the transaction object and the values passed in may not be set properly and giving you a problem. If in your DBProfile or transaction object in the "DBMS" line your place "trace MSS" and try to connect, a trace log will be started. The file name "PBTRACE.LOG" will be created and located in the windows home directory. When you first run the application and try to connect a message box will appear and state the PBTRACE.LOG is being created in your windows directory (e.g., C:\WINDOWS). If the message box does not appear, recheck your steps to verify you placed the word "trace" in front of MSS, with a space between.

 

9 7 3 1 2 4 8 :

 Common Problems

   1.Many of the common problems customers have is with using a mixture of 16 and 32-bit platform products together and/or setting improper pathing to cause connection conflicts.

   2.A common problem is to have multiple copies of the above dll's and improper pathing that can cause a host of problems with version and platform conflicts and mismatch errors.

   3.You cannot connect from 16-bit PowerBuilder (versions 5.0 or 6.0) if you've only installed the 32-bit Microsoft client-side software and visa-versa.

  Common Errors

  DBMS MSS (Msoft) SQL Server 6.0 not supported in current installation

   This error can occur under any of the following circumstances:

    1. You have not installed the proper version or platform of SQL Server 6.x DLLs

    a) Install proper version/platform of the client software provided by Microsoft.
 2. The SQL Server 6.x DLLs are missing or not in path.
    a) Verify that you can connect outside of PowerBuilder using the Microsoft client utility ISQL_W.
    b) Check the registry settings for valid entries. (Applies to: MS Sql Server 6.5 client software and 32-bit PowerBuilder).
    c) Check the path environment variable and make sure that the \sql60\bin directory (MS SQL Server 6.0 ) or \mssql\bin directory (MS SQL Server 6.5) is in the path. (applies to 16-bit only).
    3. The PBMSS DLL file is missing or is not in the path
    a) Make sure that you have properly installed the specified PowerBuilder interface and that it can be found in the path. Reinstall it if necessary
 4. A 32-bit PowerBuilder development application or executable application attempted to connect via a 16-bit SQL Server 6.x client.

    5. A 16-bit PowerBuilder development application or executable application attempted to connect via a 32-bit SQL Server 6.x client.

  Unable to connect: SQL Server is unavailable or does not exist. Specified SQL Sever not found.

  This error can occur under the following circumstances:

   1. You supplied incorrect information in the profile for the Server name option

    a) To correct the error, supply the correct server name.
   2. You have incorrectly setup the Net Library information when installing the client software applied by Microsoft.
    a) To correct the error, run the SQL Server Client Configuration Utility found in your MS SQL Client program group. On the Net Library tab (6.5 software) or under Net Library section (6.0 software), make the correct changes to reflect what services you administrator has provided, e.g., if you're setup to use Named Pipes connections you must indicate this as the Net Library driver to use.
  Note: Contact your MS SQL Server Administrator to get the required information regarding connectivity from your workstation on your particular network. They will know if they've setup Named Pipe services or TCP/IP services, etc.

  Dynamic Link Library <dll name> could not be found in the specified path.

  This error can occur under any of the following circumstances:

   1.(16/32-bit ) DLL is missing.

   2.Directory containing the DLL is not in the path. (If a search has found a copy)

   3.If a search finds multiple copies, the pathing may be result in an invalid 16/32Bit version being used for your connection.

9 7 3 1 2 4 8 :

站内文章搜索 高级搜索
文章录入:admin    责任编辑:admin 
  • 上一篇文章:

  • 下一篇文章:
  • 发表评论】【加入收藏】【告诉好友】【打印此文】【关闭窗口
    最新热点 最新推荐 相关文章
     在PB程序中实现ODBC数据…
     用PB5 设计 串口通讯程序
     如何用VC创建可在PB中调…
     PB连接Microsoft  SQL S…
     用PB编写多线程应用程序
  • page、request、session、ap…

  • 开发手记---JAVA数据库连接池

  • weblogic 9.1的domain配置my…

  • 保留weblogic 中jsp编译后生…

  • ava与数据库连接的四种方法

  • javabean+mysql数据库连接池

  • 关于CTreeCtrlr的=NM_DBLCL…

  • 使用ICE遇到的编译问题

  • boost.lexical_cast源码重列

  • SSL连接建立过程分析(5)

  •   网友评论:(只显示最新10条。评论内容只代表网友观点,与本站立场无关!)
    网络学院©2007 www.23book.net
    为您提供web编程,vb编程,vc编程,服务器架设管理,数据库设计等方面的知识 站长:David