提供7*24专业Sybase数据库远程及现场技术支持,Sybase ASE及Sybase SQL Anywhere数据库修复服务,
请联系电话: (微信),QQ: 289965371!
We supply technical support for Sybase ASE and Sybase SQL Anywhere, also have many years of experience in recovering data from damanged Sybase devices.
Please contact us:
Phone:
Wechat: 13811580958
QQ: 289965371 联系我们获取数据库技术支持!
Email: 289965371@qq.com
扫描下方微信,联系我们:
扫描雨翰数据恢复官方微信获取专业数据库恢复服务

 

随着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:165137
CR Number:   165137
Product Name:   PB Enterprise
Product Component:   DB ODBC
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.0.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
18 May 1998 Third Party Problem
Description
Customer connects to Informix from PowerBuilder 6.0 using Informix ODBC Driver (version 2.80.0005) iclit09a.dll. When they retrieve an integer or decimal column, second and subsequent rows show zero as the column value.
Workaround Description
 If you set DBParm BLOCK equal to 1, you can turn off extended fetches to get areound this problem. There will however, be a degradation in performance.



CR:165172
CR Number:   165172
Product Name:   PB Enterprise
Product Component:   DPB
Status:   Closed
OS:   AIX 4.1.5
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
Distributed powerbuilder application (client / server) on AIX crashes after performing a connect/disconnect (5 to 10 times).Running the example on NT4.0 platform there is no problem !



CR:165173
CR Number:   165173
Product Name:   PB Enterprise
Product Component:   DPB
Status:   Closed
OS:   AIX 4.1.5
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
Distributed powerbuilder application client win95 or WinNT 4.0 cannot handle a BLOB variable comming from server on AIX correctly.



CR:165177
CR Number:   165177
Product Name:   PB Enterprise
Product Component:   Rich Text
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.0.01
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 Edit control. Input fields that are saved with fixed length and right justification, come up as left justified when called up again.



CR:165255
CR Number:   165255
Product Name:   PB Enterprise
Product Component:   Window - Runtime
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.0.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
New behavior of DDLB userobject. After migration from PB 5 to 6 the ddlb shows a different behavior ie. it ignores a selectitem(index) function call called from a userevent and instead shows the last user input. It is not a migration problem since I could recreate building a new window in PB 6.
Workaround Description
 In the windows timer event use the script from the selectitem event:
integer returnval

returnval = ddlb_test.finditem(tastetryk,0)
//messagebox("",string(returnval))
if returnval <> -1 THEN
ddlb_test.selectitem(returnval)
else
ddlb_test.select



CR:165271
CR Number:   165271
Product Name:   PB Enterprise
Product Component:   Browser
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.0.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11 Dec 2000 Not reproducible with latest version of the product available as of Resolution Date
Description
If an OCX custom control has a property with enumerated tyopes that contain a gap in the list, The PB Object Browser will ignore the gap and 'slide' the rest of the values up to fill the gap. For example, if 7 was not used, the item that should be 8 will show as 7 in the Object Browser.



CR:165276
CR Number:   165276
Product Name:   PB Enterprise
Product Component:   Script Painter
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.0.01 20 Oct 1998 Fixed
Description
32k limit on one line in most script painter areas of the product including "Convert to syntax" screen, file editor, etc. Beyond 32k and you either hang or GPF even in NT 4.0



CR:165378
CR Number:   165378
Product Name:   PB Enterprise
Product Component:   DW - Runtime
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
System11 error in PREPARE statement previewing a nested datawindow with a retrieval argument of datetime in dw painter - not at runtime. Select Error: Arithmetic overflow during implicit conversion of VARCHAR '1-0-1900 0:0:0.000' to DATETIME field.

This error occurs because the Invalid date used for the PREPARE is constructed incorrectly.



CR:165394
CR Number:   165394
Product Name:   PB Enterprise
Product Component:   DB Informix
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.0.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.00 RC 11 Nov 1998 Fixed
Description
When connecting to Informix 7 using the IN7 connection, the following system tables appear in the DB Painter table list, regardless of whether "show system tables" is checked:

informix.sysdistrib
informix.sysfragments
informix.sysmenuitems
informix.sysmenus
informix.systrigbody
informix.systriggers.
Workaround Description
 None.



CR:165410
CR Number:   165410
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.0.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.0.01 07 Jul 1998 Fixed
Description
6.0.01 Regression:
Main DataWindow has a column with Edit Property of DDDW. The DDDW has a retrieval argument. If "Always Show Arrow" is unchecked, a Page Fault will occur: msvcrt.dll@0137:78009dfa
Workaround Description
 On the column with DDDW Edit style, go into properties and check Always Show Arrow.



CR:165476
CR Number:   165476
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   Solaris 2.5.1
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
dwcontrol.ImportFile function fails with return code -7 (Error reading the text), when trying to import dbf file. dbf file is valid.



CR:165586
CR Number:   165586
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.5.00 488 13 Nov 1998 Fixed
Description
6.0.00 Regression. Repaint of detail rows of composite report doesn't work if you're on page 2 and you re-retrieve. Worked OK in 5.0.04.



CR:165589
CR Number:   165589
Product Name:   PB Enterprise
Product Component:   DataBase Administrator
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.0.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10 Dec 1998 Presently Not Targeted For Any Future Release Of This Product
Description
Connected to DB 2 via Net Gatway. A select error in the DB Admin Painter puts up a generc MessageBox with the SQL Statement. If you attempt to build a datawindow with the same SQL statement, the full error from the database is displayed.

Per Development:
Not to be fixed.



CR:165638
CR Number:   165638
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.0.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.5.00 21 Sep 1998 Fixed
Description
GetRowIdFromRow(<rownumber>,<delete! or primary!>) does not work.



CR:165639
CR Number:   165639
Product Name:   PB Enterprise
Product Component:   System Runtime Functions
Status:   Closed
OS:   Solaris 2.5.1
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
APIs FindFirstFileA and FindNextFileA in libkernel40.so doesn't return complete filenames. 2nd, 3rd and 5th character is always missing. Makes it impossible to implement file-listing capabilities in dpb server running on Solaris.



CR:165641
CR Number:   165641
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.0.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
When MDI gateway setting to limit number of rows/bytes is exceeded, PB / Infomaker displays message box with error message Select Error and then displays the data retrieved upto the limit specified in the gateway setting.
Workaround Description
 None.



CR:165652
CR Number:   165652
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)
6.0.01 06 Jul 1998 Fixed
Description
New feature(s) causing severe resource leak in Win95 ONLY. There is a resource leak (GDI and System) in the datawindow painter DESIGN MODE when manipulating objects, ( resizing columns, moving items, etc) and when the dataobject has some button objects (the new controls for the datawindow in 6.0) AND they have "Use Action Default Picture" checked meaning they're using a graphic stock Icon on top of the button.

Second leak. Property sheet of button control in dw. Cycling through "action" dddw to show icons (use default icon for action checked) was leaking slightly due to the painting of the icons (for example for retrieve).



CR:165685
CR Number:   165685
Product Name:   PB Enterprise
Product Component:   Printing
Status:   Closed
OS:   HP-UX 10.20
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.0.01 439 18 Jun 1998 Fixed
Description
PROBLEM: When using print orientation of landscape on HPUX, datawindow will print the first page over and over.



