提供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:193231
CR Number:   193231
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
22 Mar 1999 Not a Bug
Description
Page number in Print preview mode may be incorrrect. Test case showed first page labelled page 2.



CR:193242
CR Number:   193242
Product Name:   PB Enterprise
Product Component:   DB Painter
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   7.0.00 RC1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.x Catalina 1148 28 Oct 1999 Fixed
Description
EA Studio 3.0 Beta:
In database painter, in the Procedures & Functions tree in the Object Panel, the Edit Data menu on RMB should not be enabled when a Function is highlighted. This is not a high priority because clicking the Edit Data menu does nothing, but it could be confusing to users.



CR:193244
CR Number:   193244
Product Name:   PB Enterprise
Product Component:   DW HTML
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   7.0.00 RC1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.00 7004 16 Jul 1999 Fixed
Description
EA Studio Beta: Free form HTML datawindow. Netscape 4.x shows all Edit style fields having the same width, regardless of the actual datawindow setting for the width.



CR:193284
CR Number:   193284
Product Name:   PB Enterprise
Product Component:   PB GUI
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12 Dec 2000 Presently Not Targeted For Any Future Release Of This Product
Description
The IsDate() and Date() functions may return incorrect values when the regional setting for date is 'yyyy/dd/mm'.

Example is using "1998/25/12" which returns FALSE with IsDate() and '1900-01-01' with Date() which means "invalid" .
No good workaround with regional settings set this way.

Closely related to CR197884, 197886)



CR:193287
CR Number:   193287
Product Name:   PB Enterprise
Product Component:   Window - Runtime
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
When a window has a rightoleft attributes it does not appear in 3D.
In 6.5 it happens the second time you open the window and in 7.0 it is not in 3D at all.



CR:193296
CR Number:   193296
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
If you change the background mode of a column when the DW has no rows, the column turns to protect mode.
Workaround Description
 1 - Do not change the background mode of a column when no rows has been retrieved.
2- Add :
dw_1.object.emp_id.Protect='1'
dw_1.object.emp_id.Protect='0'
To turn off the protect mode



CR:193298
CR Number:   193298
Product Name:   PB Enterprise
Product Component:   DW HTML
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.00 Beta 3
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.x Catalina 1027 25 Feb 2004 Fixed
Description
WRAP attribute not being set for TEXTAREA fields in HTMLDW forms. As a result, the behavior defaults to OFF
(the user must type in CRs, and they are embedded in the result).



CR:193304
CR Number:   193304
Product Name:   PB Enterprise
Product Component:   DB Oracle
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.5.00 590 27 Apr 1999 Fixed
Description
Updatabale cursors do not work with OR8 and O84. A GPF occurs when a row is fetched from the cursor.



CR:193349
CR Number:   193349
Product Name:   PB Enterprise
Product Component:   DW Display
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.5.00 08 Apr 1999 Fixed
Description
When decimal datas are saved in a datawindow and field is NUMBER datatype, then decimal part is lost when previewing datawindow.



CR:193365
CR Number:   193365
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
ImportFile doesn't work with graph controls (returnCode is -8 : not a txt file)



CR:193374
CR Number:   193374
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
01 Apr 1999 Presently Not Targeted For Any Future Release Of This Product
Description
A page fault will occur while previewing a DataWindow in the painter or at runtime.
It appears to be directly related to: Line objects side-by-side and the following scenario:

1) AutoSize Height for a column is ON
2) Line objects: Align Top or Bottom edges
3) Line objects Position property: SlideUp = AllAbove
If ANY of these three is NOT set, the page fault will not occur.
If all three ARE set but the Position property is set to DirectlyAbove the page fault DOES NOT occur.

*This does not happen in PowerBuilder 7.0.

Workarounds:
==========
#1. Don't ALIGN top or bottom edges using the menu option
#2. Set the Slide Up property of all fields of the two left-most Line Objects to "Directly Above" while leaving the Slide Up property of all other fields in the datawindow as "All Above".

Per Development:
Not to be fixed.



CR:193379
CR Number:   193379
Product Name:   PB Enterprise
Product Component:   OLE - Active X - OCX
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
Customer built an OCX using Visual Basic. It works fine when used on a PB window in an NT 4.0 environment but when used in a WIN95 environment when the user tries to close out the window the user will get an illegal page fault in user.exe at 0004:00000497. The actual OCX appears to work fine on both platforms until the user tries to close out the window on WIN 95.

Running with both PB 6.5 and 7.0 resulted in the same page fault when run on a WIN95 machine.



CR:193386
CR Number:   193386
Product Name:   PB Enterprise
Product Component:   DW Painter
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.00 Beta 3
Fixed Version Build Resolution Date Closure Code (If Appropriate)
09 Apr 1999 Fixed
Description
PB 7.0 Beta 3 build 5028

IM7/PB7: no help for rtf replace option



CR:193402
CR Number:   193402
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
18 Mar 1999 Not a Bug
Description
When applying SetFilter + Filter() to a Crosstab datawindow if there are 2 rows selected in the crosstab dw definition and the filter is carried out on the second of the 2 selected rows then if the filter expression filters out what would be the last row of the dw the result is that the summary band slides up and is superimposed on top of the detail band.

eg a dw with 4 cols in select: dept_name, status, sex and salary (psdemodb)

Crosstab definition:

Rows: sex
status

Columns: dept_name

Values: sum(salary for crosstab)

Filter expression dw_1.SetFilter("status = 'A'") Shows the problem because the last row in this dw has a status of L (at least it does in my db) and this will get filtered out.

Status='L' works OK as do filter expressions Sex='M' and Sex='F'
Workaround Description
 Sort dw beforehand



CR:193411
CR Number:   193411
Product Name:   PB Enterprise
Product Component:   DB Sybase System
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
02 Jan 2002 Not a Bug
Description
Using an SYC connection. Fetching from a cursor that references a Sybase proxy table causes error: 'No CS_command pointer passed to function RTFETCHNEXT'.
Workaround Description
 Use a datawindow instead of a cursor to retrieve data.



