作 者： njscorpio (我是菜鸟,我怕谁!)
等 级：
信 誉 值： 79
所属论坛： PowerBuilder
问题点数： 50
回复次数： 6
发表时间： 2002-5-29 20:56:07
在需要用到数据窗口的窗体时，提示："datawindow error"."database transation information not available call settrans or settransobject fuction".这是什么错误？
回复人： tiantianpb(我本弱智，ai!没有办法！) ( ) 信誉：80 2002-5-29 20:57:50 得分:13
dw_1.settransobject(sqlca)
Top
回复人： lws0472() ( ) 信誉：95 2002-5-29 21:04:32 得分:13
你的数据窗口没有连接事务对象，在窗口的open事件中写入
dw_1.settransobject(sqlca)
Top
回复人： njscorpio(我是菜鸟,我怕谁!) ( ) 信誉：79 2002-5-29 21:07:40 得分:0
晕，我写了啊，这个怎么也不会忘啊
Top
回复人： pingkeke(pingkeke) ( ) 信誉：100 2002-5-29 21:16:36 得分:12
如果你的DATAWINDOW有这一句的话settransobject(sqlca),那肯定是你的数据库在连接时忘了一句CONNECT,
Top
回复人： njscorpio(我是菜鸟,我怕谁!) ( ) 信誉：79 2002-5-29 21:49:05 得分:0
我也有啊
Top
回复人： bzlj(bzlj) ( ) 信誉：100 2002-5-29 21:50:13 得分:12
不会吧，这么奇怪，仔细看看是不是啊？
10 个解决方案
#1
只有两种可能：
1、没连接数据库或数据库连接未成功；在连接时检查SQLCA.SQLCode
2、缺少dw_1.SetTransObject(SQLCA)，在执行这后要加上检测。
1、没连接数据库或数据库连接未成功；在连接时检查SQLCA.SQLCode
2、缺少dw_1.SetTransObject(SQLCA)，在执行这后要加上检测。
#2
SQLCA.DBMS = '...'
SQLCA...= ...
CONNECT USING SQLCA;
//上面这句别忘了
。。。
dw_1.settransobject(sqlca)
SQLCA...= ...
CONNECT USING SQLCA;
//上面这句别忘了
。。。
dw_1.settransobject(sqlca)
#3
这些我都有，在我本机上是可以执行，只是安装到其他机器上时有问题。我怀疑是有个什么文件没有包含
#4
PowerBuilder6.0运行环境文件列表
The deployed application
(本文摘自《Application Techniques》 Chapter 33: Deploying Your Application on Windows)
In this section you will find lists of the files a user needs for running a PowerBuilder application. If you select one of the Deployment Kit options in the Setup program, the required files are installed for you. The lists in this section tell you what files get installed so that you can do an installation manually or so that you can specify file lists for a Setup program.
The lists do not include the application files (executable and initialization files), the database files, and the files that provide the database's runtime environment.
Localization kits
PowerBuilder provides localized deployment kits (DDDK) as an installation option. They are available in French, German, Italian, Spanish, Dutch, Danish, Norwegian, and Swedish.
You can install the DDDK in the development environment or on the user's machine. If you install the DDDK on the development machine, you can use it for testing purposes.
The localized deployment kits handle language-specific data at execution time.
Filenames
DLLs have different names for different deployment environments so that you can tell at a glance whether you are deploying the correct versions of files. In the following tables, names are shown like this: PBVM60x .DLL. The x is replaced with a letter for deployment platforms other than the ANSI version of Windows 95 and Windows NT.
For example, if your application includes DataWindow objects, you will deploy PBDWE60.DLL on 32-bit Windows platforms, PBDWE60W .DLL on 16-bit Windows platforms, and PBDWE60U .DLL if you developed your application with PowerBuilder for Unicode and you are deploying on a version of Windows NT that supports the Unicode Standard.
The tables indicate which feature or DBMS the file is required to support and whether it is available on Windows 3.1 or Windows 95 and Windows NT. For example, PBVM60x .DLL is required for all 32-bit deployed applications. You need not install other files unless your application uses the features indicated.
Powersoft files
The Powersoft deployment DLLs belong in the application directory or in a directory on the system path
Required for Name Windows 3.x Windows 95 and NT
All PBVM60x.DLL X X
Data Windows and Reports PBDWE60x.DLL X X
Rich Text PBRTC60x.DLL X X
OLE PBOUI60W.DLL X -
OLE automation servers PBAEN60.tlb - X
All PBBGR60W.DLL X -
All PBTYP60W.DLL X -
Visual Basic controls PBVBX60W.DLL X -
DataWindow plug-in NPDWE60x.DLL X X
Standard PowerBuilder window plug-in NPPBA60x .DLL X X
Secure PowerBuilder window plug-in NPPBS60x .DLL X X
Standard PowerBuilder window ActiveX PBRX60x .OCX - X
Secure PowerBuilder window ActiveX PBRXS60x .OCX - X
PowerBuilder Synchronizer executable PBSYNCx .EXE X X
Native database interfaces
The files for the native Powersoft database interfaces your application uses belong in the application directory or a directory on the system path . These interfaces are provided with the Enterprise edition of PowerBuilder:
DBMS Name Windows 3.x Windows 95 and NT
IBM databases PBIBM60W.DLL X -
INFORMIX I-Net 5 5PBIN560x.DLL X X
INFORMIX I-Net 7 PBIN760x.DLL - X
Microsoft SQL Server 4.x DB-Lib PBSYB60x .DLL
PBDBL60x .DLL X
X X
X
Microsoft SQL Server 6.0 .DLLX PBMSS60x X X
Powersoft ODBC Interface PBODB60x.DLL
PBODB60x .INI X
X X
X
Oracle Version 7.1 PBO7160x .DLL X X
Oracle Version 7.2 PBO7260x .DLL X X
Oracle Version 7.3 PBO7360x .DLL X X
Sybase InformationCONNECT DB2 Gateway PBMDI60x .DLL
PBDBL60x .DLL X
X X
X
Sybase Net-Gateway for DB2 PBNET60x .DLL
PBDBL60x .DLL X
X X
X
Sybase SQL Server 4.x DB-Lib PBSYT60x .DLL
PBDBT60x .DLL -
- X
X
Sybase SQL Server 10.x and 11.x CT-Lib PBSYC60x .DLL X X
ODBC and system files
If your application uses ODBC drivers, each user's machine needs four types of files:
Powersoft database interface
ODBC initialization files
Microsoft ODBC driver and DLLs
Windows 3.x Windows 95 and NT
CPN16UT.DLL DS16GT.DLL
ODBC16UT.DLL DS32GT.DLL
ODBC.DLL MSVCRT40.DLL
ODBCCURS.DLL ODBC32.DLL
ODBCINT.DLL ODBC16GT.DLL
ODBCINST.HLP ODBC32GT.DLL
ODBCADM.EXE ODBCCP32.CPL
ODBCCP32.DLL
ODBCCR32.DLL
ODBCINT.DLL
ODBCINST.CNT
ODBCINST.HLP
ODBCTRAC.DLL
ODBCAD32.EXE
ODBC database drivers and supporting files
These files belong in the WINDOWS\SYSTEM or WINNT\SYSTEM directory.
Filenames may change
Many of the files listed here are provided by vendors other than Powersoft. More recent files with different names may be substituted.
ODBC Drivers Windows 3.x Windows 95 and NT
All INTERSOLV drivers PBBAS07.DLL
PBFLT07.DLL
PBUTL07.DLL
PBDRV07.CNT
PBDRV07.HLP
QETRN07.DLL
QEPB.LIC PBBAS12.DLL
PBFLT12.DLL
PBUTL12.DLL
PBDRV12.CNT
PBDRV12.HLP
PBTRN12.DLL
IVPB.LIC
INTERSOLV Btrieve PBBTR07.DLL
WBTRCALL.DLL
PBBTR07.HLP PBBTR12.DLL
PBBTR12.HLP
INTERSOLV dBASE PBDBF07.DLL
PBDBF07.HLP PBDBF12.DLL
PBDBF12.HLP
INTERSOLV DB2 PBDB207.DLL
PBDB207.DLL PBDB212.DLL
PBDB212.DLL
INTERSOLV Excel 4 PBXLS07.DLL
PBXLS07.HLP -
INTERSOLV Excel Workbook PBXLS507.DLL
PBXLS507.HLP PBXLS512.DLL
PBXLS512.HLP
INTERSOLV Scalable SQL PBXQL07.DLL
WDDLSVCS.DLL
WXQLCALL.DLL
PBXQL07.HLP -
INTERSOLV Paradox 4 PBPDX07.DLL
PBPDX07.HLP -
INTERSOLV Paradox 5 PBIDP07.DLL
PBIDP07.HLP PBIDP12.DLL
PBIDP12.HLP
INTERSOLV Text PBTXT07.DLL
PBTXT07.HLP PBTXT12.DLL
PBTXT12.HLP
Sybase SQL Anywhere 5.5 WOD50W.DLL
WL50EN.DLL
WODBC.HLP
WODBC.HLP WOD50T.DLL
WL50ENT.DLL
WTR50T.DLL
WODBC.HLP
OLE system files
Windows 3.x Most users will have the required OLE DLLs on their systems because they have already installed an OLE server application. If the user's system does not have the OLE DLLs, copy them to the WINDOWS\SYSTEM directory. To allow users to access OLE 1.0 applications, you must also merge the file OLE2.REG into the system registry using Microsoft's REGEDIT utility.
COMPOBJ.DLL
CTL3DV2.DLL
OLE2.DLL
OLE2CONV.DLL
OLE2DISP.DLL
OLE2NLS.DLL
OLE2PROX.DLL
STORAGE.DLL
TYPELIB.DLL
Windows 95 and Windows NT For Windows 95 and Windows NT, the OLE DLLs are part of the system and do not need to be installed separately.
#5
经过编译生成的PowerBuilder应用程序需要如下运行环境:
1.PowerBuilder 运行时动态连接库( Runtime Library )在PowerBuilder 6.0中需要如下DLL库:
PBVM60.DLL (PowerBuilder 虚拟机)(必需)
PBDWE60.DLL (DataWindow 引擎)(可选)
PBRTC60.DLL (Rich Text Control)(可选)
PBTRA60.DLL (DLL used for tracing db calls)(可选)
2.与所需连接的数据库的直连接口(Native Driver) 或 ODBC接口(ODBC Driver)
PBSYC60.DLL (连接Sybase 的直连接口) PBO7360.DLL (连接Oracle7.3的直连接口)
3.所需连接的数据库的Client端(如Sybase的Open Client, Oracle 的SQL Net)
1.PowerBuilder 运行时动态连接库( Runtime Library )在PowerBuilder 6.0中需要如下DLL库:
PBVM60.DLL (PowerBuilder 虚拟机)(必需)
PBDWE60.DLL (DataWindow 引擎)(可选)
PBRTC60.DLL (Rich Text Control)(可选)
PBTRA60.DLL (DLL used for tracing db calls)(可选)
2.与所需连接的数据库的直连接口(Native Driver) 或 ODBC接口(ODBC Driver)
PBSYC60.DLL (连接Sybase 的直连接口) PBO7360.DLL (连接Oracle7.3的直连接口)
3.所需连接的数据库的Client端(如Sybase的Open Client, Oracle 的SQL Net)
#6
PBDWE60.DLL (DataWindow 引擎)(可选)
这个文件包含了吗？
这个文件包含了吗？
#7
connect using sqlca;
settransobject(sqlca)
settransobject(sqlca)
#8
最稳妥的办法是把那个PB西面的那些DLL全部考过去，肯定行的
#9
呵呵，这个问题怎么和我昨天遇到的一样啊？我是这样解决的（在陶清论坛上）：
请看这个链接：
http://www.pdriver.com/bbs3/cgi-bin/topic.cgi?forum=6&topic=5817
请看这个链接：
http://www.pdriver.com/bbs3/cgi-bin/topic.cgi?forum=6&topic=5817
#10
不好意思，贴错了，应该是：
http://www.pdriver.com/bbs3/cgi-bin/topic.cgi?forum=6&topic=5772
http://www.pdriver.com/bbs3/cgi-bin/topic.cgi?forum=6&topic=5772
#1
只有两种可能：
1、没连接数据库或数据库连接未成功；在连接时检查SQLCA.SQLCode
2、缺少dw_1.SetTransObject(SQLCA)，在执行这后要加上检测。
1、没连接数据库或数据库连接未成功；在连接时检查SQLCA.SQLCode
2、缺少dw_1.SetTransObject(SQLCA)，在执行这后要加上检测。
#2
SQLCA.DBMS = '...'
SQLCA...= ...
CONNECT USING SQLCA;
//上面这句别忘了
。。。
dw_1.settransobject(sqlca)
SQLCA...= ...
CONNECT USING SQLCA;
//上面这句别忘了
。。。
dw_1.settransobject(sqlca)
#3
这些我都有，在我本机上是可以执行，只是安装到其他机器上时有问题。我怀疑是有个什么文件没有包含
#4
PowerBuilder6.0运行环境文件列表
The deployed application
(本文摘自《Application Techniques》 Chapter 33: Deploying Your Application on Windows)
In this section you will find lists of the files a user needs for running a PowerBuilder application. If you select one of the Deployment Kit options in the Setup program, the required files are installed for you. The lists in this section tell you what files get installed so that you can do an installation manually or so that you can specify file lists for a Setup program.
The lists do not include the application files (executable and initialization files), the database files, and the files that provide the database's runtime environment.
Localization kits
PowerBuilder provides localized deployment kits (DDDK) as an installation option. They are available in French, German, Italian, Spanish, Dutch, Danish, Norwegian, and Swedish.
You can install the DDDK in the development environment or on the user's machine. If you install the DDDK on the development machine, you can use it for testing purposes.
The localized deployment kits handle language-specific data at execution time.
Filenames
DLLs have different names for different deployment environments so that you can tell at a glance whether you are deploying the correct versions of files. In the following tables, names are shown like this: PBVM60x .DLL. The x is replaced with a letter for deployment platforms other than the ANSI version of Windows 95 and Windows NT.
For example, if your application includes DataWindow objects, you will deploy PBDWE60.DLL on 32-bit Windows platforms, PBDWE60W .DLL on 16-bit Windows platforms, and PBDWE60U .DLL if you developed your application with PowerBuilder for Unicode and you are deploying on a version of Windows NT that supports the Unicode Standard.
The tables indicate which feature or DBMS the file is required to support and whether it is available on Windows 3.1 or Windows 95 and Windows NT. For example, PBVM60x .DLL is required for all 32-bit deployed applications. You need not install other files unless your application uses the features indicated.
Powersoft files
The Powersoft deployment DLLs belong in the application directory or in a directory on the system path
Required for Name Windows 3.x Windows 95 and NT
All PBVM60x.DLL X X
Data Windows and Reports PBDWE60x.DLL X X
Rich Text PBRTC60x.DLL X X
OLE PBOUI60W.DLL X -
OLE automation servers PBAEN60.tlb - X
All PBBGR60W.DLL X -
All PBTYP60W.DLL X -
Visual Basic controls PBVBX60W.DLL X -
DataWindow plug-in NPDWE60x.DLL X X
Standard PowerBuilder window plug-in NPPBA60x .DLL X X
Secure PowerBuilder window plug-in NPPBS60x .DLL X X
Standard PowerBuilder window ActiveX PBRX60x .OCX - X
Secure PowerBuilder window ActiveX PBRXS60x .OCX - X
PowerBuilder Synchronizer executable PBSYNCx .EXE X X
Native database interfaces
The files for the native Powersoft database interfaces your application uses belong in the application directory or a directory on the system path . These interfaces are provided with the Enterprise edition of PowerBuilder:
DBMS Name Windows 3.x Windows 95 and NT
IBM databases PBIBM60W.DLL X -
INFORMIX I-Net 5 5PBIN560x.DLL X X
INFORMIX I-Net 7 PBIN760x.DLL - X
Microsoft SQL Server 4.x DB-Lib PBSYB60x .DLL
PBDBL60x .DLL X
X X
X
Microsoft SQL Server 6.0 .DLLX PBMSS60x X X
Powersoft ODBC Interface PBODB60x.DLL
PBODB60x .INI X
X X
X
Oracle Version 7.1 PBO7160x .DLL X X
Oracle Version 7.2 PBO7260x .DLL X X
Oracle Version 7.3 PBO7360x .DLL X X
Sybase InformationCONNECT DB2 Gateway PBMDI60x .DLL
PBDBL60x .DLL X
X X
X
Sybase Net-Gateway for DB2 PBNET60x .DLL
PBDBL60x .DLL X
X X
X
Sybase SQL Server 4.x DB-Lib PBSYT60x .DLL
PBDBT60x .DLL -
- X
X
Sybase SQL Server 10.x and 11.x CT-Lib PBSYC60x .DLL X X
ODBC and system files
If your application uses ODBC drivers, each user's machine needs four types of files:
Powersoft database interface
ODBC initialization files
Microsoft ODBC driver and DLLs
Windows 3.x Windows 95 and NT
CPN16UT.DLL DS16GT.DLL
ODBC16UT.DLL DS32GT.DLL
ODBC.DLL MSVCRT40.DLL
ODBCCURS.DLL ODBC32.DLL
ODBCINT.DLL ODBC16GT.DLL
ODBCINST.HLP ODBC32GT.DLL
ODBCADM.EXE ODBCCP32.CPL
ODBCCP32.DLL
ODBCCR32.DLL
ODBCINT.DLL
ODBCINST.CNT
ODBCINST.HLP
ODBCTRAC.DLL
ODBCAD32.EXE
ODBC database drivers and supporting files
These files belong in the WINDOWS\SYSTEM or WINNT\SYSTEM directory.
Filenames may change
Many of the files listed here are provided by vendors other than Powersoft. More recent files with different names may be substituted.
ODBC Drivers Windows 3.x Windows 95 and NT
All INTERSOLV drivers PBBAS07.DLL
PBFLT07.DLL
PBUTL07.DLL
PBDRV07.CNT
PBDRV07.HLP
QETRN07.DLL
QEPB.LIC PBBAS12.DLL
PBFLT12.DLL
PBUTL12.DLL
PBDRV12.CNT
PBDRV12.HLP
PBTRN12.DLL
IVPB.LIC
INTERSOLV Btrieve PBBTR07.DLL
WBTRCALL.DLL
PBBTR07.HLP PBBTR12.DLL
PBBTR12.HLP
INTERSOLV dBASE PBDBF07.DLL
PBDBF07.HLP PBDBF12.DLL
PBDBF12.HLP
INTERSOLV DB2 PBDB207.DLL
PBDB207.DLL PBDB212.DLL
PBDB212.DLL
INTERSOLV Excel 4 PBXLS07.DLL
PBXLS07.HLP -
INTERSOLV Excel Workbook PBXLS507.DLL
PBXLS507.HLP PBXLS512.DLL
PBXLS512.HLP
INTERSOLV Scalable SQL PBXQL07.DLL
WDDLSVCS.DLL
WXQLCALL.DLL
PBXQL07.HLP -
INTERSOLV Paradox 4 PBPDX07.DLL
PBPDX07.HLP -
INTERSOLV Paradox 5 PBIDP07.DLL
PBIDP07.HLP PBIDP12.DLL
PBIDP12.HLP
INTERSOLV Text PBTXT07.DLL
PBTXT07.HLP PBTXT12.DLL
PBTXT12.HLP
Sybase SQL Anywhere 5.5 WOD50W.DLL
WL50EN.DLL
WODBC.HLP
WODBC.HLP WOD50T.DLL
WL50ENT.DLL
WTR50T.DLL
WODBC.HLP
OLE system files
Windows 3.x Most users will have the required OLE DLLs on their systems because they have already installed an OLE server application. If the user's system does not have the OLE DLLs, copy them to the WINDOWS\SYSTEM directory. To allow users to access OLE 1.0 applications, you must also merge the file OLE2.REG into the system registry using Microsoft's REGEDIT utility.
COMPOBJ.DLL
CTL3DV2.DLL
OLE2.DLL
OLE2CONV.DLL
OLE2DISP.DLL
OLE2NLS.DLL
OLE2PROX.DLL
STORAGE.DLL
TYPELIB.DLL
Windows 95 and Windows NT For Windows 95 and Windows NT, the OLE DLLs are part of the system and do not need to be installed separately.
#5
经过编译生成的PowerBuilder应用程序需要如下运行环境:
1.PowerBuilder 运行时动态连接库( Runtime Library )在PowerBuilder 6.0中需要如下DLL库:
PBVM60.DLL (PowerBuilder 虚拟机)(必需)
PBDWE60.DLL (DataWindow 引擎)(可选)
PBRTC60.DLL (Rich Text Control)(可选)
PBTRA60.DLL (DLL used for tracing db calls)(可选)
2.与所需连接的数据库的直连接口(Native Driver) 或 ODBC接口(ODBC Driver)
PBSYC60.DLL (连接Sybase 的直连接口) PBO7360.DLL (连接Oracle7.3的直连接口)
3.所需连接的数据库的Client端(如Sybase的Open Client, Oracle 的SQL Net)
1.PowerBuilder 运行时动态连接库( Runtime Library )在PowerBuilder 6.0中需要如下DLL库:
PBVM60.DLL (PowerBuilder 虚拟机)(必需)
PBDWE60.DLL (DataWindow 引擎)(可选)
PBRTC60.DLL (Rich Text Control)(可选)
PBTRA60.DLL (DLL used for tracing db calls)(可选)
2.与所需连接的数据库的直连接口(Native Driver) 或 ODBC接口(ODBC Driver)
PBSYC60.DLL (连接Sybase 的直连接口) PBO7360.DLL (连接Oracle7.3的直连接口)
3.所需连接的数据库的Client端(如Sybase的Open Client, Oracle 的SQL Net)
#6
PBDWE60.DLL (DataWindow 引擎)(可选)
这个文件包含了吗？
这个文件包含了吗？
#7
connect using sqlca;
settransobject(sqlca)
settransobject(sqlca)
#8
最稳妥的办法是把那个PB西面的那些DLL全部考过去，肯定行的
#9
呵呵，这个问题怎么和我昨天遇到的一样啊？我是这样解决的（在陶清论坛上）：
请看这个链接：
http://www.pdriver.com/bbs3/cgi-bin/topic.cgi?forum=6&topic=5817
请看这个链接：
http://www.pdriver.com/bbs3/cgi-bin/topic.cgi?forum=6&topic=5817
#10
不好意思，贴错了，应该是：
http://www.pdriver.com/bbs3/cgi-bin/topic.cgi?forum=6&topic=5772
http://www.pdriver.com/bbs3/cgi-bin/topic.cgi?forum=6&topic=5772