CR:165739
CR Number:   165739
Product Name:   PB Enterprise
Product Component:   DW Painter
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.0.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.00 145 23 Nov 1998 Fixed
Description
Printing perfomance of dw with 3d borders is very slow in PB6 compared to PB5



CR:165760
CR Number:   165760
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.x Catalina 1106 29 Mar 2000 Fixed
Description
Datawindow synchronization between a shared datastore and a standalone datawindow. GPFs trying to SetChanges from the datawindow to shared datastore.

6/8/98 Fbashaw: Verified fixed in build 439



CR:165774
CR Number:   165774
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
28 Apr 1999 Not a Bug
Description
Selected.Mouse (Mouse Selection) for grid and crosstab works in development but not at runtime (you can open the clipboard and see it works in development in preview mode in the datawindow painter but not at runtime when the datawindow is on a window.)

Per Development - no bug -- works as designed. The Copy feature is something the user has to program into the application. In a DW Preview we provide the user with menus and toolbars for things like Retrieve, Update, InsertRows, SaveAs, etc., -- and Edit / Copy of a grid selection (Edit /Copy of the contents of an EditBox is handled by Windows common controls). None of these features are 'automatically' associated with a DW Control dropped on a window -- they have to be programmed by the developer.



CR:165780
CR Number:   165780
Product Name:   PB Enterprise
Product Component:   DW Edit Mask
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.0.04 10 Mar 1999 Fixed
Description
If MS Pen Driver is installed on a Win 95 machine and the application has a datawindow with the combination of a checkbox or radiobutton selected first and another column with an editmask PB 6.0 results in a stack fault and PB 5.0 results in an illegal page fault. If the checkbox or radio button is not selected first, even if positioned first, the problem does not exist.
Workaround Description
 1 - Make sure that the first column selected to be on a datawindow is not a Checkbox if any other columns will have editmasks on them.
2 - Uninstall MS Pen driver.



CR:165791
CR Number:   165791
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   Solaris 2.5.1
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.0.01 20 May 1998 Fixed
Description
Description: On PowerBuilder for Solaris, the RowCount function incorrectly returns a 1 when no rows are present when used with a DataStore for which a data-object has not been assigned.



CR:165816
CR Number:   165816
Product Name:   PB Enterprise
Product Component:   DW Synchronization
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.0.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.00 15 Oct 1998 Fixed
Description
GetFullState() SetFullState() does not copy the filter or delete buffer in PowerBuilder 6.x.
Engineering implemented this feature for PB7.



CR:165823
CR Number:   165823
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.0.01 30 Jun 1998 Fixed
Description
6.0.00 Regression. Database columns placed in header ( in a simple datawindow containing a 1 row result set ) scroll off the screen as the user uses the THUMB on the scrollbar on the right to scroll vertically. All the objects in the header band should stay in place as you scroll.



CR:165824
CR Number:   165824
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.0.01 30 Jun 1998 Fixed
Description
6.0.00 Regression. Scrolling in a group-style datawindow (or datawindow with groups) is missing rows when scrolling in PREVIEW mode (not print preview which seems to be fine). There is a new "virtual scrolling" feature in 6.0.00 which paints the group headers as you scroll and it paints it based on a "page" boundary whether in preview or print preview. In 5.0, the group headers would remain at the "top" until the group break. This regression concerns the fact that when SCROLLING DOWN ONLY, you will often see "gaps" or a missing row or two in PREVIEW mode (everything is OK in print preview mode).


Sometimes, when scrolling down, the GROUP HEADER doesn't paint correctly but scrolling up (with the THUMB) does print correctly



CR:165829
CR Number:   165829
Product Name:   PB Enterprise
Product Component:   DB Painter
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.0.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
When creating stored procedures from Powerbuilder in the DB Administrator for Informix using native driver IN7 PB doesn't send the newline char to the database and the procedure is missing the end-of-line characters (is not formatted) when retrieving the text of the stored procedure.



CR:165844
CR Number:   165844
Product Name:   PB Enterprise
Product Component:   DW Rich Text
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.0.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
29 Jul 1999 Fixed
Description
Rich Text datawindow incorrectly defaults a datatype of type time to a date type
Workaround Description
 choose the properties for the time field when the datawindow is created instead of letting the datawindow default to a date



CR:165845
CR Number:   165845
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.0.01 30 Jun 1998 Fixed
Description
6.0.00 Regression. Vertical scrollbar painted too far left. The rightmost edge of the scrollbar seems about 5 pixels or more too far left. This sounds really minor but it's very distracting if you have a datawindow with columns that go right out to the edge horizontally and you can actually SEE data beyond the vertical scrollbar.



CR:165857
CR Number:   165857
Product Name:   PB Enterprise
Product Component:   Documentation
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10 Aug 2000 Fixed
Description
When scrolling through certain groups, two of the same Group Header with subsets of the group, are displayed on the screen .

****R&D response (March 9/98) -- NO bug; NO regression; NO fix. The scrollbar operation for DataWindows was changed in 6.0. The virtual scrollling enhancement allows any row to be at the top of a screen view (even in a group dw), and print preview scrolling to scroll from the top of the report to the bottom of the report, all in one slide. This means that it is possible to scroll to a point that shows the bottom half of one page and the top half of the next page. This is what's happening in this issue. Even in screen views the data is paginated in a fixed layout. The page size of a screen view is the size of the visual dwControl. The data was arranged into groups and it was determined that a group header was required in the middle of page 6 and repeated at the top of page 7. This layout does not change because of the scrollbar position. If the arrow keys or the page up/down keys are used exclusively, then the issue does not arise. The scrollbar enhancement was added to override the navigation keys.



CR:165880
CR Number:   165880
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   HP-UX 10.20
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
23 Sep 1998 Fixed
Description
Description: When migrating a PBL that has the DW print orientation set to Landscape
from NT to HPUX, previewing the DW on HPUX causes PB to hang.
Workaround Description
 set orientation to Default, then migrate, then change back.



CR:165883
CR Number:   165883
Product Name:   PB Enterprise
Product Component:   Printing
Status:   Closed
OS:   HP-UX 10.20
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.0.01 30 Jun 1998 Fixed
Description
PROBLEM: PB does not read the options from the windu file. Even if you go in and select the printer name, resolution, page size and paper tray and hit ok and save. PB does not save the options.



CR:165884
CR Number:   165884
Product Name:   PB Enterprise
Product Component:   Printing
Status:   Closed
OS:   HP-UX 10.20
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16 Jun 1998 Fixed
Description
Description : Under printer setup/options, there is a ddlb for paper size and paper source. Customer wants the ability to select these options from the print specification screen. On windows that functionality is available.



CR:165929
CR Number:   165929
Product Name:   PB Enterprise
Product Component:   DW SaveAs
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.00 RC0 4016 13 Jan 1999 Fixed
Description
SaveAsAscii() bugs. It puts an extra comma at next line . The headers are wrong. Multi-line headers cause a cr/lf, leading to incorrect headers. I would suggest that multi-line headers (that have ~r~n / ctrl-enter characters) not be put on multiple lines, but on one line, effectively replacing the ctrl-enter with a space.



