远程Sybase数据库技术支持,联系手机:13811580958,QQ:289965371!

 

随着Sybase被完全整合到SAP下,Sybase原来的支持网站被SAP Support Portal取代。
只有购买了SAP服务的用户才能使用账号登录SAP Support Portal进行介质下载、补丁升级、报Incident等。
考虑到Sybase数据库的初学者或者没有购买原厂服务的Sybase客户情况,现提供SAP ASE/IQ/RS/SDK/SQL Anywhere/PB等产品的BUG信息。
在SAP Support Portal网站或者google上搜索Targeted CR List for ASE,可以看到针对不同版本的CR(CR表示Change Request)简单描述信息列表。
需要注意的是:Targeted CR List for ASE列出的CR虽然绝大多数是BUG,但有一些是更改需求。
以下提供SAP ASE/IQ/RS/SDK/SQL Anywhere/PB等产品的BUG信息!

如有问题,请联系我!

QQ :289965371 点击这里给我发消息
Email:
不仅仅包括BUG的详细描述信息,还包括首次报告BUG的平台、数据库版本以及BUG修复历史过程;有些BUG还提供了Workaround来临时解决该BUG带来问题。

 

CR:156209
CR Number:   156209
Product Name:   PB Enterprise
Product Component:   Machine Code Deployment
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
scrolling in MultiLineEdit behaves differently in machine code than in p-code : in machine code, when scrolling to the last line, the last line displays at the top of the mle and you can see some blank space after this line ; in p-code, the last line displays at the bottom of the mle.



CR:156211
CR Number:   156211
Product Name:   PB Enterprise
Product Component:   Machine Code Exe Creation
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
Cannot load more than 50 dlls in an exe file (machine code executable).



Development: This is an Operating System issue. The LoadLibrary call (the call that opens the dll) fails. To prove it is an OS issue. I created a simple C program that loads 60 dlls and it fails in that as well on both win95 and winnt.



CR:156212
CR Number:   156212
Product Name:   PB Enterprise
Product Component:   Window - Runtime
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
SetFocus() in open event of window not working. It does work from a commandbutton. Also works if posted from open event.



CR:156223
CR Number:   156223
Product Name:   PB Enterprise
Product Component:   Language - Runtime
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
RPCFUNC with return value: the return value is not returned. Not database specific: tested in Oracle, SYC, SYB, MSS.



CR:156227
CR Number:   156227
Product Name:   PB Enterprise
Product Component:   DB Informix
Status:   Closed
OS:   Solaris 2.5.1
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
5.0.02 Database/Table Painter: When connected to an Informix database some of the properties, including primary keys cannot be set.

Note: Solaris Only



CR:156229
CR Number:   156229
Product Name:   PB Enterprise
Product Component:   Shared Objects
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
6.0 Beta: regression from 5.0.03. Similar to 400351. Getting assertion failure after adding a command button to a tab visual user object, and then trying to open a descendant of the udo in the user object painter. The error message is:

fieldID < no_fields in OB_OBJECT_LOCAL::getFieldL value file c:\pb051\runtime\h\obobjloc.h, line 222.



Verified fixed in 6.0.



CR:156233
CR Number:   156233
Product Name:   PB Enterprise
Product Component:   Menus - Runtime
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
Modifying the toolbar item text and toolbar tip text of toolbar on a sheet is only refreshed on the screen the first time that an instance of the sheet is opened. Subsequent sheets show the old text and tip text. WORKAROUND: Add this to the bottom of the open event of the sheet: w_sheet.setredraw(false) w_sheet.toolbaralignment = (something other than what it is to start with) w_sheet.toolbaralignment = (whatever it was originally) w_sheet.setredraw(true)



CR:156234
CR Number:   156234
Product Name:   PB Enterprise
Product Component:   DW Painter
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
Radiobutton and checkbox tabbing in NUP datawindows doesn't work as expected. You cannot tab from one radiobutton/checkbox to another on the last row of the nup - if it's a 2-up this means on the SECOND row of the NUP (across), before you tab from radio button one of the second row to radio button two on the second row, the tab will force it to SKIP to the LAST radiobutton column on the FIRST row. Same behavior with checkboxe(s).



CR:156236
CR Number:   156236
Product Name:   PB Enterprise
Product Component:   DB Informix
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
Informix IN5 (did not test IN7, but according to development, it will not work there either). RPCFUNC: I am unable to get anything back from RETURNING clause in Informix stored procedure.



CR:156237
CR Number:   156237
Product Name:   PB Enterprise
Product Component:   Installation
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
Verified 3/19

Tested on 503_25 - All 12 native drivers are present when installing Infomaker



CR:156241
CR Number:   156241
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   MS Windows NT 3.51
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
Year 2000 and editmask: dw with a dateTime field, edit mask of YYYY, cannot accept the year 2000 It zeros out the edit mask. Years other than 2000, including greater than 2000, are okay.



Workaround: Using a mask of mm/dd/yyyy works fine.



CR:156242
CR Number:   156242
Product Name:   PB Enterprise
Product Component:   DW Painter
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
Editmask on string column that uses 0 in mask definition. 0 (zero) not treated as character. 1 - 9 work fine. (User wants to set (406)@@@- @@@@ as editmask for phone numbers



CR:156245
CR Number:   156245
Product Name:   PB Enterprise
Product Component:   Project Painter
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
Project Painter. Changing library path for dlls when making 16-bit machine code exe unchecks DLL and you can't check it again.



CR:156249
CR Number:   156249
Product Name:   PB Enterprise
Product Component:   DW Painter
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
poiuwqeiopruqweroiq uprqwoeir uweproweoru



CR:156252
CR Number:   156252
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   MS Windows NT 3.51
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
GetItemString on computed field that uses a global function on dw. Field is populated with a function that retrieves a text column from database. Col is 600 characters in size. Computed field displays characters correctly, but GetItemString won't return the entire contents of the field.



CR:156254
CR Number:   156254
Product Name:   PB Enterprise
Product Component:   DB MS SQLServer
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
Pipeline problem with MSS (Microsoft SQL Server native driver and piping blob columns. This issue is a problem with MS SQL Server 6.5 replication of an IMAGE column that is corrupted by PB using the native driver MSS. TEXT columns aren't corrupted during replication.

Development: This is a serious problem as the pipeline starts a transaction and the MSS driver tries to open a new connection for writing blobs causing MS SQL Server to hold a page lock on the created table and the second connection hangs.

Workaround:
Until the code in MSS driver is modified to not open a new DB connection for writing BLOBs use AutoCommit true for BOTH source connection and destination connection AND use commit factor = 1 in the pipeline painter. This will prevent pipeline to start a transaction and the MS SQL server will not put a page lock on the created table.



CR:156262
CR Number:   156262
Product Name:   PB Enterprise
Product Component:   C++ Class Builder
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
Watcom C++ Dubugger not working when launched from within Powerbuilder. On WIN95 a page fault occurs in WDW.EXE. NT4.0 blinks for a second and then you can't exit out of it.



Developers comments:

==================

This issue is purely a configuration issue. The following lists the issues to aid customers in resolving these issues.



Windows 3.x & Windows for Workgroups 3.x

--------------------------------------------------------------

To address the configuration issues for Win 3.x (includes Windows for Workgroups 3.x)

we must examine the AUTOEXEC.BAT and CONFIG.SYS files. These files determine the primary environment which is passed to windows when it starts.



For Win 3.x ensure that:



1) the class builder directory is the first directory in the PATH environment variable.



2) the WATCOM environment variable is set to the path (no filename) where the product was installed (eg: C:\WATC).