CR:193454
CR Number:   193454
Product Name:   PB Enterprise
Product Component:   DB Painter
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.00 Beta 3
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.00 EBF1 6001 09 Apr 1999 Fixed
Description
EA Studio 3.0 Beta:
PB 7.0 DB Oracle - Cannot export view syntax correctly. If the syntax for the view itself is longer than 812 characters, it's truncated.

This is fixed for post-7.0, and has been back-patched to 7.0 for the first EBF.



CR:193455
CR Number:   193455
Product Name:   PB Enterprise
Product Component:   DB Painter
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.00 Beta 3
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.00 EBF1 6001 09 Apr 1999 Fixed
Description
PB 7.0 Beta 3 -View Syntax no longer contains column aliases



CR:193457
CR Number:   193457
Product Name:   PB Enterprise
Product Component:   DB Oracle
Status:   Open
OS:   MS Windows NT 4.0
Original Version:   7.0.00 Beta 3
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
ENHANCEMENT REQUESTED

1. Add support for packages in addition to procedures and functions
in the painters. There is a system package now that properly
describes the functions/procedures within a package, so there is no
longer a reason not to include them.

2. Show sequences as another object type that PB can work with.

3. Use "CREATE OR REPLACE" rather than "CREATE" when
generating syntax for objects that support the "CREATE OR REPLACE"
option.



CR:193464
CR Number:   193464
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.5.00 609 30 Mar 2000 Fixed
Description
If you call SelectRow() for a datawindow row that is not completely in view, it will not show as as selected until you scroll it into view.
Workaround Description
 After you call SelectRow(), call ScrollToRow() to bring the row into view. This will cause the data in the datawindow to jump.



CR:193557
CR Number:   193557
Product Name:   PB Enterprise
Product Component:   DB Sybase System
Status:   Open
OS:   MS Windows NT 4.0
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
The client would like an enhancement made so that the password is going to expire soon message is passed through to PB so either it can be used by the PWDialog DBPARM or allow the application to programmatically trap the message.

PWDialog currently allows the user to change an "expired" password.



CR:193559
CR Number:   193559
Product Name:   PB Enterprise
Product Component:   DW Edit Mask
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
Datawindow with datatype number column and a mask #,##0.00;[Red] -#,##0.00 fails when regional settings is set on English (USA).
The red color, the decimal and thousand sepeators are not displayed anymore. This happen with German NT4.0 and only with English(USA), (Trinidad), (Jamaika) reginal settings. Works fine for example with German (Deutschland) or English (Grossbritanien) settings.

Per Development, this is not a bug:
The problem is in the format mask itself. The compiler does not like the '-' after the [Red], it will only accept a '-' at the beginning of a section. A section begins just after the ';'. The following is a mask which will compile for English and German:
IF (figureunit = 2, '#,##0.00 %', '#,##0.00;-[Red]#,##0.00') Note the '-' is before the [Red] and directly after the ';'
The example is directly from the pbl and works for both German and English.



CR:193577
CR Number:   193577
Product Name:   PB Enterprise
Product Component:   DW DDDW
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.00 EBF1 6004 08 Apr 1999 Fixed
Description
6.5 Regression builds > 560 and Beta 7.0: DropDownDataWindow in preview mode is missing the left and top outer border.
Possible workaround: If "always show arrow" is checked, set border = box on column



CR:193592
CR Number:   193592
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   Microsoft Windows 98
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.x Catalina 08 Apr 1999 Fixed
Description
In the user event with map to PB predefined event ID
pbm_dwescape, the line "Close(parent)" in
the dw user event script causes a gpf in the exe e.g. PB060.exe
Workaround Description
 If the script is coded as :
Post Close(parent) instead of Close(parent), this does not cause PB to crash.



CR:193598
CR Number:   193598
Product Name:   PB Enterprise
Product Component:   Windu/U
Status:   Closed
OS:   HP-UX 10.20
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
When your in the printer setup display and than select "setup", once you
hit the "save" cb the current printer is not hightlighted or selected anymore on HPUX or AIX.

On solaris 2.5.1, the first printer in the box is always hightlighted after you hit the "save" cb.
On solaris 2.6, the second printer in the box is always hightlighted after you hit the "save" cb.



CR:193607
CR Number:   193607
Product Name:   PB Enterprise
Product Component:   DW HTML
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.00 RC1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.2 8026 01 Aug 2000 Fixed
Description
Weird formatting of the HTML datawindow using datetime columns. If you have the following conditions and do a Design/HTML Preview, you will get strange data in the columns.

- having HTML Generation/Client formatting on for the datawindow.
- a datetime column (not just a date column)
- not the initial generation of the HTML, but the HTML resulting after a SetAction.

Tabbing OFF the column shows this data...

NaN/undefined/aN undefined:undefined:undefined



CR:193609
CR Number:   193609
Product Name:   PB Enterprise
Product Component:   DW HTML
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.00 RC1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
25 Feb 2004 EOL'd version. Not to be Fixed.
Description
Powerbuilder 7.0 Beta:
Delete functionality for HTML DW does not work if DW is on the last row



CR:193621
CR Number:   193621
Product Name:   PB Enterprise
Product Component:   Library Painter
Status:   Open
OS:   MS Windows NT 4.0
Original Version:   7.0.00 RC2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
1) The search result dialog box in the library painter is not resizable, or add a 'full screen' button

2) There is no search (&replace) across multiple PBLs.



CR:193667
CR Number:   193667
Product Name:   PB Enterprise
Product Component:   DW SaveAs
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   5.0.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.5.00 621 05 Aug 1999 Fixed
Description
PB generates an error Exception Access Violation/Out of memory in all versions of PB on NT4.
Win98 has a problem with versions PB6 and later.

SaveAs PSR format OK on Win98 (all versions)
SaveAs PSR format OK on NT (except low versions - PB5 crashes)

PB6.5 does not have a Deployment DLL kit for Finnish language.