CR:165931
CR Number:   165931
Product Name:   PB Enterprise
Product Component:   Function Painter
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.0.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
When creating either a global or object level function "olecustomcontrol" is not in the dropdownlistbox although it works when typed in manually. Although the documentation states that you can specify any datatype a customer could assume that they are all listed. This seems to be the only graphicobject => window object => dragobject => that is not listed in the dropdownlistbox. It's ancestor omcontrol is not listed but the other descendant olecontrol is listed as a selection. Typing it in works, but the simple addition of this in the dropdownlistbox would make application development easier for the customer.
Workaround Description
 When creating either a Global or object level function manually type in "olecustomcontrol" in the dropdownlistbox.



CR:165945
CR Number:   165945
Product Name:   PB Enterprise
Product Component:   DW Painter
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.0.01 30 Jun 1998 Fixed
Description
6.0.00 Regression. Null datavalue in dddw column causes GPF when tabbing off
Null datavalue in dddw column causes GPF when tabbing off. Sometimes in MSVCRT.DLL, sometimes in PBDWE60.DLL.



CR:165963
CR Number:   165963
Product Name:   PB Enterprise
Product Component:   UO - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.0.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
Parentwindow property of a menu object returns incorrect information when this property is used in conjunction with a NVO, the name of the NVO is returned instead of the parentwindow.

PB Version and Build: 5.0.04.76 ----> Fail
5.0.05.10 ----> Fail
6.0.01.419 --> Fail
7.0.81 ---------> Fail

The menu option contains the following script:

window lw_test
lw_test = parentwindow
messagebox("OPEN MENU OPTION",classname(lw_test))

The PowerBuilder online help for menu object properties states the following:

ParentWindow - Specifies the window that owns the Menu object.

Using PowerBuilder 5.0.04.76 and 5.0.05.10, when the parentwindow property is called from a command button on a visual user object using the following script:

m_menu lm_pop
lm_pop = create m_menu
lm_pop.m_file.popmenu(200,100)

The name of the "command button" is returned instead of the name of the window.

In PowerBuilder 6.0 and 6.0.01.419 the name of the window is returned correctly.

When a NON VISUAL userobject is used with the above script, all versions of PowerBuilder (5.x, 6.x, 7.x) return the name of the non visual userobject instead of the name of the window.

The following are related cases:

CR 162471 ---> Ptrack 50145 ---> Bug number 49657.

Ptrack 272083



CR:165964
CR Number:   165964
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.0.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
28 Aug 1998 Duplicate
Description
When building a Crosstab datawindow, doing a preview/or running gives a crash in pb6. In PB 5 it was working ok.



CR:165965
CR Number:   165965
Product Name:   PB Enterprise
Product Component:   DB Painter
Status:   Closed
OS:   AIX 4.1.5
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
PB6 on AIX: Coredump when trying to establish connection via File->Connect, whereas File->ConnectPromt works. AIX 4.2.1



CR:165982
CR Number:   165982
Product Name:   PB Enterprise
Product Component:   DB MS SQLServer
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.0.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
The return value of an RPC is inconsistent with MSS driver



CR:166019
CR Number:   166019
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.0.01 01 Jul 1998 Fixed
Description
6.0.01 Beta Regression. Crash in PBDWE60.DLL or MSVCRT.DLL (Win95) when doing a bad Setitem() value to a dddw. This is the case where the value doesn' t have a matching display value.
The bug is that if you setitem on a drop down data window with a value that is not in the table of that pulldown. This can happen when lookup values (for the setitem) come from tables that don't match the ones being referenced by the dddw.

Win95 hangs and gpfs for customer in PBDWE60.DLL at 0257:105e01fd.
NT 4.0 GPFs in pb60.exe 0xc000005, address 0x78008dfa

This worked in 5.0.04 and 6.0.00.