3) the EDPATH environment variable is set to the path (no filename) where the watcom editors data files are stored (eg: C:\WATC\EDDAT).



4) the INCLUDE environement variable is set to the path (no filename) where the header files are located (eg: C:\WATC\H;C:\WATC\H\WIN;C:\WATC\H\SYS ). If you specify only the header file root directory (eg: C:\WATC\H ) classbuilder will ASSUME that the additional headers are located in WIN and SYS subdirectories. If you have other compilers installed on your system which use the INCLUDE environment variable ensure that the watcom header files are first in the list.



5) no environment varaible exceeds 127 characters in length. With DOS 6.x the PATH environment variable could be 255 characters in length if set in the CONFIG.SYS.



6) wdebug.386 is in the [386enh] section of the SYSTEM.INI. It should be a fully qualified filename (ie includes the path to the file). This is virtual device driver for the debugger. If it is not present or didn't load and you start the debugger you can hang the system.



7) there is enough memory in the conventional memory area after powerbuilder is running.

Every windows virtual device driver and application consume some of this resouce. If you receive Out of Memory errors and the system resources indicate that there is still memory then you are out of conventional memory. There are utilites which can monitor this resource and let you know when you are running low. Other symptoms included system hangs. This problem is exasperated when using Windows or Windows for Workgroups on networks as the network drivers usually use substancial amounts of the conventional memory area.



8) any antivirus software is disabled while using classbuilder. Antivirus software interferes with the build process.





Windows NT

------------------

To address the configuration issues for WinNT (windows nt 3.x and 4.0 ) we must examine the registry. Note that modifying the registry may result in unrecoverable system failure. You should always uses the control panel applets to modify the registry whenever possible. There are two registry sections or hives that configure NT. The user specific hive HKEY_CURRENT_USER and the system hive HKEY_LOCAL_SYSTEM. The master command environment is determined as follows:



1) HKEY_LOCAL_MACHINE\CurrentControlSet\Control\Session Manager\Environment

2) HKEY_CURRENT_USER\Environment

3) AUTOEXEC.BAT.

4) HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths



The "master" environment is built from the local machine configuration and then the current users environment settings are applied. This means that the PATH environment variable is extended with the current users path, and duplicated environment variables take on the values from the current users environment. The processing of the AUTOEXEC.BAT file is controled from the registry. The default behaviour is to process it. Any environment variables not set in either of the registry keys are add to "master" environment space, as well the last path statement in the file is appended to the current users path.



To this point we have now built the "master" environment that will be passed to every process created on NT. This is not the end of environment processing however. There is optional information that is stored about applications in the registry. This is information that can only be viewed with the registry editor. This information is stored in the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths key. Every application is supposed to have an entry here. It consists of the application name and extension (eg: PB60.EXE). The default data value for this key is a fully qualified filename for the executable (eg: C:\Program Files\Powersoft\PB60.EXE). There can be additional keys to modify - if you guessed the environment your right - the environment. What is important here is that the PATH environment variable is extended with the directories in the PATH entry, but other environment variables are REPLACED.

This is relevant since PB launches the IDE from with in its own process space. Thus the "master" environment space will be augmented with the environment information from the App Paths\PB60.EXE key. It is the augmented environment that the IDE will be using and not the environment normally seen in the command prompt.



If you experience problems with the classbuilder for NT, you should ensure that:



1) the classbuilder directories are in the PATH environment variable for either:

a) HKEY_LOCAL_MACHINE\CurrentControlSet\Control\Session Manager\Environment, or

b) HKEY_CURRENT_USER\Environment, or

c) HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\PB60.EXE



2) the BINNT directory must always come before the BINW directory. There are both applications and dynamic link libraries that have the same name in both directories. It is imperative that the NT versions are picked up before the windows 3.x versions.



3) the WATCOM environment variable is set to the path (no filename) where the product was installed (eg: C:\WATCNT).



4) the EDPATH environment variable is set to the path (no filename) where the watcom editors data files are stored (eg: C:\WATCNT\EDDAT).



5) the INCLUDE environement variable is set to the path (no filename) where the header files are located (eg: C:\WATCNT\H;C:\WATCNT\H\NT;C:\WATCNT\H\WIN;C:\WATCNT\H\SYS ). If you specify only the header file root directory (eg: C:\WATCNT\H ) classbuilder will ASSUME that the additional headers are located in NT, WIN, and SYS subdirectories. If you have other compiler installed on your system which use the INCLUDE environment variable ensure that the watcom header files are first in the list.



6) the lmain.cpp file contains a dlllmain section and not just a libmain section. The file should look like this:



/* This file is generated by PowerBuilder.

* You may modify it in any way you wish but do not remove

* Libmain and WEP. Without them you will be unable to link your DLL.

*/



#include <windows.h>

#include "pbdll.h"



#ifdef __NT__



extern "C" {



int __stdcall DLLMain( DWORD, DWORD reason, DWORD )

{

if( reason == DLL_PROCESS_ATTACH ) {

extern char __WD_Present;

if( __WD_Present ) { // this is a hook for the Watcom debugger.

extern void Int3WithSignature( char __far * );

#pragma aux Int3WithSignature parm caller [] = "int 3" "jmp short L1" 'W' 'V' 'I' 'D' 'E' 'O' "L1:"

Int3WithSignature( "DLL Loaded" );

}

}

return( 1 );

}



};



#else



int PB_EXPORT LibMain( HANDLE, WORD, WORD, LPSTR )

{

return( 1 );

}



int PB_EXPORT WEP( int )

{

return( 1 );

}



#endif // PowerBuilder code, do not remove



If it does not look like this then replace it with this one. The HELLO sample that shipped with the 10.5 ClassBuilder for NT suffers from this problem. This will cause a variety of problems such as stack faults, Access Violations, or a hung processe.



7) any antivirus software is disabled while using classbuilder. Antivirus software interferes with the build process.





Windows 95

------------------

To address the configuration issues for Win95 we must examine both the AUTOEXEC.BAT and the registry. Note that modifying the registry may result in unrecoverable system failure. You should always uses the control panel applets to modify the registry whenever possible. The master command environment is determined by the AUTOEXEC.BAT if it exists or by the io.sys file. This "master" environment will be passed to every process created on 95. This is not the end of environment processing however. There is optional information that is stored about applications in the registry. This is information that can only be viewed with the registry editor. This information is stored in the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths key. Every application is supposed to have an entry here. It consists of the application name and extension (eg: PB60.EXE). The default value for this key is a fully qualified filename to the executable (eg: C:\Program Files\Powersoft\PB60.EXE). There can be additional keys used to modify - if you guessed the environment your right - the environment. What is important here is that the PATH environment variable is extended with the directories in the PATH entry if it exists, but other environment variables are REPLACED.



This is relevant since PB launches the IDE from with in its own process space. Thus the "master" environment space will be augmented with the environment information from the App Paths\PB60.EXE key. It is the augmented environment that the IDE will be using and not the environment normally seen in the dos prompt.



If you experience problems with the classbuilder for NT, you should ensure that:



1) the classbuilder directories are in the PATH environment variable for either:

a) AUTOEXEC.BAT

b) HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\PB60.EXE



2) the BINNT directory must always come before the BINW directory. There are both applications and dynamic link libraries that have the same name in both directories. It is imperative that the NT versions are picked up before the windows 3.x versions.



3) the WATCOM environment variable is set to the path (no filename) where the product was installed (eg: C:\WATCNT).



4) the EDPATH environment variable is set to the path (no filename) where the watcom editors data files are stored (eg: C:\WATCNT\EDDAT).



5) the INCLUDE environement variable is set to the path (no filename) where the header files are located (eg: C:\WATCNT\H;C:\WATCNT\H\NT;C:\WATCNT\H\WIN;C:\WATCNT\H\SYS ). If you specify only the header file root directory (eg: C:\WATCNT\H ) classbuilder will ASSUME that the additional headers are located in NT, WIN, and SYS subdirectories. If you have other compiler installed on your system which use the INCLUDE environment variable ensure that the watcom header files are first in the list.



6) the lmain.cpp file contains a dlllmain section and not just a libmain section. The file should look like this:



/* This file is generated by PowerBuilder.

* You may modify it in any way you wish but do not remove

* Libmain and WEP. Without them you will be unable to link your DLL.

*/



#include <windows.h>

#include "pbdll.h"



#ifdef __NT__



extern "C" {



int __stdcall DLLMain( DWORD, DWORD reason, DWORD )

{

if( reason == DLL_PROCESS_ATTACH ) {

extern char __WD_Present;

if( __WD_Present ) { // this is a hook for the Watcom debugger.

extern void Int3WithSignature( char __far * );

#pragma aux Int3WithSignature parm caller [] = "int 3" "jmp short L1" 'W' 'V' 'I' 'D' 'E' 'O' "L1:"

Int3WithSignature( "DLL Loaded" );

}

}

return( 1 );

}



};



#else



int PB_EXPORT LibMain( HANDLE, WORD, WORD, LPSTR )

{

return( 1 );

}



int PB_EXPORT WEP( int )

{

return( 1 );

}



#endif // PowerBuilder code, do not remove



If it does not look like this then replace it with this one. The HELLO sample that shipped with the 10.5 ClassBuilder for NT suffers from this problem. This will cause a variety of problems such as stack faults, Access Violations, or a hung processe.



7) wdebug.386 is in the [386enh] section of the SYSTEM.INI. It should be a fully quallified filename (ie includes the path to the file). This is virtual device driver for the debugger. If it is not present or didn't load and you start the debugger you can hang the system.



8) any antivirus software is disabled while using classbuilder. Antivirus software interferes with the build process.



CR:156263
CR Number:   156263
Product Name:   PB Enterprise
Product Component:   Window - Runtime
Status:   Closed
OS:   Solaris 2.5.1
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
There are several interrelated bugs with sles:



1) SLE with more text than fits into sle displays differently on Unix than it does on Intel or Mac. This depends on whether text is set in properties or from script, whether Auto HScroll is checked or unchecked, and whether the sle has focus or not.



2) Even with Auto HScroll unchecked, you can use the Home and End keys to get to the beginning/end of the sle, but you have to press them twice.



3) Previously reported: with Auto HScroll unchecked, you can type more into an sle than will 'fit'. Once there is too much text, the arrow keys move past the displayed text, and you can't see the cursor. On Intel or Mac, arrow keys won't move past displayed text.



4) If the sle text is set in object properties, when you tab or click into the sle, the beginning of the text displays, even if the end was showing when the window opened. If sle text is set from script, when you click or tab to the sle, whatever was showing originally remains showing.



CR:156265
CR Number:   156265
Product Name:   PB Enterprise
Product Component:   DW Rich Text
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
Users are unable to insert the value contained within a computed field into an RTE control. All other fields work fine.



CR:156268
CR Number:   156268
Product Name:   PB Enterprise
Product Component:   DB Sybase System
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
System 10 SYC RPC: when an uninialized decimal is returned into a decimal and there are more than 2 decimal places, get warning message: scale error during implicit conversion of decimal value 12345.768 to decimal field. The number was returned as 12345.670. Database definition is decimal(18,3)



PER DEVELOPMENT:

Change category to enhancement:

Want ability to pass how many decimal places we want in the declaration of a Local External Function in User Object Painter



CR:156269
CR Number:   156269
Product Name:   PB Enterprise
Product Component:   Window - Runtime
Status:   Closed
OS:   MS Windows 3.1
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
Autoinstantiated NVOs cause runtime DLLs to not be released from Memory. Very similar to bug 41327.



CR:156271
CR Number:   156271
Product Name:   PB Enterprise
Product Component:   OLE - Active X - OCX
Status:   Closed
OS:   MS Windows NT 3.51
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
ole activation (in place!) does not appear to be working correctly. It looks as if the ole control is activated off site.



CR:156272
CR Number:   156272
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
14 Apr 1999 Third Party Problem
Description
Presence of titlebar on child window changes behavior of cursor positioning within a large column on a datawindow on that child window. You cannot position the cursor within the column using the mouse (clicking) if there is a titlebar on the child window. Tab does work.



Probably related to other child window bugs determined to be a Microsoft bug by development.



Possible Workaround:

- Map an event to pbm_lbuttonup for each control put on the child window that has this problem with clicking not setting focus to the control.

- In the event, code the following "This.setfocus()"



RESOLUTION: This is an operating system problem. It has been reported to Microsoft. The reference number for the issue is: SR X99041360189



Datawindow specific problems with titlebars

==================================

For datawindows containing titlebars, you will see the same behavior of not being able to position the cursor in the edit control. this problem is a little harder to workaround:

- Create a custom visual user object with 2 datawindow controls. One with it's titlebar (dw_titlebar) and one without dw_dataobject (the one that will contain the dataobject). Position and size the dw_titlebar (turn titlebar attribute on, make the control 3D raised and the background color GREY) just above dw_dataobject and make it show only the titlebar (this datawindow control will never actually have a dataobject assigned - it's used solely to simulate a titlebar on the second control 'dw_dataobject.'

- Create a custom user event on dw_titlebar mapped to pbm_move (call it "move")

- In the Contructor event of dw_titlebar, put dw_dataobject.width = dw_titlebar.width - 5 // accounts for border.

- In the "move" custom user event on dw_titlebar, place the following in script:

dw_dataobject.x = xpos - 8 // accounting for border again.

dw_dataobject.y = ypos

- Call the custom visual user object uo_dwtitlebar and place one on the window. Now when you pick up the datawindow control and they will move together AND more importantly, you can type into the SLE's on the datawindow in the "dw_dataobject" control. The scripting is a bit more involved, but it works.



uo_dw.dw_dataobject.retrieve() or you could write custom user events or functions so uo_dw.retrieve() will do what you expect.



CR:156275
CR Number:   156275
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   MS Windows NT 3.51
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.00 RC 05 Jan 1999 Fixed
Description
Numeric retrieval arguments are not passed correctly to a child datawindow with retrieval argument. Decimal part of the argument is lost at nested level.



CR:156276
CR Number:   156276
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.04
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
On a datawindow, different validation behavior for date column and integer column that don't contain edit mask.