PB Deployment Tested SaveAs WMF:
Win98 with French Deployment DLL's result PB65_444 Broken
Win98 with English Deployment DLL's result PB65_444 Broken
Workaround Description
 None as yet.



CR:193685
CR Number:   193685
Product Name:   PB Enterprise
Product Component:   Window Painter
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
13 Nov 2001 Fixed
Description
Saving a large window after adding a large visual user object lead to GPF
Workaround Description
 a- Move all instances variables to a new user object. Add this new user object as an instance variable to u_dw_sai . Then modify script to compile fine the application.



CR:193689
CR Number:   193689
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
When specifying an editmask for dates (window or datawindow) the symbols used as 'place holders' are zeros
eg 00/00/0000. Ct would prefer to have the option to use a different character in the date editmask eg ??/??/???? (l
to make it possible to differentiate between 'real' zeros or those used as 'place holders'



CR:193713
CR Number:   193713
Product Name:   PB Enterprise
Product Component:   UO - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
Memory usage goes up by just connecting and disconnecting from server
in PB 6.5 and PB 7.0.



CR:193719
CR Number:   193719
Product Name:   PB Enterprise
Product Component:   DW Display
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.00 EBF1 6004 08 Apr 1999 Fixed
Description
When a column has a font escapement set, then part of the text can be drawn outside
the normal column area.
PB6.5 Builds 482 and later do not properly redraw the text part outside the column rectangle



CR:193734
CR Number:   193734
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 Mar 1999 Duplicate
Description
Datawindow with newspaper columns that contain a nested report lose its formating when placed in a composite report



CR:193752
CR Number:   193752
Product Name:   PB Enterprise
Product Component:   Shared Objects
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
Once a client connects to a server and you create and then
destroy the shared object, the thread count does not go back to the value of what
it was before you did the create of the shared object.

If you continue to connect/create shared object/destroy object and than
disconnect from the server, the thread count continues to incremate by 1.



CR:193776
CR Number:   193776
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
28 Mar 2000 Fixed
Description
The resetupdate() function on a "master" datawindow alters the current row of a shared datawindow to 1. The workaround is to use getrow() before the resetupdate function and do a setrow() after the resetupdate() function on the shared datawindow. See below the code example:

dw_master.retrieve()
dw_master.sharedata(dw_detail)
dw_master.ResetUpdate()

WORKAROUND:
long ll_row
dw_master.retrieve()
dw_master.sharedata(dw_detail)
ll_row = dw_detail.getrow()
dw_master.ResetUpdate()
dw_detail.setrow(ll_row)


Tried the above workaround and setrow() did not work but ScrolltoRow() did.

Code sample that worked for me:
long ll_row

ll_row = dw_1.getrow()
dw_2.resetupdate()
dw_2.scrolltorow(ll_row)
Workaround Description
 long ll_row
dw_master.retrieve()
dw_master.sharedata(dw_detail)
ll_row = dw_detail.getrow()
dw_master.ResetUpdate()
dw_detail.setrow(ll_row)



CR:193793
CR Number:   193793
Product Name:   PB Enterprise
Product Component:   Source Control
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.00 RC1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.00 EBF1 18 May 1999 Fixed
Description
Inability to check in to PBLs not in library path is considered by customer to be a major problem. Background:

If your source control system does not support Add Object function, then you are going to have to use the old method of performing version control. You'll have a set of registered libraries that everyone will check-in/check-out from and another set of libraries that people will test run their applications against to avoid the locking of the libraries.

So it sounds as though we'd have to:

1) change our lib list to include the registration pbl.
2) check out the object
3) change the lib list again to remove the registration pbl.

This is extremely inconvenient and difficult to work with.



CR:193810
CR Number:   193810
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.00 RC1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.00 EBF1 1026 20 Apr 1999 Fixed
Description
HTML DW broken using IE 5 GA.

Per development: This is believed to be a bug with IE 5. HTML DW works prior to IE 5 GA, and worked using IE 5 beta. Development
will attempt to code a workaround on our side, but can make no guarantee.



CR:193812
CR Number:   193812
Product Name:   PB Enterprise
Product Component:   PB GUI
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.00 RC0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
25 Feb 2004 EOL'd version. Not to be Fixed.
Description
Beta 7.0: This is NT specific
When using "Snap mouse to default button in dialogs" - mouse settings: Clicking tab pages in a view such as the Properties view, makes the pointer "jump".



CR:193836
CR Number:   193836
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
When in a For loop changes are made to the dw using dot notation to change values using GetitemNumber, the performance has gotten significantly worse when migrating from PB 5.0.04 to PB 6.5.

The line of code causing the performance problem is :

lds_merged.Object.format_code[ll_row] = lds_merged.getitemnumber(ll_row, "source_flag")

In the example that accompanies this case what used to take 2 seconds with pb5.0.04, now takes 2 minutes with pb6.5. If the line of code within the For loop is commented out, the performance is essentially the same as in PB 5.0.04. In this example the changes are being made to a datastore but when used with a dw it appeared essentially the same.

There were many CR's that appeared related, both still open and some fixed in 5.0.03/04. I did not find one that appeared to be exactly the same.



CR:193843
CR Number:   193843
Product Name:   PB Enterprise
Product Component:   Jaguar Integration
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.00 RC0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.00 14 May 1999 Fixed
Description
Retrieving a resultset from jaguar returns nothing to the
dw control.

Resolution:
A couple of things needed to be changed (in the client pbl) to work properly.
1. Declaring a datasore as an instance variable rather than with in the event code and
2. Associating the datawindow control with a datawindow object

After the above changes, the dw control worked properly.



CR:193891
CR Number:   193891
Product Name:   PB Enterprise
Product Component:   Window Painter
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.00 RC2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
22 Jun 1999 Fixed
Description
Deleting an object from a window when that object is still referenced somewhere in the object causes
an Access Violation on Save As - instead of compiler warning.



CR:193905
CR Number:   193905
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
14 Nov 2000 Fixed
Description
If you click in spaces between rows the clicked event no longer returns 0 for the row argument with ebf 585. this is broken between builds 492 and 585. Works fine for the maintenance Release 6.0.01 and 6.5. Happens only with latest EBFs.