CR:166025
CR Number:   166025
Product Name:   PB Enterprise
Product Component:   WT - Web DataWindow DTC
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   1.5
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
PowerSite object model does not include a method or property to control timeout on sessions.
Workaround Description
 LiveWire ( default:10 minutes for client object stored on the server) configurable via client.expiration(#)
ASP (default: 20 minutes) configurable via Session.Timeout
PowerDynamo (default: 5 minutes) configurable via session.timeout property



CR:166053
CR Number:   166053
Product Name:   PB Enterprise
Product Component:   DB ODBC
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.0.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10 Dec 1998 Not reproducible with latest version of the product available as of Resolution Date
Description
A datawindow that contains a drop down datawindow and a long varchar column causes a gpf in MSVCRT.DLL at 0157:78008dfa on the retrieve if the data in the source table does not match the values in the DDDW.



CR:166061
CR Number:   166061
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Open
OS:   MS Windows 3.1
Original Version:   4.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
ISUG Enhancement Request e15_045:



The Datawindow Engine/Painter needs to be rewritten in order to allow text and large character columns to be displayed accurately when it does not fit a on a physical page. There is 'a longstanding DW requirement that rows fit on a page.
Review Status
 Reviewed by PB Engineering - ISUG Rating:

"U" Under consideration.



CR:166063
CR Number:   166063
Product Name:   PB Enterprise
Product Component:   Documentation
Status:   Closed
OS:   MS Windows 3.1
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
03 Jun 1998 Duplicate
Description
Documentation Bug - PFC Reference Guide - Page 188.

Function of_GetDetail()

Description ==>> Creates an array containing references to all details for the current DataWindow.
Access ==>> Public
Syntax ==>> dwcontrol.instancename.of_GetDetails ( details[ ] )
Description ==>> Creates an array containing references of all details for the current datawindow.
Usage ==>> Call this function from any DataWindow in the linkage chain to access its detail DataWindows.

Problem:
=======
Documentation needs to include a description, and/or a warning, when using the of_GetDetail() function along with the of_Unlink() function. There was an enhancement request to enhance the functionality of the of_Unlink() function to address this issue.

A small note should perhaps be added to mention something like the following:

''When using the of_Unlink() function along with this function, be sure to check all the elements in the Linkage chain are actually referencing a u_dw object as you loop through the linkage chain. Keep in mind that the of_Unlink() function does NOT remove elements from the PFC Linkage chain. It only re-references the the element to an ramdom section in memory.''

Excerpt from enhancement request:
''Currently PFC Unlinks a datawindow from the linkage chain by creating a local variable of type u_dw and assigning it to the element in the array that references the datawindow control the user wants to unlink. This is done by calling the of_unlink() PFC function. The of_unlink() function then calls the of_unlikdetail() function which performs the re-assignment.''

Note: How PFC development will deal with issue is directly revelant to the outcome of this one.
RKN: I will work this out with PFC development.



CR:166067
CR Number:   166067
Product Name:   PB Enterprise
Product Component:   DB ODBC
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.0.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.00 201 07 Oct 1998 Not reproducible with latest version of the product available as of Resolution Date
Description
When using a datetime datawindow retrieval argument, you sometimes get an error when going from the SQL graphics painter to the DW painter. The error is caused by a SQL statement created by PowerBuilder that contains a datetime value in a string format that is incorrect. The problem is that there is a negaive number in the milliseconds portion of the date.



CR:166068
CR Number:   166068
Product Name:   PB Enterprise
Product Component:   DW Edit Mask
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.0.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
This only happens in Windows NT 4.0. Win95 works correctly . This was originally submitted as a PB 6.0.01 regression but when tested here thie same behavior was seen in all versions tested back to PB 5.0.

If a datawindow has a long char column (255 char) that has Auto Vertical Scroll and Autosize Height selected when a new row is inserted and a user is inputting data there are differences in behavior from NT 4.0 and WIN 95. In NT 4.0 if the space bar is pressed multiple times at the end of the visible input line to try to take the user to the next line the cursor does not move until a valid character is entered. The extra spaces however are retained in the row and in the database. In Win95 the appropriate number of spaces hit to take the user to the end of the visible input line takes the user to the next line and no additional spaces are retained to the database.
Workaround Description
 Be aware not to input extra spaces in the visible input line of a long char column with Auto Vertical Scroll with Autosize height selected.



CR:166069
CR Number:   166069
Product Name:   PB Enterprise
Product Component:   DW - Runtime
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
Allow the modification of the "datawindow.printer" attribute with Modify() and dot notation. This would allow background print processing used by many servers to switch printers - using dw_1.print() automatically with script.



CR:166070
CR Number:   166070
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.0.01 16 Jun 1998 Fixed
Description
6.0.01 beta Regression. A char(2000) datawindow column with a dddw edit style causes a GPF during retrieval.



CR:166106
CR Number:   166106
Product Name:   PB Enterprise
Product Component:   Machine Code Exe Creation
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.0.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.0.01 09 Oct 2004 Not reproducible with latest version of the product available as of Resolution Date
Description
In later builds of PowerBuilder 6.0.01, If your script contains certain international characters then you will get the following access violation 0xc0000005 0x00333437

I have managed to reproduce the access violation with the following international characters:

I have performed the following tests with all builds of PowerBuilder 6.0.01:

6.0.251 GA - Will allow me to create a 32 bit machine code executable.

The following characters are displayed in message boxes with my test application:

- - Correct
- - Correct
- o - Incorrect
- - Correct
- o - Incorrect

If I create a 32 bit p-code executable, all the characters are displayed fine.

6.0.01.360 - Will allow me to create a 32 bit machine code executable.

The following characters are displayed in message boxes with my test application:

- o - Incorrect
- o - Incorrect
- o - Incorrect
- o - Incorrect
- o - Incorrect

If I create a 32 bit p-code executable, all the characters are displayed fine.

6.0.01.365 - Will NOT allow me to create a 32 bit machine code executable.

I get the following link error: Codegen compilation error, see file 'D:\TEMP\test2.log'.

Test2.log contains the following information:

CGEN: Compiling 'D:\TEMP\test2.c'
D:\TEMP\test2.c(13) declaration specifiers are required to declare 'INT'
D:\TEMP\test2.c(12) syntax error before 'WINAPI'; probable cause: incorrectly spelled type name
D:\TEMP\test2.c(45) syntax error before 'INT'; probable cause: incorrectly spelled type name
D:\TEMP\test2.c(493) syntax error; probable cause: missing ';'
D:\TEMP\test2.c(498) syntax error; probable cause: missing ';'
D:\TEMP\test2.c(500) syntax error before 'VOID'; probable cause: incorrectly spelled type name
D:\TEMP\test2.c(537) syntax error before 'INT'; probable cause: incorrectly spelled type name
D:\TEMP\test2.c(2134) symbol 'VTAB_CLASS_INFO' already defined
D:\TEMP\test2.c(2134) 'int VTAB_CLASS_INFO' defined in: D:\TEMP\test2.c(493) (col 8)
D:\TEMP\test2.c(2134) syntax error; probable cause: missing ';'
D:\TEMP\test2.c(2144) symbol 'VTAB_GROUP_INFO' already defined
D:\TEMP\test2.c(2144) 'int VTAB_GROUP_INFO' defined in: D:\TEMP\test2.c(498) (col 8)
D:\TEMP\test2.c(2144) syntax error; probable cause: missing ';'
D:\TEMP\test2.c(2146) syntax error before 'VOID'; probable cause: incorrectly spelled type name
D:\TEMP\test2.c(2170) no reference to symbol 'VTAB_CLASS_INFO'
D:\TEMP\test2.c(2170) 'int VTAB_CLASS_INFO' defined in: D:\TEMP\test2.c(493) (col 8)
D:\TEMP\test2.c(2170) no reference to symbol 'VTAB_GROUP_INFO'
D:\TEMP\test2.c(2170) 'int VTAB_GROUP_INFO' defined in: D:\TEMP\test2.c(498) (col 8)

If I create a 32 bit p-code executable, all the characters are displayed fine.

I get the same results as 6.0.01.365 after testing with 6.0.01.370, 6.0.01.375

With 6.0.01.381 I get the following access violation when trying to compile a machine code executable 0xc0000005 0x00333437

I also get the same access violation while testing with the following builds of PowerBuilder 6.0.01: 6.0.01.385, 6.0.01.390, 6.0.01.399, 6.0.01.404, 6.0.01.409, 6.0.01.414, 6.0.01.419. 6.0.01.424, 6.0.01.444

If I create a 32 bit p-code executable with the above builds, all the characters are displayed fine.
Workaround Description
 The workaround is to create a machine code executable.

In 6.5 can compile on Win95 instead



CR:166109
CR Number:   166109
Product Name:   PB Enterprise
Product Component:   Pipeline - Runtime
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
New Feature Request: The Pipeline object error messages should be more comprehensive eg. insert new error message numbers, according to the actual error happening.



CR:166129
CR Number:   166129
Product Name:   PB Enterprise
Product Component:   Documentation
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.00 22 Jun 1999 Fixed
Description
The PowerBuilder PFC documentation for the u_calendar service should be changed to reflect the restriction that, if used with a datawindow column, the date formats must be compatible with the client default system date. That is, you cannot override the format with an editmask on the dw column.



CR:166206
CR Number:   166206
Product Name:   PB Enterprise
Product Component:   Menus - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.0.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.0.01 10 Jun 1998 Fixed
Description
6.0.00 Regression. Setting menu visible attribute causessheets not to open.
Setting multiple menu item visible attributes in the Open event of a window causes the opens to fail if you open and close about 40 sheets. The window is inherited and there is similar code in the ancestor to turn off/on about 15 menu items and the descendant window open event script also has another 15 or so. Seems to be NT 4.0 only. SDI type application.



CR:166217
CR Number:   166217
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)
8.0.4 06 Apr 2004 Fixed
Description
Checkboxes and radio buttons appear incorrectly when on a datawindow and called from a Visual C++ program through OLE automation. The datawindow will appear fine in any other environment (dev or runtime).



CR:166233
CR Number:   166233
Product Name:   PB Enterprise
Product Component:   DB Sybase System
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.5.00 465? 02 Feb 1999 Fixed
Description
If you have PWDIALOG in the application dbparm. If your Sybase password has expired, the executable is not displaying the change password dialog. This works in PB 5.0.0x in development. pcode and compiled code. In 6.x it works in development but not in pcode or compiled code.
Workaround Description
 The only workaround that you could implement is to actually call sp_password from your application if you get a specific error code returned from the db, otherwise, manually change the password from ISQL