CR:156282
CR Number:   156282
Product Name:   PB Enterprise
Product Component:   Language - Runtime
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
Problem using direct notation instead of the GetItem() function when the row number is greater than 32767. Error: "PowerBuilder Application Execution Error (R0039)

Application terminated. Error: Error accessing external object property"



Development: Will not be fixed in the 5.0 codebase. Use GetItemXXX functions instead. Fixed in 6.0. 16 and 32 bit problem.



CR:156287
CR Number:   156287
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   MS Windows NT 3.51
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
The OK button of the prompt for criteria dialog is not a default anymore in 32 bit (works ok in 16 bit and version 4)



CR:156291
CR Number:   156291
Product Name:   PB Enterprise
Product Component:   DW Rich Text
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
05 Jan 1999 Duplicate
Description
5.0.03 and panther 103. RTE style datawindow. When showing the header/footer, I can get PB to freeze.



Steps to recreate using the pbl in ptfiles:

1. Open d_rte_with_2_computed in the datawindow painter.

2. Go into preview.

3. Click on the menu item design, then header/footer.

4. Scroll up the footer, so that you see "page 1 of 5".

5. Click on the 'last' button on the toolbar.

It now says 'page 5 of 5'.

6. Now, click on the 'prior' button on the toolbar.

PB freezes. When you hit cntl/alt/delete, it shows it as not responding.



CR:156294
CR Number:   156294
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16 Dec 1998 Not a Bug
Description
Using setitemstatus() function to change the status of a new row from NewModified! to DataModified! doesn't work properly : the status of each column which was DataModified! becomes NotModified!.

Development: The test case does a RowsCopy into another DW, the rowstatus is newmodified! (as expected) and the columns are all datamodified!. When reporting the status of the columns we are making the ASSUMPTION that if the row is NEW and there is SOME value in the column it is datamodified!

The test then sets the rowstatus to datamodified! ... this actually does nothing to the columns status.

When we report the status of columns now, we make the assumption that if the row is NOT new and there is no ORIGINAL data associated with the column then the column status is notmodified!

Remember, we look at original column values as kind of an undo facility and if there is nothing to undo then the data isn't modified except of course in the above example where a row status of newmodified! forces the column status to be datamodified!.

This is 'intended behavior'



CR:156295
CR Number:   156295
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   MS Windows 3.1
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
24 Sep 1998 Not reproducible with latest version of the product available as of Resolution Date
Description
n a datawindow with a column col1 with password attribute and another column col2 with the ddlb edit style, the data in col2 is lost after calling modify() function to change the background color of col1 and col2.



CR:156299
CR Number:   156299
Product Name:   PB Enterprise
Product Component:   Menus - Runtime
Status:   Closed
OS:   MS Windows 3.1
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
16 bit only: PB menu: double click on first menu item is incorrectly interpreted / behaves as double click on Control menu, and closes application.



CR:156302
CR Number:   156302
Product Name:   PB Enterprise
Product Component:   DW Rich Text
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
Rich Text Datawindow. Turning ruler on using the Popup Menu after the datawindow has been painted and previewed causes incorrect numbers to be displayed for left margin. Some cases, -2 inches, others -22 inches.



CR:156303
CR Number:   156303
Product Name:   PB Enterprise
Product Component:   DW Rich Text
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
Rich Text Datawindow in painter. Fields with fixed width and data that have trailing spaces (or _). The underlined spaces don't show up in preview. The underlined spaces are truncated at the field width.



CR:156304
CR Number:   156304
Product Name:   PB Enterprise
Product Component:   DW Rich Text
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
In VGA resolution, a rich text datawindow page break doesn't move down when inserting lines of text above it. Like any word processor, the page break - denoted by a dotted line - should move.



Workaround: Go in and out of Print Preview and notice the dashed line (page break) is now in the correct place.



CR:156308
CR Number:   156308
Product Name:   PB Enterprise
Product Component:   Window - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   5.0.03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
VCI Grid in a Window: After populating a VCI grid programmaticly, turning redraw off, filling in the data, and then turning redraw on, the data does not appear visually until the user clicks in the grid.



CR:156312
CR Number:   156312
Product Name:   PB Enterprise
Product Component:   DB Oracle
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
Using oracle 7.2. Customer has number and float datatypes. In pb, datatypes show extra precision at the end. If they use decimal zero, then everything works ok, but they need the decimal places.



They have table with column defined as number (table created outside PB). In Oracle, this is floating point with precision 38. In datawindow painter, comes up as float.

Some numbers come up with extra precision at the end, and that column cannot be updated.



CR:156313
CR Number:   156313
Product Name:   PB Enterprise
Product Component:   Window Painter
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
Treeview ItemExpanding is triggering Itempopulate on last item even though return 1 was sent to prevent this.



PER DEVELOPMENT:

have reproduced the above-described behavior. However, the behavior is correct since ItemPopulate is called before ItemExpanding. Therefore the return value of ItemExpanding can't be used as a means to prevent the tree population. In order to prevent the tree expansion and population both methods have to use the counter ii_countit.



CR:156315
CR Number:   156315
Product Name:   PB Enterprise
Product Component:   DB MS SQLServer
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   5.0.04
Fixed Version Build Resolution Date Closure Code (If Appropriate)
21 Dec 2000 Presently Not Targeted For Any Future Release Of This Product
Description
Connecting to MS SQL Server using named pipes and the explicit name of the server (instead of the dot) is not working (error 10003, login incorrect)



CR:156318
CR Number:   156318
Product Name:   PB Enterprise
Product Component:   DB Oracle
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
Using RPCFUNC to return array from PL/SQL table is giving page fault in pbrte051.dll at 0137:99754c53. Array of strings or numbers gives same error.



CR:156325
CR Number:   156325
Product Name:   PB Enterprise
Product Component:   Toolbar
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
Can not move or create windows when SetRedraw=False.



PER DEVELOPMENT:

Functions as designed. This is the purpose of SetRedraw(false)



SetRedraw=FALSE should only be used at the start of a performance sensitive piece of code. A SetRedraw=TRUE should follow the performance sensitive section.



CR:156327
CR Number:   156327
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.0.01 17 Apr 1998 Fixed
Description
GPF in MSVCRT40.DLL in Win95 when the default printer is HP 5L (driver hppcl5g.drv) and doing a print, then some dot notation inside to a numeric column in a datawindow such as:

long ItestID

double dtest



lTestId = dw_1.GetItemNumber(1,"test1_id") /* long in datawindow */

dTest = dw_1.GetItemDecimal(1,"amount") /* number in datawindow */

lTestId = dw_1.GetItemNumber(1,"test2_id") /* long in datawindow */



where test1_id, test2_id are null. GPF's on the last line.



CR:156331
CR Number:   156331
Product Name:   PB Enterprise
Product Component:   Window - Runtime
Status:   Closed
OS:   MS Windows 3.1
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
If the argument to the timer function is larger than documented range (0 to 65) then it seems to work with the large argument in 32 bit Powerbuilder, but not in 16 bit Powerbuilder. 16 bit Powerbuilder seems to use the first two digits of the argument instead. For example, if you code Timer(300) the timer event fires every 5 minutes in 32 bit Powerbuilder, but in about every 30 seconds using 16 bit Powerbuilder. Not yet known whether it is a bug that 300 works for 32 bit, or will we add an error message that the argument is invalid. Or possibly documentation is incorrect and 300 should work now in 16 bit. WORKAROUND: Use an argument to the Timer() function which is within the documented range of values, 0 to 65, and an instance variable counter to count interations of the timer event, and execute the script when the desired iteration is hit. As in the example, if you want the Timer Event script to fire every 5 minutes, use Timer(60) for the timer function, and add a counter which is incremented each time the timer event fires. While the counter is less than 5, just return from the Timer Event script without doing anything. When it reaches 5, reset the counter, and execute the rest of the timer event script. Arguments to the timer function that are within the documented range of valid values behave the same whether running 16 or 32 bit Powerbuilder.