WORKAROUND:
implemt in clicked event something like:
long myrow
if dwo.name = 'datawindow' then
myrow = 0
else
myrow = row
end if



CR:193920
CR Number:   193920
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.5.00 600 06 Oct 1999 Fixed
Description
Problem with dw HTML generation when the dw object property "generateCSS" is set to "no".

(dw_1.object.datawindow.HTMLtable.generateCSS = "no" or ls_rc = dw_1.Modify("datawindow.HTMLTable.GenerateCSS="no")

No is the default according to the documentation, but even if set explicitly it does not take effect in PB 6.5 for any style but grid.
With PB 7.0 it does not take effect for any style including grid.

When it is set to "no" the generated HTML should not include any reference to the classes generated in the "StyleSheet".



CR:193954
CR Number:   193954
Product Name:   PB Enterprise
Product Component:   Help
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.00 RC1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
22 Apr 1999 Fixed
Description
EA Studio 3.0, Powerbuilder 7.0:
Online help implies that HTML DW supports Nested datawindows. HTML DW has not been implemented for Nested datawindows.
The following places incorrectly included nesteds, and should not:
Online help discusses HTML DW and includes Nested reports. HTML was not implemented for nested. Details from customer:
In the "Data.HTMLTable DataWindow Object Property", "Generating HTML" and "Writing the user object method" pages, the following quote is found:
"The Composite, RichText, Graph, and OLE 2.0 presentation styles and nested reports produce HTML tables based on the result set only and not on the presentation style."
I haven't been able to produce HTML for any nested reports.
On the "Displaying DataWindow Objects As HTML Forms" page, the following quote is found:
"Embedded nested DataWindows display as HTML tables within the form"



CR:193980
CR Number:   193980
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.5.00 22 Jun 2000 Not a Bug
Description
In a shared datawindow, InsertRow() and ResetUpdate() fires RowFocusChanged and RowFocusChanging events and changes the current row to 1.

ResetUpdate() was fixed and does not cause RowFocus events to fire. However InsertRow() does. See below.

Per Development:
This is not a bug. RFC has to fire in the InsertRow() circumstance. All actions in the shared DataWindow environment take place on the parent DataWindow and the shared children are sync'd to the parent. The process of sync'ing to the parent sets the current row to 1 and current column to 1 and this will fire the RFC events. It is always necessary to sync to the parent and it is always necessary to set the current row and column.



CR:193987
CR Number:   193987
Product Name:   PB Enterprise
Product Component:   Jaguar Integration
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.00 RC1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
25 Feb 2004 EOL'd version. Not to be Fixed.
Description
The "properties" button of the select object dialog box
doesn't appear to do anything. It's enabled when a component is hightlighted.
Once you select it (properties button), nothing happens and then it just becomes
disabled again.



CR:194019
CR Number:   194019
Product Name:   PB Enterprise
Product Component:   DW Edit Mask
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
with edimask dd/mm/yyyy you can't change date 12-02-98 simply to 31-03-98 because 'online-type-checking' will not accept febr 31st as a valid date. You'll have to change first the month and then back to the day.
workaround:
if you like to change it without 'online-type-checking' set date to null



CR:194029
CR Number:   194029
Product Name:   PB Enterprise
Product Component:   DW Display
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Mar 1999 Not a Bug
Description
a composite dw cut the last Column of his nested grid datawindow when you zoom in print preview



CR:194064
CR Number:   194064
Product Name:   PB Enterprise
Product Component:   Jaguar Integration
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.00 RC2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.00 RC2 25 Feb 2004 Fixed
Description
GetFullState() on a datastore that has a DropDownDatawindow in Jaguar, the returning blob will contain duplicate entries for the last dropdowndatawindow.



CR:194101
CR Number:   194101
Product Name:   PB Enterprise
Product Component:   DW Display
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.00 EBF1 6004 07 Apr 1999 Fixed
Description
When the datawindow object and datawindow control are almost the same size,
PowerBuilder 6.5 Build may draw scrollbars in the datawindow control where earlier
Builds did not. PB7 Build 5031 has the same behaviour as the later Builds of PB6.5



CR:194134
CR Number:   194134
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.00 EBF1 6004 09 Apr 1999 Fixed
Description
In all versions of PB tested from 5,0,03 through PB 7.0 build 5031 when the detail height of rows in a tabular datawindow is set to 0 using dw_1.setdetailheight(start row, end row, 0 ) the user is unable to use the up arrow key. The down arrow key and the mouse work fine for navigation, but the up arrow key does not work when a point is reached in the datawindow where there is a row with a height of 0 right above it.



CR:194148
CR Number:   194148
Product Name:   PB Enterprise
Product Component:   DDE
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
25 Jun 1999 Third Party Problem
Description
Using DDE's getremote function for a cold link returns -3 under nt 4.0 sp 4. Under sp3, works ok. The app works fine using dde warm link under nt 4.0 sp3 and sp4.

6/25/99 Per Development this is not a PB bug:
The problem is that when doing a getremote function call for a cold link in service pack 4, the user is getting a return code from us of -3. In service pack 3, it returns cleanly. Even with a return code of -3, the data is coming back fine. In the code, after we've received the data we do a post of WM_DDE_TERMINATE and then we wait for our WM_DDE_TERMINATE. We never get the terminate and thus the -3. When I compare dde messages in Spy between service pack 3 and 4, indeed, we get our terminate in sp3 but not in sp4.

The following article describes problem with sp4 on nt 4.0 from Microsoft:
http://support.microsoft.com/support/kb/articles/q231/3/37.asp



CR:194180
CR Number:   194180
Product Name:   PB Enterprise
Product Component:   Generators
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
25 Feb 2004 EOL'd version. Not to be Fixed.
Description
COM generator link errors when long filenames have spaces, period.

You can create a project with a path that contains spaces/periods, but the build fails intermittently. If you move an existing project to a path which contains a space and/or a period/dot, you cannot change the properties to reflect the new path. You will get an error message of "Missing or Invalid Component Server File Name"

Workaround: Use directory names with no spaces or periods.



CR:194181
CR Number:   194181
Product Name:   PB Enterprise
Product Component:   DW Graph
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.x Catalina 1032 07 Apr 1999 Fixed
Description
Graph is changed dynamically using modify to change the category, value and series on a graph. Sample is a 3d pie graph but trying other types of graphs resultied in the same behavior. Eventually making these changes results in an illegal page fault in pbdwe60.dll. Sometimes several changes can be made, other times it crashes the first time they are changed. Specific changes do not seem to matter.

Problem occurred on both WIN95 and NT4.0 and when tested on NT 4.0 this did not appear to be related to any memory leak. Tried using Yield() and Setting redraw to false but this did not correct the problem.



CR:194183
CR Number:   194183
Product Name:   PB Enterprise
Product Component:   Edit Mask
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.0.04 06 Jul 1999 Fixed
Description
If a column (from a database table or external datasource) has a datatype of datetime and EditMask mm-dd-yyyy, if you clear out the date by hitting the backspace key or delete it refreshes to 00-00-0000 which is should do, BUT when you tab off the column it changes to 01-01-0000.
If the column is of type DATE and is 'cleared out' the date EditMask will remain 00-00-0000 when tabbing off.
Also if the EditMask uses slashes instead of dashes, mm/dd/yyyy this behavior will NOT occur.



CR:194186
CR Number:   194186
Product Name:   PB Enterprise
Product Component:   Jaguar Integration
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.00 RC1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
24 Sep 1999 Fixed
Description
When creating a jaguar component of type "service" and
its deployed to Jaguar, the jaguar's server "com.sybase.jaguar.server.services"
property isn't being updated with the package/component name.

You must manually entered it in. According to the Application Techniques manual
for PB 7.0, "Creating a service component", this property is automatically updated
for you when you deploy the service component.



CR:194201
CR Number:   194201
Product Name:   PB Enterprise
Product Component:   Function Painter
Status:   Closed
OS:   Solaris 2.5.1
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
Errors when calling an external global function.

The function declaration is as follows:
FUNCTION string getcwd(REF string buff, UnsignedInteger size) LIBRARY "/usr/lib/libc.x"

The function is being called as follows:
string ls_return, ls_directory
ls_directory = space(100)
ls_return = getcwd(ls_directory, 100)

Sun Solaris: On sun, the function works ok. Although if you take out the line ls_directory = space(100), pb will crash with a segmentation fault.
HP-UX: Calling this function above will just hang pb.
AIX: Calling this function will result in the following error:
Error opening DLL library xxxx/libc.a for external function at line 5 in clicked event of object cb_1 of w_test
Also ran as root and got the same error.

Application works ok using PB 6.5 solaris 2.6 (build 565).



CR:194207
CR Number:   194207
Product Name:   PB Enterprise
Product Component:   Function Painter
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.x Catalina 14 Aug 2000 Fixed
Description
he Application Techniques manual for pb 6.5 and 7.0 that
describes "Calling external functions and programs on Unix" shows a function
declaration for Solaris. This function declaration is incorrect. If this function
is typed in this way on Unix, you'll get a syntax error.

Currently:
FUNCTION string getcwd(REF string buff, unsigned int size) LIBRARY "/usr/lib/libc.so"

Should Be:
FUNCTION string getcwd(REF string buff, UnsignedInteger size) LIBRARY "/usr/lib/libc.so"

In the Powerbuilder Powerscript Reference: Volume 1, Chapter 3, it discusses the datatypes
to be used for external functions. For unsigned int (32 bit platforms), it list UnsignedInteger.



CR:194209
CR Number:   194209
Product Name:   PB Enterprise
Product Component:   Debugger
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.00 Beta 3
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15 Apr 1999 Not a Bug
Description
When running an application with the debugger, but with no breakpoints set, the debugger stops at the line of code that causes an error.



CR:194239
CR Number:   194239
Product Name:   PB Enterprise
Product Component:   DW Synchronization
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.5.00 11 Oct 2000 Fixed
Description
6.5.1 Regression. Setfullstate() on a dw that is placed on a uo tabpage on a tab control move the dw to a other place on the uo/tabpage. This might be caused by triggering the resize event when you call setfullstate(). When this happens iteratively, the datawindow control on the tab page gets smaller and smaller until it disappears.

Workaround: for example place in the resize event of the dw the values of the x and y propertie of the dw or move the dw back after the the setfullstate call by code.
example.:
this.x = 90
this.y = 200

See 200150 as well for memory leak fix related to setfullstate().

This works fine in 7.0 and in 6.5 builds > 1065.



CR:194279
CR Number:   194279
Product Name:   PB Enterprise
Product Component:   Window - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.00 Beta 3
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.00 8003 19 Dec 2000 Fixed
Description
In PB 7.0 on a treeview when the default textcolor is changed the change does not take effect when running the window. If you export the syntax the textcolor is changed. Also the backcolor on the actual tree is white while the bigger part of the control's color is changed to what the backcolor has been changed to.

In PB 6.5 the problem with the textcolor still exists but when running the window the entire backcolor is changed to the color selected.

Other information: The Treeview control uses the WindowText and WindowBackground for the font regardless of what is chosen. The background will be the font background but the the label (text) of the treeview items always uses the windowbackground text color. You can see this by importing the .srw and twiddling the NT defaults:

The treeview is taking on the Window Text color of the NT system. To see this.
- Right Mouse on NT Desktop
- Go to "Appearance" tab
- click on "Window Text" area to populate the Item/Font values.

For the items:

Item:

Font:

This is what controls the background of the treeview and the treeview icons (things like Folders). The user believes this should be controlled by the

treeview.fontcolor
treeview.backcolor

attributes instead of going directly to the NT defaults. (and ignoring any changes to these two treeview attributes.



CR:194376
CR Number:   194376
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.5.00 613 30 Apr 1999 Fixed
Description
MS SQL Server 7.0 w/ODBC: DateTime column update causes error if DisableBind=1. Error also occurs in a SELECT statement w/a WHERE clause that contains datetime argument.
"Error 241 SQLSTATE=22008 [Microsoft][ODBC SQL Server Driver][SQL Server]Syntax error converting datetime from character string"

Workaround: There is a DBParm that you can set in script or in the Profile in the Syntax tab under formats. Format DateTime to: =' \''mm-dd-yyyy hh:mm:ss.fff \'' ' so the time part will have 3 digits instead of 6.



CR:194382
CR Number:   194382
Product Name:   PB Enterprise
Product Component:   DW Plugin
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.00 RC1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
25 Feb 2004 EOL'd version. Not to be Fixed.
Description
The dw plugin (psr report) does not view in the Netscape browser
when using nt 4.0 sp4 and win95b. When viewing the page source, it shows
the correct mime type of application/datawindow7.

Under nt 4.0 sp4, when closing out of Netscape 4.5, the browser will gpf.

On win95b, (KFrantz) used Netscape 4.06.

Workaround: Works ok on nt sp3 and win95a.



CR:194383
CR Number:   194383
Product Name:   PB Enterprise
Product Component:   ORCA
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.5.00 18 Jun 1999 Duplicate
Description
When a datawindow is regenerated using ORCA's CompileEntryRegenerate the resulting datawindow is not evaluating expressions properly.

The example expression on the dw is as follows:

If (cmp_frame = 1.1, 'L', if (cmp_frame = 0.9, 'S', 'M'))

So entering a value of .9 for cmp_frame should have this expression
evaluate to 'S'. And it does, when regenerated from the Library Painter, or from an exe generated by the project painter. But
when the datawindow is regenerated with ORCA, or an executable is made through ORCA it does not evaluate
properly, returning 'M' instead.

The following expression which should be equivalent and always evalutates correctly:

If (cmp_frame = Dec ('1.1'), 'L', if (cmp_frame = Dec ('0.9'), 'S', 'M'))

If a full rebuild in the Library Painter is done after the ORCA regeneration then it also evaluates correctly. Although I could not test it because the ORCA sample only includes PB 5.0 functionality there is a possibility that if the PB 6.0 ORCA pborca_application rebuild was performed prior to building a runtime library or executable the resulting evaluation will be correct.



CR:194421
CR Number:   194421
Product Name:   PB Enterprise
Product Component:   Window - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.5.00 19 Aug 1999 Fixed
Description
When using the clipboard function to copy a graph to the
clipboard, it always returns -1. Copying a string text works ok. Clipboard function
returns -1 when trying to copy a graph object and a graph inside a datawindow
object.



CR:194450
CR Number:   194450
Product Name:   PB Enterprise
Product Component:   UO Painter
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.00 RC1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
25 Feb 2004 Fixed
Description
When migrating a pbl that has local external functions
declared as RPC FUNC, the functions show up under local external functions
and as functions of that object. They show up twice.

When viewing an export of an nvo from pb6.5 and 7.0, the exports look the same.
It doesn't appear that the functions are in their twice.



CR:194488
CR Number:   194488
Product Name:   PB Enterprise
Product Component:   Window Painter
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   7.0.00 RC2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.00 EBF1 6008 22 Jun 1999 Fixed
Description
PB 7.0 Beta: Can't open window w_nested_criteria in the PB7 examples. GPF.



CR:194511
CR Number:   194511
Product Name:   PB Enterprise
Product Component:   DW Plugin
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   7.0.00 RC1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15 Jun 2004 EOL'd version. Not to be Fixed.
Description
Beta 7.0 build 5031 does not print the dw plugin if using WIN95b or WIN98. This happens if using IE4. If using Netscape and PB 7.0, the dw plugin does not view (see CR 194382)

This was also a problem in PowerBuilder 6.5 but it now works okay with build 590 (NPDWE60.DLL)



CR:194513
CR Number:   194513
Product Name:   PB Enterprise
Product Component:   DataBase Administrator
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.00 RC1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.00 EBF1 6004 15 Apr 1999 Fixed
Description
When connected to EAS Demo DB V3 in the DB admin painter
and you try to execute a stored procedure in the isql pane, you'll get a error
(Select error Sql State=S1010 [Microsoft][ODBC Driver Manager] Function
Sequence error) using the following syntax:

execute sp_customer_list;

Workaround:
The following statement works ok:
exec sp_customer_list;

The above two statements both work in PB 6.x.



CR:194529
CR Number:   194529
Product Name:   PB Enterprise
Product Component:   Query Painter
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
05 Apr 1999 Not a Bug
Description
If you add a second occurence of a table to a datawindow that already has a where clause on the table, you will get a syntax erro. The error is in the where clause which still reflects the originalk table name. the where clause should reflect the newly asisgned correlation name.
Workaround Description
 Convert the select to syntax and correct the problem by replacing the bad table reference in the where clause with the correct correlation name.



CR:194546
CR Number:   194546
Product Name:   PB Enterprise
Product Component:   DW Painter
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   7.x Catalina
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.x Catalina 1036 23 Apr 1999 Fixed
Description
If you are creating a datawindow with manual result set and pick a type which has another parameter (string, decimal, etc), after you pick the type and then tab, the cursor goes immediately to the name of the next argument, not to the other parameter. In 6.x, when you tabbed, cursor went to the next parameter for that argument.

Quick repro:
1) Create an external datawindow
2) Name the first argument, tab to type (string) and either leave it string or change to decimal. Now tab again: goes to the next argument line, not to the length (for string) or dec (for decimal). You have to click or Shift-Tab to get back.



CR:194552
CR Number:   194552
Product Name:   PB Enterprise
Product Component:   Language - Runtime
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
Change of event firing order when an event is posted from a response window



CR:194570
CR Number:   194570
Product Name:   PB Enterprise
Product Component:   Window Painter
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.00 RC2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15 Jun 2004 EOL'd version. Not to be Fixed.
Description
By opening window and closing it from window painter resources go down drastically (memroy leak). The same bug was created for datawindow painter group (CR191993)



CR:194585
CR Number:   194585
Product Name:   PB Enterprise
Product Component:   Rich Text
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   5.0.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
13 Jul 2000 Fixed
Description
Linecount() returns incorrect values for RichText when there are large amounts of text involved (approx 32000)



CR:194598
CR Number:   194598
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
05 Jul 2000 Not a Bug
Description
Opening a window in the ItemChanged event accepts value even though event returns 1

WORKAROUND:
Use a validation rule and move the code from the ItemChanged event to the ItemError event



CR:194603
CR Number:   194603
Product Name:   PB Enterprise
Product Component:   DW DDDW
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.5.00 1005 18 Aug 1999 Fixed
Description
This CR looks like a duplicate of CR 172725,

Under certain circumstances if one modifies the color of the background on a DDDW while program is running it will cause the text in the first row to dissapear. This only happens if the DDDW has focus and the text reappears when you tab off the column. This also only happens the first time the column has focus.



CR:194606
CR Number:   194606
Product Name:   PB Enterprise
Product Component:   Window - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
Sample application has a menu with a large number of menu items on it. Actual sheet does not have any other controls on it. Also as the problem is on NT 4.0 and not WIN95 this is not the WIN 95 limitaiton mentioned in Case 40507590.

When the sample is run on NT 4.0 it is impossible to open more than 12 sheets on my machine. If sheets are closed and then new ones are opened the limit is still 12 on my machine. If the menu is changes so that the sheet's menu has less items them more sheets are able to open.

When sample with large number of menu items was run on WIN95 in excess of 50 sheets were opened.



CR:194613
CR Number:   194613
Product Name:   PB Enterprise
Product Component:   DB Informix
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
19 Jul 1999 Third Party Problem
Description
An invalid page fault in module kernel32.dll at 0137:bff798e9
occurs when closing an application after the application performed the following
1) connected to informix 7.3,
2) called a local external function
3) disconnected