CR:166239
CR Number:   166239
Product Name:   PB Enterprise
Product Component:   Machine Code Exe Creation
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.0.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
Please ignore, logged by mistake.



CR:166240
CR Number:   166240
Product Name:   PB Enterprise
Product Component:   Window - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16 Dec 1998 Presently Not Targeted For Any Future Release Of This Product
Description
Word 6.0,7.0 remembers the state of the previous sheet open. If you have some document sheets open and maximize the 'active' sheet (using the maximize icon on the titlebar), you will see that the text time you do a File/New, the next "document" will also open maximized into the frame. Powerbuilder 4.0-6.0 has a different behavior. In this same scenario with some sheets open and the active sheet being "maximized", and if no default {arrangeopen} style is used in the Opensheet() call, it ALWAYS opens the next sheet in such a way as to re-arrange ALL the sheets to "cascaded!" rather than opening the new sheet as maximized (like the previously open sheet).



CR:166243
CR Number:   166243
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.0.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.0.01 09 Jun 1998 Fixed
Description
In PB 5.0.04 and PB 6.0.01 if a numeric column has an editmask (###,##0.#### for example) or (###,###.00) on it and the user highlights the field and hits the delete key, initially the value changes to '0' exactly as it should. However when the user tabs off of the field the original value is re-entered into the field. If a '0' is entered or any other valid entry then there appears to be no problem.

In PB 6.0 GA (build 251 tested) there was a different problem, that has been fixed in PB 6.0.01, that masked this problem where if you highlighted the field and hit the delete key a huge negative number appeared in the field.

Without the editmask it triggers the editchanged event when the delete key is hit and the itemerror event when tabbed off but with the editmask on neither the editchanged or the itemchanged events get fired. If valid data is input, even a "0" then both the editchanged and the itemchanged events get fired.

Workaround: Map a user event on the datawindow called ue_key to the system event pbm_dwnkey. Code the following:


long ll_null, ll_row
int li_column
string mod_string, ls_coltype


if key = keydelete! then


// did you select ALL text for delete? Bug 166243

if len(selectedtext()) > len(gettext()) then


// what type of column am I on? Make sure you're on a column

if not isnull(getcolumn()) then

// get the row and column numbers
li_column = getcolumn()
ll_row = getrow()


mod_string = "#"+string(li_column)+".coltype"
// get the column type "deci, numb, long, ulong
ls_coltype = describe(mod_string)
// Error checking.
if mod_string <> "!" then

// get value ready
setnull(ll_null)

// find out if it's numeric
choose case left(ls_coltype,4)
case 'deci','numb','real','long','ulon'
setitem(ll_row,li_column,ll_null)
end choose

end if /* mod string check*/

end if /* getcolumn not null */

end if /* Selected full text in editmask */

end if /* Pressed DELETE key */
Workaround Description
 After highlighting the entry hit '0' rather than hitting the delete key. This is really not an acceptable workaround as people doing data entry may not even realize that the original value has been reentered after tabbing off of the field.



CR:166252
CR Number:   166252
Product Name:   PB Enterprise
Product Component:   DW Display
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.0.01 435 28 Sep 1998 Not reproducible with latest version of the product available as of Resolution Date
Description
NT 4.0 only. Database column data in header band missing. Output truncation in header band under groupboxes. Missing column output in header band when printed. Works fine in print.preview. 5.0.04, 6.0.00 and 6.0.01 build 424 seem to have the problem..

Win95 does not have this problem. LaserJet 4 driver.



CR:166256
CR Number:   166256
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.0.01 436 06 Jul 1998 Fixed
Description
The new Virtual scrolling feature in 6.0.00 seems to have introduced some problems with the thumb scrollbar - even in development. If you have a semi-complex datawindow into print preview and then re-retrieve(). After the second retrieve is finished, if you then pick up the thumb on the vertical scrollbar and move down slowly to about 3/4's of the full scrollbar, it will GPF.



CR:166263
CR Number:   166263
Product Name:   PB Enterprise
Product Component:   DW Printing
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
28 Sep 1998 Third Party Problem
Description
On a nested report set border to "BOX", during preview and printout, the printout is missing the left and top parts of the box and the right and bottom parts that do print are printing with a pen that is 1/2 the size it should.



CR:166287
CR Number:   166287
Product Name:   PB Enterprise
Product Component:   Window - Runtime
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.0.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
07 Dec 1998 Fixed
Description
Calling the functions ole_1.Move() and ole_1.Resize() together from the same event cause an ole control to move briefly to its original position (as defined in window painter) before moving it to the position specified by the Move function.

Only with ole controls and standard visual uo of type olecontrol
Only reproduced with an OLE custom control (OK with 'Create New' or 'Create from file')
Any ole custom control will show this, example is with Visual Components Formula 1
Not reproduced with other PB controls
Workaround Description
 Directly change ole control's x, y, width, height properties
Use standard uo type olecontrol, overload 2 functions with...
integer Move (integer x, integer y) and integer Resize (integer w, integer h)



CR:166289
CR Number:   166289
Product Name:   PB Enterprise
Product Component:   OLE - Active X - OCX
Status:   Closed
OS:   Microsoft Windows 98
Original Version:   6.0.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
ole_x.resize(x,y) returns the x and y co-ordinates to the original values even if the object has been moved
using the move function. Only occurs with ocx/ole controls



CR:166312
CR Number:   166312
Product Name:   PB Enterprise
Product Component:   DB Sybase System
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.00 3235 29 Dec 1998 Fixed
Description
SYC/SYB drivers don't have FormatargsasExp DBPARM implemented in 6.0.00
Open/Client SYC, problems with dw retrieval argument of type number with 16 digits. Dw_object seems to never work with 16 digits of precision and ending in 001...



CR:166367
CR Number:   166367
Product Name:   PB Enterprise
Product Component:   Plug-ins
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.0.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.00 211 31 Oct 2002 Fixed
Description
Using the secure window plugin nppbs60.dll.
Non secure code in control constructor and/or window open events does not give the expected runtime error when using the secure window plugin. It is possible to read and write to disk, delete files, call external functions etc which are all illegal actions with the secure window plugin

The same code in other events (such as a user event posted from open/constructor events) gives the correct runtime error - R1071 - and exits the window

Tested with Netscape 3.0 to 4.0.04 and MSIE 3.0 to 4.0 on NT 4.0 and Win95

There is no acceptable workaround. Could post a user event from constructor/open events but this will not make the client machines secure from other web apps which have been developed without using this alternative.



CR:166380
CR Number:   166380
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
07 Jan 1999 Presently Not Targeted For Any Future Release Of This Product
Description
16 bit under 32 bit OS GPF using "cancel" during retrieve of datawindow.



CR:166448
CR Number:   166448
Product Name:   PB Enterprise
Product Component:   Source Control
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   2.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
If ObjectCycle is used with Visual J++'s Microsoft Common Source Code Control (MCSCC), and if there is more than a single user using source control, then you will experience problems with checkin/checkout status.

Problem 2: If user1 checks an object out into ObjectCycle, user2 should NOT be allowed to alter the checked out object, but currently user2 has the ability to do this.



CR:166457
CR Number:   166457
Product Name:   PB Enterprise
Product Component:   Migration
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.0.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
The PostQuitMessage API used in conjunction with other Windows API calls does not give the same results in PB 5.0 and PB 6.0.
The customer is using PostQuitMessage to determine the ending status of his application from another (nightly batch jobs). However, the message that he posts gets altered by PB when retrieved using the GetExitCodeProcess API from the application that processes the batch jobs.

There is definitely a change in behavior from PB 5.0 to PB 6.0. It appears as though PB 6.0 is interfering with the windows messaging or this could also be simply unsupported behavior.



CR:166458
CR Number:   166458
Product Name:   PB Enterprise
Product Component:   DB ODBC
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.0.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.0.01 15 Dec 1998 Fixed
Description
ODBC - After calling a stored procedure on a transaction object which holds an open cursor - Error -1 Cursor is not open ocurrs
Workaround Description
 use two different transaction objects



CR:166482
CR Number:   166482
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.0.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.5.1 27 Jun 2000 Fixed
Description
PB 6.0.01
If you have a datastore that is using sharedata, have only one row, assign the values to that row with dot notation and click on the first column of the dw that value will seem to disappear until you click on a different column. At this point if you click again on the first column it does not disappear. This also happen with the above scenario if in the script you use a setfocus() to the datawindow. When you click on a column other than the first, the data in the first reappears also. If there is more than one row in the datawindow then it also doesn't occur,
Workaround Description
 Simply use setitem rather than dot notation if there is only going to be one row.



CR:166524
CR Number:   166524
Product Name:   PB Enterprise
Product Component:   Pipeline Painter
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.0.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
20 Oct 1998 Fixed
Description
6.0.01 Regression: Accessing pipeline objects when the user is not the owner of the tables results in an error: "The table <tablename> not found"



CR:166525
CR Number:   166525
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
18 Apr 1999 Not a Bug
Description
Running a simple 1 row freeform datawindow with a or multiple long text (with autosizeheight ON and autoverticalscroll ON and autohorizontalscroll OFF) columns above other nested reports causes some reports to slide up and overlap even though the data is less than half of one page for the entire row. Even playing with zoom factors doesn't seem to help.

There is a mixture of long text columns and nested reports in a freeform style but the entirety does not flow beyond a page.

What is happening is the long text columns are print previewing to a larger font and this makes it appear to overlap the nested reports below it (even if the autosize is set properly everywhere).

Per Development:
Not a bug -- This is the long standing overlap bug due to conversion from print to screen resolution.
This is another example of PrintPreview facsimiles not being able to reproduce an exact image of the printed page because of the integer-math of screen resolutions. This report has a bad layout design of a mixture of AutoSizeHeight text columns, and AutoSizeHeight nests. On the printer, the data is presented in the proper position. On the screen the initial large text columns on the detail band expand to twice their print size, because of the lower resolution -- and therefore higher font height -- of the screen. The text expands to appear under the subsequent nests. This is a long-standing side-effect of PrintPreviews of large text columns. If the PrintPreview is to be used to view the report, then the design should be changed to put each of the large text columns in its own nest. The last lines of the nests will probably get clipped -- due to accumulated line height differences -- but at least the blocks of text will not be overlapped. Also, once you start placing nested reports in a detail band, the remainder of the detail band should all be nests -- that is, do not add more columns or text fields after the nests, because of nest pagination rules.



CR:166576
CR Number:   166576
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)
7.0.00 Beta 3 3234 16 Nov 1998 Fixed
Description
When the library search path is not correctly specified (ie. the pfc libraries are left out of the search path of the application object) regenerating an object inherited from one of the PFC classes leads to a PB crash or hanging.