CR:156333
CR Number:   156333
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   MS Windows 3.1
Original Version:   5.0.03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
When using SaveAs() to save a DataWindow in dbf, dBASE3 format, long (memo type) columns are being truncated after 255 characters.



CR:156334
CR Number:   156334
Product Name:   PB Enterprise
Product Component:   DW SaveAs
Status:   Closed
OS:   MS Windows 3.1
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0 Beta 4 19 Sep 2002 Fixed
Description
SaveAs with Dbase3 format has 2 problems

1) It doesn't respect definition of decimal fields : the decimal part is lost

2) When Windows decimal separator is comma it saves decimal number with comma but dbase wants a dot.



CR:156335
CR Number:   156335
Product Name:   PB Enterprise
Product Component:   Business Graphics
Status:   Closed
OS:   MS Windows 3.1
Original Version:   4.0.06
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
using cumulativesum in a datawindow graph produces wrong result if for one abscisse several occurences are returned by the select statement



CR:156336
CR Number:   156336
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.00 23 Sep 1998 Presently Not Targeted For Any Future Release Of This Product
Description
After populating a Date field in a DataWindow and opening a Response Window, the date field is highlighted up to where the moouse cursor is and continues to be selected and deselected by mouse movement only until it's clicked. Happens in 16 bit Powerbuilder only running on the Windows 95 platform.



CR:156337
CR Number:   156337
Product Name:   PB Enterprise
Product Component:   DW Painter
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.00 31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
Powerbuilder ignores the Windows setting (hh:mm) for time when using [time] format in edit masks or in display formats

PER DEVELOPMENT:
All that is read from the Windows setting is the separator character. This has always been the case in PowerBuilder, and we do not want to change this because it could greatly impact existing customer applications. A change request will be logged to update the documentation to reflect what we really do: read the separator character.



CR:156338
CR Number:   156338
Product Name:   PB Enterprise
Product Component:   DW Painter
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.0.01 19 Nov 1998 Not a Bug
Description
Documentation states keywords inside Edit Masks and Display Formats are fully interchangeable. They are not: [date] is only valid for an edit mask, and [shortdate] or [longdate] are only valid for display formats.



CR:156340
CR Number:   156340
Product Name:   PB Enterprise
Product Component:   DW Rich Text
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
Printing RichText Presentation Style datawindow objects. All hyphens ("-") are translated to a line break regardless of the type of the printer when you print a Datastore with it's object being of type RichText presentation style and with WordWrap ENABLED. This does not happen if you use the same dataobject and a datawindow.

This does not happen if DISABLE wordwrap.



CR:156341
CR Number:   156341
Product Name:   PB Enterprise
Product Component:   DW Painter
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12 Apr 1999 Not a Bug
Description
It seems that a DataWindow that is set up to print in landscape mode occasionally determines the number of pages to print incorrectly, resulting in the trailer band overprinting the header band on the last page.

Per Development:
No-bug -- the DW design breaks the internal rule that the last row plus any trailing group trailers plus any summary band must fit within the printed page. Any overflow off the end of the page, spills over onto the next page without proper pagination. The text doesn't overlap the header text, due to recent patches, but a line of text could be cut in half. There are many formulas withn the DW Engine, that depend on this rule. This will not change until new DW design rules are implemented in some future PB release.



CR:156343
CR Number:   156343
Product Name:   PB Enterprise
Product Component:   DW Painter
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
Sometimes, a column in a DataWindow containing multiple lines will word wrap differently in the datawindow painter print preview than what is printed.



PER DEVELOPMENT:

Unfortunately this is not a bug. It is true in 4.0 and 5.0 and Panther as well. The problem is that even in print preview we are painting to a different (not a printer) device and the font sizes and spacings can be subtly different. So it would be surprising if they DID wrap exactly the same.



Moreover, in this specific example, we are using the Win API call "TextOut" to write the text and we are sending it the same parameters in preview as in print so, someone downstream from us (GDI or the specific print driver) is making further adjustments before it gets on the paper.



A Datawindow print preview is an approximation of how it will look on the paper and cannot be expected to be exact.



CR:156344
CR Number:   156344
Product Name:   PB Enterprise
Product Component:   Language - Runtime
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Not reproducible with latest version of the product available as of Resolution Date
Description
Problem: A variable of type any is assigned a NULL date value. It is passed by value as an argument type any) to a function. Inside the function, it appears as an argument of type any, not of type date. When it is passed by reference, it shows as a NULL date inside the function



CR:156345
CR Number:   156345
Product Name:   PB Enterprise
Product Component:   DB Sybase System
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
Using SYC database interface, sql syntax errors are not consistently reported by the script painter even though "Display Database Warnings" script property is set on. You will get errors until the script compiles successfully, but then if you make changes to the script which include invalid sql syntax, you do not get the error messages anymore. Also tested using ODBC to SQL Anywhere and O72 to Oracle 7.2, and those db interfaces continued to report syntax errors. Could not reproduce the problem using those two interfaces.



CR:156346
CR Number:   156346
Product Name:   PB Enterprise
Product Component:   DB Oracle
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
5.1_103 Oracle: stored functions called as RPC not returning return value properly. Similar bug reported in 402747: 5.1 is not returning anything if integer return value is returned to integer, is returning 0 if integer return value is returned into a long. Not database specific.



This is behaving somewhat differently:

If number return is returned into an integer or a long, 0 is returned if the stored function is standalone. If the function is part of a package, different incorrect numbers are returned depending on whether integer is returned into an integer or a long.



In both cases, stored function does nothing except return 10.



CR:156350
CR Number:   156350
Product Name:   PB Enterprise
Product Component:   PB GUI
Status:   Closed
OS:   Solaris 2.5.1
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
Solaris PB 5.0 running slow under Unix.



CR:156351
CR Number:   156351
Product Name:   PB Enterprise
Product Component:   DW Painter
Status:   Closed
OS:   MS Windows 3.1
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
Customer has a nested dw with filter expression set. When previewing the datawindow filter is ignored and all the rows are retrieved for the nested datawindow. Only reproducible with PB versions after 4.0.05.



CR:156353
CR Number:   156353
Product Name:   PB Enterprise
Product Component:   Machine Code Exe Creation
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
When running Powerbuilder from the network and generating machine code, several developers jobs can collide because .h, and .pch files get written to the \CGEN directory on the network drive. The first build works fine but all other builds fail. This can be extremely inconvenient.



Enhancement: The ability to set an environment variable or setting in the pb.ini file to redirect the placement of the .h, .pch files to the local drive or some other drive so multiple developers don't get collisions.



WORKAROUND: If you create any machine code executable logged on locally into the actual FILE SERVER machine on the network - the one containing the PB software - the .h and .pch files will be created ONCE. After that, all users accessing the network software remotely to create executables will no longer have this problem.