If the application just called the external function without connecting to
Informix than no problem. Using the native informix driver. Works ok
using informix thru odbc. Worked ok on win95b in PB 6.0. Works ok on nt 4.0.
Works ok in PB 7.0 (build 5031) on win95 and nt 4.0.
Failed in (builds 444 thru 585) on win95b. Failed in win95a in PB 6.0 and PB 6.5.

Per Development, this is not a PB bug, it is a Third Party problem. Customers can use the following workaround:
1) Declare the following local external functions:
FUNCTION ulong GetModuleHandleA(string dllname) LIBRARY "kernel32.dll"
FUNCTION boolean FreeLibrary(ulong hMod) LIBRARY "kernel32.dll"

2) Add the following logic PRIOR to disconnecting the transaction object for PBIN760:
ulong hMod
boolean bRC
hMod = GetModuleHandleA("TestDll.dll")
if IsNull(hMod) then
MessageBox("Error", "Unable to obtain handle for testdll.dll")
else
bRC = FreeLibrary(hMod)
end if
/* Now that TestDll has been freed, the atexit processing for isqlt07c will occur while pbin760 is still in the process address space */
disconnect using sqlca;



CR:194758
CR Number:   194758
Product Name:   PB Enterprise
Product Component:   DW Edit Mask
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.5.00 28 Apr 1999 Fixed
Description
yyyy-mm-dd editmask on a datetime dw column causes incorrect data if the value is deleted from the column