CR:166581
CR Number:   166581
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)
7.0.00 05 Dec 2000 Fixed
Description
Changing the property "DataWindow.Table.Data.Storage" to "Disk", has no effect ( when checking the property value at run-time it returns "memory".



CR:166587
CR Number:   166587
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.0.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
A modified column cann't be edit anymore in datawindow query mode after you set override_edit to yes.
example:
dw_1.Object.Datawindow.QueryClear = 'Yes'
dw_1.Object.DataWindow.QueryMode = 'yes'
dw_1.Object.Emp_id.criteria.override_edit = 'yes'
dw_1.Object.Emp_id.Background.Color='255'
Workaround Description
 dw_1.dataobject = "d"
dw_1.settransobject(sqlca)
dw_1.Object.Emp_id.Background.Color='255'
dw_1.Object.Datawindow.QueryClear = 'Yes'
dw_1.Object.DataWindow.QueryMode = 'yes'
dw_1.Object.Emp_id.criteria.override_edit = 'yes'



CR:166590
CR Number:   166590
Product Name:   PB Enterprise
Product Component:   Menu Painter
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
14 Sep 1998 Not a Bug
Description
Customer would like to log a CR: If a ToolBarButton is disabled, then the Tooltip should not get displayed.



CR:166625
CR Number:   166625
Product Name:   PB Enterprise
Product Component:   UO - Runtime
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.0.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.0.01 30 Jun 1998 Duplicate
Description
The customer reported that in his code he is calling a function on the window, passing it a custom nonvisual object (by reference) that has never been created. In the window function, he is assigning the nonvisual object parameter to an instance variable of the same type.

In all versions of PB 5.0 and PB 6.0 prior to build 424 his script works fine. Starting in build 424, and also failing in build 429,
this same script gives an illegal page fault in PBVM60.dll. In build 424 the address is 0137:11218af5 and with build 429 the address is 0137:11218b05 on my machine.

This has been simplified by removing the function and simply assigning the instance NVO to the local NVO that has not yet been created in the script on the button. The same illegal page fault is generated.

Duplicate of bug 166615
Workaround Description
 Be sure to either create the NVO or use autoinstantiate prior to referencing a local NVO.



CR:166627
CR Number:   166627
Product Name:   PB Enterprise
Product Component:   Generators
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.0.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
Java Proxy generated for a NVO that uses bounded array by reference arguments can't be compiled. It results in compilation errors. The current workaround is to avoid using bounded array by reference arguments or to mark methods that have such arguments as "private".



CR:166648
CR Number:   166648
Product Name:   PB Enterprise
Product Component:   Rich Text
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.0.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.5.00 1112 13 Jul 2000 Fixed
Description
GPF/Dr. Watson when switching OS language (WIN95, NT) in a RTE Control with the shortcut Ctrl+Shift



CR:166667
CR Number:   166667
Product Name:   PB Enterprise
Product Component:   OLE - Active X - OCX
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.0.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
26 Jun 1998 Fixed
6.0.01 07 Jul 1998 Fixed
Description
PB 6.0.01 Regression - Customer is reporting a difference in behavior between PB 5.0.04 and PB 6.0.01. Customer is using VCI Formula One Workbook but I tried a different control and it behaved the same way. An ole user object is not being resized correctly when placed on a sheet whose resize event has the following script - ole_1.resize(this.workspacewidth(),this.workspaceheight()). PB 5 and PB 6.0 GA (build 251) work correctly - when the sheet is opened in the frame window, the ole user object is resized appropriately but in PB 6.0.01 (all builds from 360-424 that were tested exhibited behavior) it does not resize until you manually resize the sheet , or click on the sheet, after opening it.



CR:166676
CR Number:   166676
Product Name:   PB Enterprise
Product Component:   DW Synchronization
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.5.00 31 Oct 2002 Fixed
Description
In Distributed PB, using Syncronize Functions: Deleting Subsequential times causes Update() error: -1 with message: Row changed between retrieve and update



CR:166680
CR Number:   166680
Product Name:   PB Enterprise
Product Component:   DPB
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
In Distributed PB, when client calls setchanges returns -1 in state of resetting the flags.



CR:166691
CR Number:   166691
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.0.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.0.01 08 Jun 1998 Not reproducible with latest version of the product available as of Resolution Date
Description
6.0.01 regression, SetChanges returns a -2 trying to apply changes to a server datastore.

6/8/98 fbashaw: Verified it works correctly in build 439.



CR:166694
CR Number:   166694
Product Name:   PB Enterprise
Product Component:   DW Painter
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.0.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.5.00 31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
6.0 build 419. Numeric editmask in datawindow using German or French settings and [currency(7)], or '###,###.00' editmask, [General] exhibits the following behavior if the datawindow column datatype is ''number": Type in 12.34, tab out - you get 12,34 - fine. Now click on that field again - it displays 12,00. If you tab out, or click elsewhere, it reverts back to 12,34. This only happens when you select, or tab into, the field again.

Similar to cr163009.



CR:166732
CR Number:   166732
Product Name:   PB Enterprise
Product Component:   Font
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
Feature request:
Currently the font for the RTE control can only be of type truetype. It is not possible to reformat the text of an RTE control by setting the font manually tofixed sizedd fonts like FixedSys or MS Sans Serif.



CR:166736
CR Number:   166736
Product Name:   PB Enterprise
Product Component:   DB Oracle
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.0.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.5.00 466 22 Oct 1998 Fixed
Description
Oracle 8 - PB6 update with binding doesn't work against column of type CHAR - reproduced with build PB 6.0.01.424.
Error: Row changed between retrieve and update.
No changes made to database.
Workaround Description
 1.) DisableBind=1