CR:156355
CR Number:   156355
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0 Beta 1 16 Aug 2000 Fixed
Description
Importfile: Argument for which row to start import is ignored if the file name is left empty string to have user select the file from dialog. If the file name is provided the row number argument works correctly.

Per development: This is working as designed. CR was revised to go to documentation instead. If this is correct behavior, we should add a note in the ImportFile documentation.



CR:156356
CR Number:   156356
Product Name:   PB Enterprise
Product Component:   DPB
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
If a client breaks a connection abnormally, such as via NT Task Manager End-Task or WIN95 Task Manager, NO clients can connect to the Server application. Error 52 Distributed Communications WINSOCK_RECV_ERROR occurs.

The only way any subsequent connections can be made is by shuting down/restart the server application.



CR:156362
CR Number:   156362
Product Name:   PB Enterprise
Product Component:   DPB
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
In DPB if you try to generate a log file whose name is 8 characters in length, and a file with the same name plus additional character(s) at the end of the name already exists on disk, the contents of the file is actually overwritten. Happens for both client connection object trace, and server transport trace.

**This only happens on WIN95



PER DEVELOPMENT:

This is a problem with WIN95 explorer. The rename to a long file name is leaving the DOS file name as the old one. If the different names are all specified from Log=, then everything works properly.



CR:156363
CR Number:   156363
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.5.00 09 Nov 1998 Not a Bug
Description
win 95 and win nt 4.0

32 bit {pb 5.0.02_11, pb 5.0.03_35, pb 5.0.04_31}



Page breaking on a preview of a datawindow is sporadic. Open datawindow ds_report_annual_airlift_main. Preview dw. At the bottom of the first page see ATL HOW. One line (USMC) appears below and there seems to be enough room at the bottom of the page to continue but the rest is continued on the next page.



I canot event preview the dw in nt 4.0 . The app is sucking up resources big time. Normaly it can take about 2 mins to preview , and every time you preview the dw it takes longer and longer until you run out of memory



CR:156364
CR Number:   156364
Product Name:   PB Enterprise
Product Component:   DW Painter
Status:   Closed
OS:   MS Windows NT 3.51
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.00 22 Jun 1999 Fixed
Description
String datatype on a column with editmask of ##### (numeric), if you type in 12345, then highlight 123 and replace it with a 2 you end up with 25 instead of 245. If the datatype is number instead it works. The DELETE key normally deletes characters to the right of the cursor. But when something is highlighted, it should not act this way, it should replace characters. It still delets one character to the right of the hightlighted text.



CR:156365
CR Number:   156365
Product Name:   PB Enterprise
Product Component:   OLE - Active X - OCX
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
HTML Editors require the LibList path name to be followed by a semicolon. If the semicolon is not there, the editor will hang. This occurs with Microsoft FrontPage and Microsoft Control Pad. Powerbuilder delimiter should not be required?



CR:156368
CR Number:   156368
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
24 Sep 1998 Not a Bug
Description
SetItem and ImportString used on a datawindow handle a value of an empty string ("") differently. SetItem results in an empty string value in the datawindow column, ImportString results in a Null value in the datawindow column. The setting of "Empty String is Null" on the datawindow column does not make any difference.



CR:156375
CR Number:   156375
Product Name:   PB Enterprise
Product Component:   DB Sybase System
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   4.0.06
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.0.04 06 May 1999 Not reproducible with latest version of the product available as of Resolution Date
Description
PBSYC interface : When trying to create a datawindow based on a stored procedure which has an argument of type int, gets the error "implicit conversion from datatype 'VARCHAR' to 'INT' is not allowed. Use the convert function to run this query."



CR:156385
CR Number:   156385
Product Name:   PB Enterprise
Product Component:   DB SQLAnywhere
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.04
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.00 EBF1 6001 07 Apr 1999 Fixed
Description
When you save a datawindow in the dw painter, Pb doesn't save the width attribute defined for a col. header. It occurs only with a grid datawindow.



CR:156390
CR Number:   156390
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
Long varchar column on a dw. Has Auto Vert scroll turned on. If the height of the column is changed slightly, the behavior of DW when the Enter Key is pressed changes. It looks to me as if the column must be high enough to display at least two lines in order for the Enter key to work within the same datawindow row/column.



CR:156395
CR Number:   156395
Product Name:   PB Enterprise
Product Component:   Language - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   5.0.03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
dividing a decimal by integers is giving a wrong result.



CR:156396
CR Number:   156396
Product Name:   PB Enterprise
Product Component:   Language - Runtime
Status:   Closed
OS:   MS Windows 3.1
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
After assigning a row of a datawindow with a decimal column to a structure with a decimal field using dot notation, the decimal field behaves like an integer : any value you try to put in the field is rounded to an integer.



CR:156397
CR Number:   156397
Product Name:   PB Enterprise
Product Component:   DB ODBC
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
'Data Truncated" error fetching a blob from DB2/NT through ODBC > 32k bytes through a stored procedure. Using SelectBlob does work but this requires explicit privileges on the underlying table - a security issue. If a stored procedure is used, users need only have execute privilege on the package associated with the stored procedure. This prevents users from accessing the sensitive data from any means other than the stored procedure



Fetch: SQLSTATE 01004 [IBM][CLI Driver] CLI0002W Data Truncated . SQLSTATE 01004.



CR:156408
CR Number:   156408
Product Name:   PB Enterprise
Product Component:   Window - Runtime
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
Hebrew/Arabic - In 4.0 and MS Hebrew/Arabic versions, you can use CTRL+Shift and ALT+Shift to switch between Hebrew/Arabic and English. In PB, this does not work correctly Win95 or Win 3.1. In Win 95, it will change character sets and direction the first time, but the second time you use it, it only changes the character set. In 3.1, they do not work at all The Hebrew/Arabic and English buttons do not work properly in either 3.1 or Win 95.



PER DEVELOPMENT:

microsoft bug - notepad gives same behavior



CR:156412
CR Number:   156412
Product Name:   PB Enterprise
Product Component:   Function Painter
Status:   Closed
OS:   MS Windows NT 3.51
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
In function painter, it's not possible to give the precision of an argument of type decimal : DECIMAL{n} is not authorized as a datatype of an argument. Only DECIMAL is authorized.



CR:156415
CR Number:   156415
Product Name:   PB Enterprise
Product Component:   Library Painter
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
02 Nov 1998 Duplicate
Description
Library Painter open in two windows, changes made while in one instance of Painter not reflected in the other instance of the painter.



Is this a bug ? Trying other Windows products, most refresh, some do not. For example, Explorer will refresh the file list when changes are made to directories, but File Manager does not refresh if two windows are open viewing the same directories.



CR:156420
CR Number:   156420
Product Name:   PB Enterprise
Product Component:   Business Graphics
Status:   Closed
OS:   MS Windows 3.1
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
PB 16-bits only : on a graph control, calling the insertdata() or adddata function() after calling reset(all!) produces a memory leak. If occurs only when the categoryvalue argument is specified.



CR:156423
CR Number:   156423
Product Name:   PB Enterprise
Product Component:   Debugger
Status:   Closed
OS:   MS Windows NT 3.51
Original Version:   5.0.03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.00 Beta 3 3245 30 Nov 1998 Fixed
Description
Problem: Changing value of a reference variable in debug mode will cause gpf