The data value for that column is 0000-01-01 00:00:00:000000 instead of NULL



Try to update the database with a datetime deleted from this editmask and the SQL generated is...

UPDATE tablename SET datetimecol = '0000-01-01 00:00:00.000000' WHERE ...etc



Up to 6.5.502 the SQL generated was...

UPDATE tablename SET datetimecol = NULL WHERE ...etc



The data is also correctly set to NULL if it's a date column instead of datetime or with other editmasks eg dd-mm-yyyy or even yyyy/mm/dd



Also happens with datetime editmask controls and GetData() -> gives 0000/01/01 00:00:00 and returns 1 (success)
Workaround Description
 Use yyyy/mm/dd instead of yyyy-mm-dd



CR:194804
CR Number:   194804
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
A embedded ole2 excel sheet ole object on a dw will not be filled with the db data,
when you add some columns in the data tab of the ole object.
Happens only on German NT and with German Office97



CR:194815
CR Number:   194815
Product Name:   PB Enterprise
Product Component:   Project Painter
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
Unicode executable creation: If the user binds an icon in the properties of the application, the unicode executable build will fail with the following error:

Link Errors - Create of Executable file failed. If the Icon is removed the executable is created without a problem,



CR:194834
CR Number:   194834
Product Name:   PB Enterprise
Product Component:   Machine Code Deployment
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.5.00
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 the app as a machine code exe, the app
will crash with a reference memory error on nt. On win95, invalid page fault
in pbvm60.dll. The problem seems to be in w_csr_browse_claim/ue_viewclaim.
The structure consist of powerobject datatypes, integers,strings, etc.