2.) use VARCHAR2 instead of CHAR in the column definition



CR:166737
CR Number:   166737
Product Name:   PB Enterprise
Product Component:   DB ODBC
Status:   Closed
OS:   MS Windows NT 4.0
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
DB2 ODBC Cst uses stored procedure. The parameters in/out are truncated to 254 characters. with SQLLINK ODBC Driver for DB2



CR:166738
CR Number:   166738
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.0.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12 Jun 1998 Not reproducible with latest version of the product available as of Resolution Date
Description
Whn you perform an update from a PFC application, the update causes a page fault in kernel.dll or pbvm60.dll.



CR:166741
CR Number:   166741
Product Name:   PB Enterprise
Product Component:   DB Oracle
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.0.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.5.00 495 10 Nov 1998 Fixed
Description
Oracle 8 - PB6 retrieval argument with binding doesn't work for column of type CHAR

with 6.0 DataWindow Error
Select Error: ORA-01460: unimplemented or unreasonable conversion requested
with 6.0.01 the error message doesn't show, but the data is not retrieved



CR:166747
CR Number:   166747
Product Name:   PB Enterprise
Product Component:   DW Expression
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
Median values for Group values in Datawindows are sometimes calculated incorrectly.



CR:166760
CR Number:   166760
Product Name:   PB Enterprise
Product Component:   DW Display
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.0.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
21 Jun 1999 Duplicate
Description
The problem that the customer is experiencing is that they have a text field that can be up to 255 characters in length and cannot predict what the longest sub-string or word will be. The column on the datawindow is narrow enough that at times part of the text is getting truncated when printed and there is no way for the customer to know this. When the length of an individual word is longer than the width of the column the extra characters are truncated and not in the printed report. The customer believes that PB should wordwrap at this point.

There are also differences seen with the sample when the column has focus and whether or not it has autosize on or not. From speaking with GerryR. this is most likely just behavior and not a bug.
Workaround Description
 Make sure that the width of the column is at least as wide as the longest substring in large text fields.



CR:166799
CR Number:   166799
Product Name:   PB Enterprise
Product Component:   DB Oracle
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.0.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.5.00 497 11 Nov 1998 Fixed
Description
Oracle 7.3 / 8 DBPainter - in Foreign Key Definition Dialog Box the Primary Key columns don't appear



CR:166817
CR Number:   166817
Product Name:   PB Enterprise
Product Component:   Language - Runtime
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
Closing the window from the key even will cause an application error under NT and Win95. Only occurs if there is a datawindow control with a datawindow object on the window. If the dw control does not have a datawindow object, the error does not occur.

Works properly under PB 5.0x
Workaround Description
 POST the function to close the window in the Key Event:

if key=keyescape! then
POST close(this)
end if



CR:166826
CR Number:   166826
Product Name:   PB Enterprise
Product Component:   DPB
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.0.01 437 31 Oct 2002 Fixed
Description
Problem dealing with shared objects and corruption of heap space on a multi-processor machine.



CR:166871
CR Number:   166871
Product Name:   PB Enterprise
Product Component:   DW Display
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.5.00 17 Nov 1998 Not a Bug
Description
5.0.04/6.0.00 Regression. With 2 report objects on a composite report -- the first being a standard header, the second being the actual report. They are "stacked". In the second report, the user specifies "new page on group break" on the group attribute. The footer is trailed on both report objects within the composite report. 5.0.04/6.0.00 is now putting one blank page at the beginning of the report just after the header nested report. (can be seen in print preview) before showing the first group.

August 3, 1998 - Product Support Engineering
Workaround found: Use another level of composite (put the composite in a composite) and the group report will start after the top header report without going on to the next page.



CR:166875
CR Number:   166875
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.00 Beta 3 15 Dec 1998 Not reproducible with latest version of the product available as of Resolution Date
Description
If all columns in the datawindows are defined with the Protect attribute set to 1, the SetRow() function returns -1 and the row in focus does not change. This is contrary to the fact that users can change the row using the mouse, or programatically if we set the TabSequence attribute to 0 instead of using the Protect attribute.

Tab Order Protect Rowfocuschanged via Setrow()
--------------- ----------- -----------------------------------------------
1. <all zero> <all protected> Fires <<- huh? Why fire it in this case but not case 2?
2. <10,20,etc> <all protected> Does not fire (setrow(), getrow() fail) <<- This is the complaint
3. <all zero> <none protected> Fires
4. <10,20,etc> <none protected> Fires



CR:166920
CR Number:   166920
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.0.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.0.01 06 Jul 1998 Fixed
Description
6.0.01 beta Regression.Keypad '.' ignored when using comma decimal separator. This happens with an edit style "edit" in a numeric or decimal{2} datawindow column as an example. This does not happen when there is an editmask on the column. Note this worked fine in 5.0.04 and 6.0.00.