CR:156425
CR Number:   156425
Product Name:   PB Enterprise
Product Component:   Language - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
Autoinstantiated NVO passing bound array of type string, with values defined GPFs. Removing autoinstantiate and coding creates /destroys works fine.



CR:156426
CR Number:   156426
Product Name:   PB Enterprise
Product Component:   DB Sybase System
Status:   Closed
OS:   Solaris 2.5.1
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
Solaris - SYC not working for distributed applications for a threads safe driver.



PER DEVELOPMENT:

New driver added to 503 code base SYD it is a thread safe version of SYC. syd - needs to be in the vendors list in the .pb.ini. SYD is used just like SYC except SYD is listed as the DBMS.



CR:156430
CR Number:   156430
Product Name:   PB Enterprise
Product Component:   DW Painter
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
09 Jan 2001 Fixed
Description
I can create a composite dw with two crosstabs with retrieve arguments, but I cannot add a crosstab with retrieve arg to an existing composite. I get an error message "Crosstab nested report has retrieval arguments and can only be used in composites". It is a composite, so the error message doesn't make sense.



WORKAROUND: You can include multiple crosstab datawindows with arguments on a composite, you just can't add one later, so you have to create a new composite that includes the crosstab you're trying to add.



CR:156432
CR Number:   156432
Product Name:   PB Enterprise
Product Component:   Language - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   5.0.03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
Calling MessageBox from the endeditlabel event is causing a stack overflow.



Developer: This one isn't a bug, it's one of a class of "bugs" that we call the "good old messagebox" problems. Basically what is happening is that one event is triggered when a control loses focus and that event causes the control to lose focus which causes the event to be triggered which causes the control to lose focus which causes the event to be triggered which causes the control to lose focus which causes the event to be triggered... ad infinitum, as nauseum.



The real point is this: don't use the messagebox to send messages from focus-sensitive events, rather send text to a status object (sle, console window, etc.)



CR:156433
CR Number:   156433
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   5.0.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
pbm_dwnkey event : The Numeric keypad's "period" key is not generating a pbm_dwnkey event. (KeyDecimal! does not fire this event)



WORKAROUND:

Editchanged event is triggered for each keystroke in the datawindow. Check if KeyDown(KeyDecimal!) = true to trap numeric keypad decimal key.



CR:156434
CR Number:   156434
Product Name:   PB Enterprise
Product Component:   DB Other
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
MDI Interface, Placing comments using " /* ... */" in the middle of a SQL Statement is being Interpreted incorrectly.



CR:156439
CR Number:   156439
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
Using GetRow() function with datastore. In 5.0.02 it would return 1, in 5.0.03_22 it returns 0.



CR:156443
CR Number:   156443
Product Name:   PB Enterprise
Product Component:   DB ODBC
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.0.00 17 Apr 1998 Fixed
Description
Auto-incrementing double columns default to a value of -1.082593065378032E+51 instead of the appropriate number. The value is correct when you re-retrieve the rows.



CR:156454
CR Number:   156454
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
N-up datawindow: computed columns defined in the footer band are not working correctly. Move them up to the detail band and then they display correctly.



CR:156459
CR Number:   156459
Product Name:   PB Enterprise
Product Component:   Language - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   5.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
If pbm_dwnkey event is triggered, and within that event script parent.ue_pbm_dwnkey is triggered passing the arguments to pbm_dwnkey directly, you get a gpf in PBRTE050.DLL. If you declare additional variables local to the pbm_dwnkey script, assign the input parameters to the local variable, and pass them to the parent.user event, the gpf does not occur. The problem and workaround are better shown in the below example:



Specifically, if you think of the events as functions:

//// the following causes a gpf

dw.pbm_dwnkey(keycode key, unsignedlong keyflags)

{

parent.ue_pbm_dwnkey(key,keyflags);

}



////changing the event to this works around the gpf:

dw.pbm_dwnkey(keycode key, unsignedlong keyflags)

{

keycode lkey

unsignedlong lkeyflags



lkey = key;

lkeyflags = keyflags;

parent.ue_pbm_dwnkey(key,keyflags);

}



The user event ue_pbm_dwnkey is correctly defined to expect these two arguments.



CR:156461
CR Number:   156461
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   MS Windows 3.1
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.5.00 09 Nov 1998 Not reproducible with latest version of the product available as of Resolution Date
Description
Structure assignment from datawindow buffers causing crash when data is fully populated.



str1[] = dw_1.object.data[1,1,5,4]



CR:156467
CR Number:   156467
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   MS Windows 3.1
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
String concatenation causes memory leak on Windows 3.11 platform.



CR:156477
CR Number:   156477
Product Name:   PB Enterprise
Product Component:   Language - Runtime
Status:   Closed
OS:   MS Windows 3.1
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
Using dot notation to assign value of string dw column to an array of characters.



Debugger shows the full string being assigned to the first member of the array, other members null. In other words only one character should be held for the first element, but instead you could have about 40 characters held. This should NOT be correct behaviour



If you specify a character array of length 1 then only one character is held. This is correct behaviour.



CR:156478
CR Number:   156478
Product Name:   PB Enterprise
Product Component:   Inheritance
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
In an inherited user object, overload a function uf_get() which returns an ANY value. From uf_get() function of the descendant, a call is made to the function uf_get() of the ancestor using the SUPER pronoun : it doesn't work. It's the descendant function which is called so it loops.



CR:156480
CR Number:   156480
Product Name:   PB Enterprise
Product Component:   DB ODBC
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
ODBC trace does not generate a log file, either running ODBC 2.0 or ODBC 3.0.23.1.

Works OK in 4.x and 5.x with either ODBC 2.0 or 3.0.



CR:156481
CR Number:   156481
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
Enhancement: Protect attribute based on expression isn't being enforced on newly inserted rows when the user tabs off the row and the datawindow control (and it should). The protect attribute for a particular column should be set to 1 and protected but if you tab off to another window control and tab back, you can still put focus (an edit control is created).

Workaround: (works for some). Filter() or Sort() directive in the losefocus event of the datawindow control to force the datawindow engine to re-evaluate the Protect attribute. NOTE: This generally is a problem on datawindows that are completely protected except for new rows inserted. The developer generally wants to immediately protect the new row when focus moves off the datawindow control.

PER DEVELOPMENT: THIS WILL BE CHANGED TO AN ENHANCEMENT REQUEST:

In the user's app, the protect attribute is being set when tab'bing to the second DW, BUT, you can still mouseclick back to the newly inserted row and still change the data. This is because everything else on the DW is protected and we have not completed the "editChange"/"editUpdate" processing, there is no other editable field to change to until another row is inserted. At that point, the protect attribute is in full force.
Here's the word on what is going on with this one:
(Using the user's app)

If you use insertrow() with the commandbutton, mouseclick on the newly inserted row, there is no current edit on the DW so we set an appropriate edit control window over the column.

Type some data

Click or tab away from the column and click or tab back we have an edit control and it's already there ... basically set the focus and that is that. This is where the customer wants us to have evaluated the protect attribute and disallow access to the column.

Insert another row.

Click on the same column as above, again we have an edit control and it is in the right place so we just set focus.

Click in the newly inserted column, we NOW have to move the edit control, go through editUpdate/editChange, the protect attribute is evaluated and enforced from this point on.

So, we ONLY evaluate and enforce the protect attribute for a gob on a DW if the edit control is moving to a new place.

I would be VERY shy about changing this order of events for fear of screwing up other customers or having a BAD impact on application performance as a result of too often re-evaluating too many expressions.



CR:156482
CR Number:   156482
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   MS Windows 3.1
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.0.04 17 Apr 1998 Fixed
Description
Graph object on datawindow causes a severe memory leak either when you resize the sheet the datawindow is on or when you click on the datawindow. Seems to be worse if the Properties "Data" tab page has Rows:Page set.



CR:156485
CR Number:   156485
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
Passing an incorrect column name to the GetItemString function does not fire the datawindow error event. PB goes directly to the system error event so it is not possible to trap the error and give the user another chance to enter a correct column name.



If you use dot notation and enter an incorrect column name, the datawindow error event does fire, so it is possible to halt error processing and allow user another chance to enter a valid column name.



Customer would like the two methods of accessing the data to handle errors in the same way.



CR:156493
CR Number:   156493
Product Name:   PB Enterprise
Product Component:   Window - Runtime
Status:   Closed
OS:   Solaris 2.5.1
Original Version:   5.0.03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
The ALT+(some shortcut key) combination does not supress normal keyboard behavior in a DDLB and adds the shortcut key character to it, under some circumstances.



PER DEVELOPMENT:

Fixed in 12/16 libuser patch



CR:156495
CR Number:   156495
Product Name:   PB Enterprise
Product Component:   Language - Compiler
Status:   Closed
OS:   MS Windows 3.1
Original Version:   5.0.03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
GPF when saving a window that has script which references a constant variable declared in a uo, within a global variable of that uo class. I.E.:

Create a custom user object uo_globals. Declare and instance constant integer in the user object. Declare a global variable in the application, uo_globals guo_globals. In the script of a window, reference guo_globals.instance_constant_variable. Close the script painter, respond yes to the "save changes?" prompt. Close the window painter. You may gpf here, or you may need to open the window and script painter, make change, and close both (script and window painters) a few times in order to generate the gpf.



CR:156498
CR Number:   156498
Product Name:   PB Enterprise
Product Component:   DB Sybase System
Status:   Closed
OS:   MS Windows 3.1
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
In pb 4.0 the MONEY field in Sybase can be previewed with 4 decimal places, ie .5555. In pb 5.0 the MONEY field in Sybase can be previewed with only 2 decimal places and it rounds the data up, ie. .5555 --> .56. The Sybase MONEY field is intended to round to 2 decimals and have storage for 4 decimals.





PER DEVELOPMENT: Cannot be fixed in 5.0 or 6.0.



WORKAROUND: Use StaticBind=0.



CR:156501
CR Number:   156501
Product Name:   PB Enterprise
Product Component:   Window Painter
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
An editmask window control for a date which uses a spin control will allow an invalid date to pass. If you have a date editmask defined as mm/dd/yy and you use a spin control on the mask, you can type in, for example, 03/31/97 and then, using the mouse, position the cursor over the month and click the spin increment to increment the month the 04. Now the date shown is 04/31/97 and you can tab away from the control with no error.



Workaround would be to add date validation yourself to the modified event of the control.





Per Development:

This is not a bug. A spin control editmask does not have the capability to catch this situation. By comparison, an editmask of mm/dd/yy with 03/31/98 can catch the '04' when typed into the mask because we can guess that you think you intend to input that data. A spin control must allow the '04' because you MIGHT be passing through to '05'. We also have to allow this because you MIGHT spin the 31 to 30. An editmask does not get control when it loses focus so it cannot check the final contents, this must be done in script for an editmask on a window. In a Datawindow however, the DW engine will catch the bad date.



CR:156502
CR Number:   156502
Product Name:   PB Enterprise
Product Component:   Business Graphics
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
A memory leak occurs when using modifydata() function on a graph control



CR:156506
CR Number:   156506
Product Name:   PB Enterprise
Product Component:   OLE - Active X - OCX
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
After smoketesting ActiveX/OCX instantiation for a period of time, painting and other problems occur. Fonts change, icons in the list box disappear, dialog box flashes, insert control tab goes away



CR:156509
CR Number:   156509
Product Name:   PB Enterprise
Product Component:   Window Painter
Status:   Closed
OS:   MS Windows 3.1
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
PB 5.0.0x 16bit ONLY: Has a window with a custom uo on it. If you modify the uo and add a new control such as a cb, save the uo. Open the window with the uo on it and error: "PowerBuilder Application Execution Error (R0023). Application terminated. Error: Cannot assign object of type ... to variable of type ... at line ... in create event of object ..."

Workaround: Regen window before opening. Fixed in 6.0 only.





--------------------------------------华丽的分割线-------------------------------------------------------------------------
之前就已经研发成功了能够从Sybase SQL Anywhere的DB文件中恢复数据的工具:ReadASADB。
此工具支持ASA v5.0,v6.0,v7.0,v8.0,v9.0,v10.0,v11.0,v12.0等版本。
恢复Sybase SQL Anywhere的工具在国内应该算首创。

ReadASADB功能
能够从损坏的SQL Anywhere数据文件(.db)和UltraLite数据文件(.udb)上提取数据的非常规恢复工具

  1. 适用于所有的SQL Anywhere版本    包括:5.x,6.x,7.x,8.x,9.x,10.x,11.x,12.x
  2. 适用于所有的UltraLite版本
  3. 能够恢复出来表结构和数据
  4. 能够恢复自定义数据类型
  5. 能够恢复存储过程等对象的语法
  6. 能够导出到目标数据库
  7. 能够导出到SQL文件并生成导入脚本
  8. 支持多种字符集  包括:cp850、cp936、gb18030、utf8等
  9. 能够恢复未加密或者简单加密类型的数据
  10. 简单易用
  11. 限制:不支持AES加密的数据文件
请参考:研发成功了从Sybase SQL Anywhere的DB文件上恢复数据的工具
            SQL Anywhere数据库非常规恢复工具ReadASADB使用介绍

ReadASADB适用场景

各种误操作:

  1. 误截断表(truncate table)
  2. 误删除表(drop table)
  3. 错误的where条件误删数据
  4. 误删除db或log文件
  5. 误删除表中的字段

本工具的应用场景:

1.因为物理磁盘故障、操作系统、系统软件方面或者掉电等等原因导致的Sybase SQL Anywhere数据库无法打开的情况;
2.误操作,包括truncate table,drop table,不正确的where条件导致的误删除等;
Sybase SQL Anywhere无法打开时,比较常见的错误是:Assertion failed。
如:
1、Internal database error *** ERROR *** Assertion failed:201819 (8.0.1.2600) Checkpoint log: invalid bitmap page -- transaction rolled back
2、Internal database error *** ERROR *** Assertion failed:201819 (8.0.1.2600) Page number on page does not match page requested -- transaction rolled back
3、Internal database error *** ERROR *** Assertion failed:200502 (9.0.2.2451) Checksum failure on page 23 -- transaction rolled back
4、File is shorter than expected
5、Internal database error *** ERROR *** Assertion failed: 201116 Invalid free list index page found while processing checkpoint log -- transaction rolled back
6、*** ERROR *** Assertion failed: 51901 Page for requested record not a table page or record not present on page等等。
+-------------------------------------华丽的分割线-------------------------------------------------------------------------