Works ok as a pcode exe and in development on nt/win95. Works ok on nt as a machine code
exe when using /pbdebug.



CR:194844
CR Number:   194844
Product Name:   PB Enterprise
Product Component:   Jaguar Integration
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.00 RC2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Sep 1999 Fixed
Description
Deployment of PowerBuilder component to Jaguar:
Setting the "Component Timeout" (found on the Components tab of the "Properties for Jaguar Component Generator" dialog in the project painter) has no effect on the deployed component. The Jaguar property (com.sybase.jaguar.component.timeout) is NOT set. The Jaguar
property (com.sybase.jaguar.component.tx_timeout) IS being set. ALl of the help file verbiage refers to the component timeout NOT the transaction timeout.

This causes a component to never get deactivated (assuming that autodemarcation is off and setcomplete is never called) and thus never destroyed.

WORKAROUND:
When the property (.timeout) is set manually from Jag manager, everything works properly.



CR:194846
CR Number:   194846
Product Name:   PB Enterprise
Product Component:   Jaguar Integration
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.00 RC2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
25 Feb 2004 EOL'd version. Not to be Fixed.
Description
Deploying a PowerBuilder component to Jaguar:
Deploying a component causes any currently active components of the same type to be terminated. Deactivate and destroy events do not appear to be executed when this happens.