CR:166922
CR Number:   166922
Product Name:   PB Enterprise
Product Component:   DW Painter
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.5.00 145 06 Dec 2000 Fixed
Description
Datawindow pagination gives 1 of 14000 for even 1 row datawindow if there is the following conditions:
1. There is a datawindow button in the DETAIL band and the HEADER band.
2. The Properties/Print Specifications is set to "Display Buttons on Print Preview" is checked
3. The detail band is set as "autosizeheight".
4. The datawindow must be a SQ L source datawindow and it must retrieve data (you don't have to show ANY columns anywhere in the datawindow but it MUST retrieve).

Once the datawindow is put into Print Preview, you can see the problem in the pagecount.

Also, if you take either the DETAIL band button or the HEADER band button out, this doesn't occur. It has to be in BOTH bands.

Workaround: Try turning autosizeheight of the detail band off and size the columns so they don't need slide or autosize.



CR:166925
CR Number:   166925
Product Name:   PB Enterprise
Product Component:   DB Sybase System
Status:   Closed
OS:   MS Windows 3.1
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.0.01 17 Jun 1998 Fixed
Description
6.0.00 Regression :
Calling an rpc function with an output parameter using the 16-bit SYC ct-lib interface in PowerBuilder 6.0
gives following error :
999 Number of parameters do not agree
Problem does not occur with PowerBuilder 5.0.03 16-bit
Workaround Description
 Use DB-lib interface.



CR:166933
CR Number:   166933
Product Name:   PB Enterprise
Product Component:   DW Painter
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.0.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.00 RC1 5010 01 Feb 1999 Fixed
Description
This problem was originally reported as CR 161435, this CR has now been closed. The problem was fixed by this CR, but only in preview and runtime modes. The problem still exists in design mode, the underline column property is still 'thicker' than it is when in design mode in PowerBuilder 5.x.





--------------------------------------华丽的分割线-------------------------------------------------------------------------

Sybase SQL Anywhere数据库恢复工具ReadASADB:

之前就已经研发成功了能够从Sybase SQL Anywhere的DB文件中恢复数据的工具: ReadASADB。
此工具支持ASA v5.0, v6.0, v7.0, v8.0, v9.0, v10.0, v11.0, v12.0, v16.0, v17.0等版本。
能够从损坏的SQL Anywhere数据文件(.db)和UltraLite数据文件(.udb)上提取数据的非常规恢复工具。
恢复Sybase SQL Anywhere的工具在国内处于领先水平。

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,16.x,17.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使用介绍

Sybase SQL Anywhere数据库恢复工具ReadASADB适用场景

各种误操作:

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

Sybase SQL Anywhere数据库恢复工具ReadASADB的应用场景:

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
7、*** ERROR *** Assertion failed: 201417 (7.0.4.3541) Invalid count or free space offset detected on a table page
8、Internal database error *** ERROR *** Assertion failed: 201425 (8.0.3.5594) Invalid count or free space offset detected on a free list page -- transaction rolled back.
9、Internal database error *** ERROR *** Assertion failed: 100702 (8.0.1.2600) Unable to modify indexes for a row referenced in rollback log -- transaction rolled back


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

Sybase ASE数据库恢复工具READSYBDEVICE:

一个不依赖数据库管理系统、直接从Sybase数据库设备文件上提取数据的业内领先的恢复工具!
能够从损坏的Sybase ASE设备文件(.dat)上提取数据的非常规恢复工具。

Sybase ASE数据库恢复工具READSYBDEVICE的主要功能:

  1. 被勒索病毒加密数据文件及备份文件情况下的恢复;
  2. 系统崩溃只剩下数据文件的情况下的恢复,甚至数据库文件不存在而只有损坏的备份文件情况下的恢复;
  3. 因断电、硬盘坏道等造成数据库文件损坏情况下的恢复;
  4. delete数据恢复、误update数据恢复、误删除表(drop)恢复、误truncate表恢复 等;
  5. 各种Sybase内部系统表损坏、索引错误的修复;
  6. master数据库损坏而无法正常运行情况下的恢复;
  7. Sybase数据库被标记为可疑,不可用等情况的恢复;
  8. Sybase数据库中数据文件内部出现坏块情况下的恢复;
  9. Sybase数据库无数据文件但有日志文件的情况下的恢复;
  10. Sybase数据库只有数据文件无任何日志文件的情况下的恢复;
  11. Sybase数据文件被误删除情况下的碎片提取恢复;
  12. 磁盘阵列上的Sybase数据库被误格式化情况下的数据库恢复;
  13. 数据库sysobjects等系统表损坏无法正常应用情况下的恢复;
  14. Sybase数据库还原数据库出现失败情况下的恢复;
  15. Sybase数据库只剩下损坏的备份文件情况下的恢复。

Sybase ASE数据库恢复工具READSYBDEVICE支持的版本:

Sybase ASE 11.0.x,11.5.x,11.9.x,12.0.x,12.5.x,15.0.x,15.5.x,15.7.x,16.0.x


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

SQL Server数据库恢复工具SQLRescue:

一个不依赖数据库管理系统、直接从SQL Server数据库文件上提取数据的业内领先的恢复工具!
能够从损坏的SQL Server数据库文件(.mdf)上提取数据的非常规恢复工具。

SQL Server数据库恢复工具SQLRescue的主要功能:

  1. 系统崩溃只剩下数据文件的情况下的恢复,即无日志文件或者日志文件损坏情况下的恢复;
  2. 断电导致数据库文件损坏情况下的恢复;
  3. 硬盘坏道造成数据库损坏情况下的恢复;
  4. 数据文件内部存在坏页情况下的恢复;
  5. 企业管理器误删除数据表记录,管理软件误删除数据表记录的恢复;
  6. 并闩锁错误、格式化、误删除后导致软件不能使用的情况;
  7. 无法读取并闩锁页sysindexes失败情况下的修复;
  8. 数据文件被误删除情况下的碎片提取恢复;
  9. 系统表损坏、索引错误、误删除数据库表、删除记录的数据找回;
  10. master数据库损坏而无法正常运行情况下的恢复;
  11. 数据文件无法附加情况下的数据恢复;
  12. 数据库被标记为可疑,质疑,不可用等情况的恢复;
  13. 数据库sysobjects等系统表损坏情况下的恢复;
  14. 数据被误(drop、delete、truncate)删除表数据的恢复,误update后的数据恢复等;
  15. 还原时报一致性错误,错误823等情况下的数据恢复,各种错误提示的数据库文件修复;
  16. 数据库被误格式化等情况下的数据库恢复;
  17. 日志收缩造成数据库损坏情况下的恢复;
  18. 仅剩损坏的备份文件情况下的恢复。

SQL Server数据库恢复工具SQLRescue技术特点:

只要SQL Server数据库的数据文件存在,我们就有办法帮您从数据文件中找回重要数据。
  1. 从数据文件中直接恢复数据
  2. 不能附加时直接恢复数据并生成新的数据库
  3. 系统表损坏的数据库修复
  4. 快速修复SQL 823错误、连接中断错误

SQL Server数据库恢复工具SQLRescue支持的版本:

Microsoft SQL Server 7.0, 2000, 2005, 2008, 2008R2, 2012, 2014, 2016, 2017,2019。
+-------------------------------------华丽的分割线-------------------------------------------------------------------------