CR:194850
CR Number:   194850
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
Registering shared objects in the same thread that has a database connection may cause PB to crash



CR:194887
CR Number:   194887
Product Name:   PB Enterprise
Product Component:   Machine Code Deployment
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
Calling HALT in window open event of an application's first window will not halt the application at this point - it still executes the code in Application open event which comes after the call to open the first window. Only happens in machine code compiled exe. Simple w/a is post a user event from window open event and put the HALT call there. HALT CLOSE also works fine.
Workaround Description
 Post a user event from window open event and put the HALT call in the posted event (ie allow app open event to finish before calling HALT)
Use HALT CLOSE



CR:194911
CR Number:   194911
Product Name:   PB Enterprise
Product Component:   DB Oracle
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.5.00 607 27 Apr 1999 Fixed
Description
Using the Oracle OR8 and O84 drivers, you cannot run a stored procedure by referring to its public synonym unless you qualify the procdure with "PUBLIC".



CR:194944
CR Number:   194944
Product Name:   PB Enterprise
Product Component:   DB MS SQLServer
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.00 EBF1 8011 15 Nov 2000 Fixed
Description
PB Catalog tables cannot be found or created when MS SQL is enforcing ANSI conventions regarding the use of quotation marks, upon connection.



CR:194945
CR Number:   194945
Product Name:   PB Enterprise
Product Component:   DB Oracle
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.x Catalina 1039 04 Jun 1999 Fixed
Description
Multiple datawindow retrieves for SP datawindows using the OR8 and O84 drivers cause cursors to be left open on the server if SQLCache DBParms > 0.



CR:194946
CR Number:   194946
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.5.00 1015 18 Jun 1999 Fixed
Description
Regression: 6.5 Crosstab datawindows using 4 times memory of 5.0.04 crosstabs



CR:195013
CR Number:   195013
Product Name:   PB Enterprise
Product Component:   DB Oracle
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.5.00 1208 10 Aug 2000 Fixed
Description
PB 6.5 does not support Oracle 8 Password expiration.



CR:195017
CR Number:   195017
Product Name:   PB Enterprise
Product Component:   DB ODBC
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.00 RC1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.x Catalina 1046 07 May 1999 Fixed
Description
When using embedded sql and calling a sp when
tracing is turned on, the output parm doesn't work and pb crashes with
a referenced memory exception when closing out of pb.

Problem happens using Sybase Adaptive Server 6.01.

Works ok when tracing is not turned on. No crashes and output parm returns
result. No problems using rpc.



CR:195038
CR Number:   195038
Product Name:   PB Enterprise
Product Component:   DW Edit Mask
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.x Catalina 10098 23 Jul 2001 Fixed
Description
Entering data into a data edit mask control where the date does not fit into the control may cause a GPF in POINT.DLL.



CR:195057
CR Number:   195057
Product Name:   PB Enterprise
Product Component:   DB Oracle
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.x Catalina 1049 13 May 1999 Fixed
Description
Using Oracle O84 driver. If you perform an EXECUTE IMMEDIATE on a SQL strring that contains "->" embedded in a comment, a GPF will occur.



CR:195100
CR Number:   195100
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Open
OS:   Microsoft Windows 95
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0 Beta 2 2042
9.0 Beta 2 2042
Description
New Feature Request:
Customer wants to print multiple datawindows to the same print file while retaining the print attributes from the individual dtawindows.



CR:195102
CR Number:   195102
Product Name:   PB Enterprise
Product Component:   Edit Mask
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.5.00 17 Aug 1999 Fixed
Description
Datetime field with an editmask of mm/dd/yyyy allows a year of 0000 to be valid when a user inputs month and day and does not input in a year but tabs off. When this happened in PB 5.0.04 the date was simply recognized as Null. This would seem correct as this is an invalid year. When this is tested using PB 6.5 build 600 the year is 0000 but when this same app is tested with PB 7.0 the year is changes to 1900.

Additionally in PB 7.0 the same thing is happening on a Date field with the same editmask of mm/dd/yyyy. In all other versions of PB tested the Date field would see this as Null.



CR:195136
CR Number:   195136
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
26 Sep 2000 Fixed
Description
If you use SetTrans to assign transaction info to a daatwindow, subsequent retrieve leave the connection open.
Workaround Description
 Use SetTransObject() instead of SetTrans().



CR:195186
CR Number:   195186
Product Name:   PB Enterprise
Product Component:   Machine Code Deployment
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
Machine code exe is crashing on a retrieve. It appears
that a retrieval argument is probably not initialized and is causing the crash.
In a odbc trace log file, the error was S1010 Function Sequence Error.

Works ok in pcode and in development.

The problem is in the of_detail_list function in the cvuo_lv_container.
Crashes in exe:
ll_row_count = lds_level1.Retrieve(ast_keys.location, ast_keys.work_id, &
ast_keys.hardware_id, ast_keys.hardware_type, ast_keys.cost_centre )

Works in exe:
ll_row_count = lds_level1.Retrieve(ast_keys.location, ast_keys.work_id, &
integer(ast_keys.hardware_id), ast_keys.hardware_type, ast_keys.cost_centre )



CR:195215
CR Number:   195215
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15 Apr 1999 Duplicate
Description
datawindow.update (true,true) then dw.setfocus lead to change the current row



CR:195237
CR Number:   195237
Product Name:   PB Enterprise
Product Component:   UO Painter
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.x Catalina 1046 07 Jul 1999 Fixed
Description
PB7.0 :
Pressing <Ctrl><Shift> and l or r or c key in the script of a custom non-visible user-object painter
crashes PB7.0 .
The same key combination in the script of other type of objects do not immediately crash, but a crash can occur
afterwards.





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

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。
+-------------------------------------华丽的分割线-------------------------------------------------------------------------