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

 

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

如有问题,请联系我!

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

 

CR:204509
CR Number:   204509
Product Name:   PB Enterprise
Product Component:   Language - 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
PB connects to WebServer running a CGI script. When using PostURL() the function returns back 'Access Denied'. Using plain HTML post method works. If you make the same call using HTTPRequestBuilder.exe it works as well.

Workaround:
It is possible to use the POST method using the Powersocket 2.1 library which is not FREEWARE.
This has to be purchased seperately.



CR:204512
CR Number:   204512
Product Name:   PB Enterprise
Product Component:   Printing
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
07 Sep 1999 Not a Bug
Description
Regression in PB6.5.1 and PB7.

After a user has selected a printer in the PrintSetUp function, then a different printer
can no longer be selected dynamically in script using either the method described in
TechDoc 47627 or through an external utility.



CR:204621
CR Number:   204621
Product Name:   PB Enterprise
Product Component:   DW Graph
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   7.0.00 RC1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.5.00 1096 26 Apr 2000 Fixed
Description
2 Series line graph, fails to draw line if both don't have the same cat values.
Verified fixed in 6.5.1 build 1127, and 7.0.1 build 7021



CR:204667
CR Number:   204667
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)
31 Oct 2002 Fixed
Description
A datawindow has one decimal column. This datawindow is used in another datawindow as a drop down datawindow.
Click on the drop down and choose a value such as 10.001. Press the tabulation key then, if a 10.000 value exists in the drop down datawindow buffer, then the main datawindow show no longer 10.001 BUT 10.000. If the 10.000 does not exists in the drop down datawindow buffer then all works fine.



CR:204702
CR Number:   204702
Product Name:   PB Enterprise
Product Component:   OLE - Active X - OCX
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 Fixed
Description
Redraw problem with an OCX after minimizing the window or after any dialog is put up in front of the OCX. Sometimes the OCX background will blank out (white) and users cannot see the data until they resize the entire sheet. Problem did not occur using 6.5, but it happens now with 7.0. The problem occurs only when the OCX is compiled using Visual C++ version 6.0, not when Visual C++ version 5.0 is used.



CR:204779
CR Number:   204779
Product Name:   PB Enterprise
Product Component:   Window - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.00 7014 21 Dec 2000 Not reproducible with latest version of the product available as of Resolution Date
Description
6.5 and 7.0 performance of iterations of window opens (with no controls on the window) are visibly and measurably slower in 7.0 than in 6.5 in the EXECUTABLE. Development environment speeds are similar for opening windows. Related to several other performance issues including CR202771.
12/29/99 Update:
Fixed in pbvm70.dll build 7014 (Post 7.0.1 Maintenance Release)
This was a problem where PowerBuilder was not handling windows with no icons specified. In 6.5, the system translated a window icon to application! by default (if no Icon was specified). In 7.0, there was no default (it was taken away) and this was no longer being translated because of conflicts between the bitmap named Application! and the icon named Application!.

In 7.0 we now have an
icon called AppIcon!, which does the same as Application! and no icon specified is translated to this icon. AppIcon! is selectable from the list in
the window painter and no icon is now translated to this solving both this problem and the name conflict issue. The performance degradation was caused because we were searching the library list for icon of the name "".



CR:204847
CR Number:   204847
Product Name:   PB Enterprise
Product Component:   Library Painter
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8004 28 Jan 2000 Fixed
Description
Regression. In PB 7.0 doing a search of selected objects in the library painter fails to search scripts that strart with a blank line.



CR:204883
CR Number:   204883
Product Name:   PB Enterprise
Product Component:   WT - Web DataWindow DTC
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16 Mar 2004 EOL'd version. Not to be Fixed.
Description
The PowerSite object model, and the WebDW DTC only allow you to associate a single Jaguar server/port for the WebDW component, such as:
jagConn = new PSJaguarConnection("localhost:9000", "jagadmin", "", "DataWindow/HTMLGenerator", false);

If you set up a cluster of Jaguar servers to take advantage of high availability etc. then you will run into issues if the Jaguar server on port 9000 goes down.

WorkAround: Write your own script instead that references the PowerDynamo object model with:
java.CreateComponent("mycomp","iiop://localhost:9000;iiop://localhost:10000;...")
Workaround Description
 Do not use the WebDW DTC -- write your own script and reference the PowerDynamo object model instead of the PowerSite object model



CR:204888
CR Number:   204888
Product Name:   PB Enterprise
Product Component:   DW Painter
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
20 Apr 2000 Fixed
Description
Here, a DataWindow is created via a stored procedure.
Column Specifications allows you to INSERT ROW and DELETE ROW by rmb clicking in the Column Specifications view, but there is no ADD or APPEND ROW option as in previous versions. Using the ADD option would put the new item at the bottom. Right now the only way you can add a new row is to TAB. Inserting a row inserts one above the row where the cursor is currently at.



CR:204897
CR Number:   204897
Product Name:   PB Enterprise
Product Component:   Documentation
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
03 Sep 1999 Fixed
Description
CR149163 states that "Due to all the problems with the query mode and UNIONS we now disallow query mode if the select clause has a UNION statement. We don't parse the select if it has UNION (too complicated) and we have no idea where the ''WHERE'' should go."

But our "Datawindow Programmer's Guide" in Chapter 3 section "Providing query ability to users" :
"Limitations
You cannot use query mode in a DataWindow object whose data source you have modified syntactically (as opposed to graphically) and that contains the UNION keyword or nested SELECT statements"

And this is not correct according to CR149163. The "Limitations" should be replaced by :
"Limitations
You cannot use query mode in a DataWindow object whose data source that contains the UNION keyword or nested SELECT statements"



CR:204899
CR Number:   204899
Product Name:   PB Enterprise
Product Component:   Library Painter
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.00 7018 29 Nov 1999 Fixed
Description
7.0 regression: Regening selected objects in library painter, updates the modification date.
Fixed in 7.0 build 7021 (MJD EBF)



CR:204915
CR Number:   204915
Product Name:   PB Enterprise
Product Component:   Window Painter
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
NT 4.0 only - MLE TabStop has no affect if set in painter.

Workaround: Set TabStop in script: mle_1.TabStop[1] = 10
mle_1.TabStop[2] = 15
etc.

DO NOT set any tabs in the painter.



CR:204939
CR Number:   204939
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 27 Mar 2000 Fixed
Description
N-Up datawindow goes blank when clicked at runtime



CR:204994
CR Number:   204994
Product Name:   PB Enterprise
Product Component:   Printing
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
18 Dec 2000 Fixed
Description
7.0 File/Print Setup in development and the PrintSetup() dialog in runtime should be made wider (the listbox containing the list of printers) and have a horizontal scrollbar so users can see all the printers. Long printer names often get chopped off. When you have more than one printer defined, it's annoying to go back and forth in the dialog just to see if you have the right printer.



CR:205036
CR Number:   205036
Product Name:   PB Enterprise
Product Component:   Shared Objects
Status:   Closed
OS:   Microsoft Windows 98
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
This is a regression from PB6.0.00.

The shared datastores/datawindows become unlinked when a GetFullState() is done on a non-shared ds/dw object and a SetFullState() done on one shared ds/dw object.

The latter should cause the synchronization of all the shared ds/dw objects. This synchronization feature is
broken.
Workaround Description
 The partial workaround if suitable for the ct is to a)Stop the sharing of data before the SetFullState() function
b)Reference the primary datastore/datawindow when doing SetFullState() instead of any secondary one so that
repeat assignment call(s) to



CR:205046
CR Number:   205046
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.5.00 28 Mar 2000 Fixed
Description
6.5.1 regression: In dw clicked event, row argument sometimes is wrong.



CR:205097
CR Number:   205097
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 1096 28 Mar 2000 Fixed
Description
After calling a combination of several modify() function PB causes a gpf / dr. watson.
This could be related to creating computed fields associated to other computed fields with a modifiy function.



CR:205128
CR Number:   205128
Product Name:   PB Enterprise
Product Component:   Window Painter
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   7.x Catalina
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.2 8046 29 Jun 2000 Fixed
Description
7.0 Regression: You cannot alter the 'text' property of tabpages so that the text appears on multiple lines. Both PB5 and PB6 gave the user a multiline edit on the propery sheet so that the user could do this. PB7 only provides a single line text field for this property so entering multiple lines is not possible.



CR:205184
CR Number:   205184
Product Name:   PB Enterprise
Product Component:   DB Painter
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.00 06 Oct 1999 Fixed
Description
If you create a ASA DB with the option "Emulate ASE" then all primary keys
and custom stored procedures are not displayed in the Database Painter.
This is related to the "Case sensitivity for all names and values" propertie if you create
a ASA DB in Sybase Central



CR:205207
CR Number:   205207
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   Microsoft Windows 98
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
SetFullState copies the blob correctly to the datastore/datawindow.
However if the dataobject property of the target datastore/datawindow is verified, the value is missing/ not available.
The workaround is to assign the dataobject property to the datastore/datawindow before calling SetFullState.
Workaround Description
 Assign the dataobject property to the datastore/datawindow before calling SetFullState.
Script:
ids_test.GetFullState(lblb_test) // for ds
dw_test.Dataobject = ids_test.dataobject // for dw on window
dw_test.SetFullState(lblb_test)



CR:205242
CR Number:   205242
Product Name:   PB Enterprise
Product Component:   Window Painter
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
07 Sep 1999 Duplicate
Description
Using PB 6.0, you could set the multiline property of a tab page, and then initialize the text on multiple lines within the painter. In 7.0, you can set the multiline property, but the entry for the Text property does not allow you to enter text on multiple lines. Workaround: initialize the text in the constructor event of the tab control. (Use "~r~n" for the newline within the string.)

DUPLICATE BUG: See 205128 for current information.



CR:205249
CR Number:   205249
Product Name:   PB Enterprise
Product Component:   WT - Web DataWindow DTC
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
26 Apr 2001 Fixed
Description
If you have a datawindow with a DateTime retrieval argument defined, you cannot use the WebDW DTC to specify a constant value for it. If you choose Constant as the Value Type and specify a datetime Value (such as 04/12/1999 03:02:01), this information is not saved by the DTC.
The Value Type is cleared, and only the last couple of positions of the Value are saved.

WORKAROUND: use a script variable to pass the value instead.
Workaround Description
 Use a script variable to store the value instead.



CR:205254
CR Number:   205254
Product Name:   PB Enterprise
Product Component:   UO Painter
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.00 RC2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11 Aug 2000 Fixed
Description
In the UO painter, the Help item is disabled on the popup menu for the Property sheet.



CR:205273
CR Number:   205273
Product Name:   PB Enterprise
Product Component:   Window Painter
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
02 Oct 2000 Fixed
Description
7.0.1ebf and 7.0.2 Regression. The Tab and Enter keys no longer work in the Edit Find/Replace text dialog used in various script painters.

There were several bugs in 7.0 in the dialog.
CR204215-dialog is modal (fixed 7.0 7015). Users could not "type behind" dialog to fix script like most replace dialogs. CR204215 fixed the modality but broke the ability to use the tab keys and hotkeys in the dialog.
CR205273- Broken tab and hotkeys in the dialog. Fixed in 8.0 but not in the 7.0 ebf line yet as of 2/9/2000.



CR:205288
CR Number:   205288
Product Name:   PB Enterprise
Product Component:   System Runtime Functions
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.04
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
The problem described in this CR is related to PB 32 bit versions running on Windows95 32 bit operating system.
The function DirList() works correctly for pattern searches which have a file extension e.g. *.txt, *.dat
Workaround Description
 If suitable for customer: a)Suppose filename is fixed length 8 chars with no extension.Setting the file specification to '\????????' will display those filenames matching 8 chars only. b)Upgrade operating system to MS Windows98 or NT.



CR:205309
CR Number:   205309
Product Name:   PB Enterprise
Product Component:   DB DirectConnect
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.5.00 1091 31 Oct 2002 Fixed
Description
Execution of Sybase-provided RPC syb_pem fails with GPF



CR:205338
CR Number:   205338
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 28 Mar 2000 Fixed
Description
Using Autosize Height on a Freeform datawindow, after doing an InsertRow and a SetItem with data that causes the height of the column to change, in 6.5 the display of the datawindow refreshed to show the complete data. Using 6.5.1, this no longer occurs. Behavior in 7.0 is the same as in 6.5.1.

Workaround is to add SetRedraw(true) and the display is then refreshed, but this was not necessary using 6.5.



CR:205404
CR Number:   205404
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.x Catalina 28 Mar 2000 Fixed
Description
7.0 Regression:
DataWindow control on a window. If there is anything in the OTHER event, even a comment, after a few times of double-clicking on the dw, the page fault will occur (using WIN95) @PBVM70.DLL@0137:112cb9f8 or an access violation will occur (using NT): The instruction at 0x112cb9f8 referenced memory at 0x00000010 the memory could not be "read"..
This crash occurs if running from development or runtime.



CR:205423
CR Number:   205423
Product Name:   PB Enterprise
Product Component:   Windu/U
Status:   Closed
OS:   Solaris 2.6
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
The fileopen and fileclose PowerScript functions are producing a memory leak. The leak is very small (approx 200k per 5000 iterations). Then after 30 or 40 thousand iterations, the leak increases to between 2 and 3 MB per 5000 iterations. After 64863 iterations PowerBuilder will core dump.

I also migrated my altered test case back onto NT, where it is still running happily after over 2 million iterations with no sign of a memory leak.



CR:205511
CR Number:   205511
Product Name:   PB Enterprise
Product Component:   DW Edit Mask
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
Datawindow editmask DATE YY returns NULL for YY=00 (as in 2000)
This problem happens with Powerbuilder 5.0.04 EBF 2, 6.5 buld 1077 and 7.01 build 7013
Workaround Description
 Use another edit mask or migrate to PB 6.5 buld 1077 and 7.01 build 7013



CR:205512
CR Number:   205512
Product Name:   PB Enterprise
Product Component:   DW Edit Mask
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
Datawindow editmask DATETIME YY returns NULL for YY=00 (as in 2000)
This problem exists for PB 5.0.04 Ebf2
This problem is fixed in PB 6.5 buld 1077 and 7.01 build 7013
Workaround Description
 Use another Edit Mask or migrate to PB 6.5 buld 1077 and/or 7.01 build 7013



CR:205531
CR Number:   205531
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)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
This is a regression from PB6.5 GA.

Function GetFullState is not releasing memory after application is terminated on 2 tier application i.e. PB with ASA.



CR:205678
CR Number:   205678
Product Name:   PB Enterprise
Product Component:   DW - Runtime
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
WebDW cannot handle a DateTime retrieval argument.
In the DW painter, you can successfully retrieve rows using a datetime value such as: 04/12/1999 03:02:01

However, when you try to use the dw object in a WebDW component, no rows are returned.



CR:205724
CR Number:   205724
Product Name:   PB Enterprise
Product Component:   DB OLE DB
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.00 7018 08 Nov 1999 Fixed
Description
Unable to set the WSID property in an OLE DB Connection to MS SQL Server7



CR:205751
CR Number:   205751
Product Name:   PB Enterprise
Product Component:   MAPI
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
Using a sample PB mapi application to attach and send a file - the attachment and the text are merged together when the e-mail is recieved in Outlook or Exchange.



CR:205811
CR Number:   205811
Product Name:   PB Enterprise
Product Component:   DataBase Administrator
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8550 07 Oct 1999 Fixed
Description
Sybase server 11.92.1, setsqlselect then retrieve causes GPF when the network db connection is lost.

use the latest OC on 11.1.1 will solve the problem
Workaround Description
 Use the latest OC on 11.1.1 or use OC 12.0
go to support.sybase.com--->sodtware distribution to get latest OC on 11.1.1



CR:205862
CR Number:   205862
Product Name:   PB Enterprise
Product Component:   DW Synchronization
Status:   Closed
OS:   Microsoft Windows 98
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
The ModifiedCount method is wrong for a datastore interaction with datawindow when :
-datastore has inserted rows
-saved inserted rows to database table
-then data modification done on any row in the datawindow
-then GetChanges and SetChanges done.

The problem described in this CR does not happen for either of the following:
-if there have been no new inserted saved rows affecting the datastore/datawindow.
-for datawindow to another datawindow

Per Development:
This is not a bug.
Workaround Description
 -Do 'GetChanges for dw' then 'SetChanges to ds' twice, then the buffers are synchronized.
OR
-When changes are applied to database table, do a fresh Retrieve() for the ds.



CR:205956
CR Number:   205956
Product Name:   PB Enterprise
Product Component:   DW Painter
Status:   Closed
OS:   Microsoft Windows 98
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
20 Mar 2000 Duplicate
Description
When computed column(s) are defined on the datasource SQL statement for a new crosstab datawindow. The problem is that the computed column does not appear in the crosstab definition 'Source Data' box.
Workaround Description
 Modify the SQL Select statement for the saved crosstab dw e.g. add a WHERE clause or add another column etc.
Save the statement and return to dw painter.
Display the crosstab definition dialog and then the computed column appears in the source data box.



CR:205963
CR Number:   205963
Product Name:   PB Enterprise
Product Component:   Edit Mask
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
Documentation:
In the documentation we state that if [time] is used as a display format for the time data type, PowerBuilder will use the display format for time that is specified in the Microsoft Windows Control Panel. In fact, all that is read from there is the separator character.
See CR 156337 for details that led to this change request.



CR:205992
CR Number:   205992
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)
20 Dec 2000 Not a Bug
Description
After displaying HP8000 printsetup dialog window, pointer goes missing when over command buttons



CR:206028
CR Number:   206028
Product Name:   PB Enterprise
Product Component:   OLE - Active X - OCX
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
OLE object passed by reference as parameter to an oleobject method lead to GPF.The oleobject passed as parameter is a PB COM generated Object.



CR:206033
CR Number:   206033
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)
11 Jan 2000 Not reproducible with latest version of the product available as of Resolution Date
Description
dd/mm/yyyy editmask has different behaviour then in PB 4 and PB 5. Days will not be entered correctly. If you've 00/00/1999 try to type in 30.08.1999 you can only enter the "3" (03/00/1999).

workaround:
type first the month and then the days



CR:206038
CR Number:   206038
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
06 Jul 2004 Fixed
Description
7.0 Regression: SetText of a string with commas to a dddw column ignores commas.



CR:206045
CR Number:   206045
Product Name:   PB Enterprise
Product Component:   OLE - Active X - OCX
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
06 Oct 1999 Not a Bug
Description
Ole mailmerge.field.addset stopped working.
When you right mouse click in the word doc,
you should see the following:
{set str2 "TEST STRING with []!"}{set str1 "TEST STRING with ()!}

In pb 7.0.01 you just see:
{set str2 " "}{set str1 " " }


Worked ok in PB 7.0 (build 5031) and pb 5.0.04.



CR:206117
CR Number:   206117
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0 Beta 4 5017 23 Mar 2001 Fixed
Description
PB Version and Build: 7.0.5013 (GA), 7.01.6012 (MR), 7.01.7015

Datawindow Painter will crash with Crosstab datawindow when adjusting band size if 'Preview' view & 'Design' views are both open and 2 rows have been selected in the crosstab definition.

Build 7015 -> 0x10695e95 referenced memory at 0x00000004 - Memory could not be read
Build 6012 -> 0x10695d15 referenced memory at 0x00000004 - Memory could not be read

Workaround is to close 'Preview' view before moving any band in the 'Design' view

Engineering note: DW Runtime problem
I can recreate the GPF using the following syntax at runtime:
dw_1.modify("datawindow.header[2].height='132'")
Workaround Description
 Remember to close 'Preview' view before moving any band in the 'Design' view



CR:206119
CR Number:   206119
Product Name:   PB Enterprise
Product Component:   P-Code Deployment
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Third Party Problem
Description
For PB6.5.1 deployment to 16 bit Windows operating system (e.g. Win3.11, Win95), the problem occurs for String to Double to String conversion when comma is the decimal separator.
The fractional part of the value is truncated e.g 100,25 becomes 100 ;
Workaround Description
 -Convert the text value to datatype decimal and then convert from decimal to double;
-If converting true datatype double to string, result is OK e.g. ldouble_value = 147.82 ; ls_double_to_string = string(ldouble_value)



CR:206140
CR Number:   206140
Product Name:   PB Enterprise
Product Component:   DW Painter
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
08 Jun 2000 Fixed
Description
Create a datawindow with stored procedure datasource (which requires retrieval arg(s)), preview, supply the args, save the dw. Now create a Quick Select datasource datawindow against any table without any retrieval args. Preview it and you are prompted for the retrieval arguments for the previous sp dw. Only happens with a quick select dw (not query or sql select data source) created after creating a stored procedure dw.
Workaround Description
 1) Use SQL Select data source
2) Export the dw, open srd file in file editor, find the line

arguments=(("customer_id", number))

or similar. Remove it and import again.



CR:206208
CR Number:   206208
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
rounding errors on numeric fields with editmask #,##0.00 format.
For example Number 1,005 will be incorrectly rounded to 1.00 instead of 1.01 by computed field with #,##0.00 mask.

Workaround: Using Round() function on computed field works ok.
exapmle: round(column_name) instead of only column_name in the computed field



CR:206212
CR Number:   206212
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
While building a dw based on a ORACLE stored procedure having an array as an input parameter PowerBuilder is not able to finish the creation. The array input parameter is not currently supported for a sp based datawindow. Customers view this as an enhancement.
Current Error-Message: Error 999 (rc -1) : Invalid stored procedure parameter type of 'COMPOSITE' on '........'.
Workaround Description
 Use other SP technique: RPC and move data into dw in code.
For detailed instructions see TechDoc 44450



CR:206221
CR Number:   206221
Product Name:   PB Enterprise
Product Component:   WT - Editor - HTML
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   8.0 RC
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5011 18 Apr 2001 Fixed
Description
The existance of an unbalanced quotation mark in a script causes the PowerSite editor to add extra ending HTML tags such as </BODY> and </HTML>. This is occurring with version 7.1.297 of PowerSite with the additional PowerSite patch named 710298.zip. This behaviour is occuring in both client side or server side scripts such as alert('hello) or psdocument.write('hello). In a more complicated page from a customer he was seeing about 40 additional closing tags being added.



CR:206246
CR Number:   206246
Product Name:   PB Enterprise
Product Component:   MTS Integration
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.2 8030 31 Oct 2002 Fixed
Description
COM objects crash frequently bringing down ASP application when used with IIS and MTS. Crashes
using the Web Application Stress Tool after only 15 connections. The following error appears
in the event viewer for Transaction Server:

Failed on creation from object context: CoCreateInstance (Package: IIS-{Default Web Site//Root/41051303Ssite}) (ProgId: ie.uo_testcrash1.1) (CLSID: {4C9410D3-977D-11D3-90F9-00A0C9ED4BAC}) (Microsoft Transaction Server Internals Information: File: d:\viper\src\runtime\context\ccontext.cpp, Line: 1292)

When trying to call the com object thru asp in a browser, the following error message also appeared:
error 'ASP 0115'

Unexpected error

/41051303Ssite/testcrash1.asp

A trappable error occurred in an external object. The script cannot continue running. -2147418113 007~ASP 0115~Unexpected
error~A trappable error occurred in an external object. The script cannot continue running. Server objectCreate Object
Successful
424 Object required Microsoft VBScript runtime errorof_testcrash1:
Workaround Description
 Able to successfully make 150 connections when registered the com dll thru the
run dialog box and the "run in separate memory space" was checked. If the com dll
was registered thru dos or if "run in separate memory space" wasn't checked than
mts failed



CR:206257
CR Number:   206257
Product Name:   PB Enterprise
Product Component:   Edit Mask
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.00 EBF1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.5.00 1095 06 Jul 2000 Fixed
Description
PB 7.0.01/7.5 Regression--on a datetime column with edit mask mm/dd/yyyy or mm/dd/yyyy hh:mm:ss if you enter a date or retireve it from the database and then zero it out, the value defaults to 01/01/1900.

This happens with both external and non-external datawindows. Date colums with an editmask of mm/dd/yyyy do not exhibit problem.



CR:206309
CR Number:   206309
Product Name:   PB Enterprise
Product Component:   Jaguar Integration
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.00 EBF1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.2 8027 25 Feb 2004 Fixed
Description
Jaguar server GPFs at startup if a PB Component is used for custom authentication.



CR:206310
CR Number:   206310
Product Name:   PB Enterprise
Product Component:   Jaguar Integration
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.00 EBF1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
06 Apr 2001 Fixed
Description
Getting IDL Compiler error when deploying a PB Component that uses CTSSecurity package. This component implements a Custom Authentication server.

** The error message actually indicates a generic problem that will be encountered anytime a user will try to implement an existing Jaguar interface. SO this issue needs to be addressed ASAP. **



CR:206321
CR Number:   206321
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 you use a user object inherited from a datastore, neither the dberorr event or error events fire when you trigger a retrieve error that is caught by PowerBuilder.



CR:206343
CR Number:   206343
Product Name:   PB Enterprise
Product Component:   DW Synchronization
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.00 28 Dec 2001 Fixed
Description
Update of datastore after SetChanges to an empty datastore fails due to incorrect buffers.
Verified fixed in 7.0 MJD release (build 7021)



CR:206354
CR Number:   206354
Product Name:   PB Enterprise
Product Component:   WT - Web DataWindow DTC
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
28 Feb 2001 Fixed
Description
Repro
Add a Web DW DTC to a page
Select a pbl and dw
Switch to the Jaguar tab. Select the HTML generator
Close the DTC
Notice that the name of the DTC on the page is Object1 instead of htmlDW
Notice that the connection information is empty.
Notice that if the DTC had any page params needed if it had a retrieval argument that the information is empty.


Delete the DTC and readd it
Select a pbl and dw
Before switching to any other tabs attempt to close it and notice that it does not let you.

Notice that the difference here is that the Jaguar tab was selected previously. This is an inconsistency.



CR:206376
CR Number:   206376
Product Name:   PB Enterprise
Product Component:   DW Synchronization
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
Createfrom(ADOResultSet) drops the last row. A blank row appears.
Works ok with resultset.

WorkAround:

Add a new record before calling the CreatFrom function:

loo_ADOrecordset.Movelast()
loo_ADOrecordset.AddNew()



CR:206382
CR Number:   206382
Product Name:   PB Enterprise
Product Component:   DW Plugin
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 you right mouse click on a dw plugin, and you
select 'save rows as' option and save the psr report to another psr, the
file that is created is distorted once you view it thru a browser.

Problem happens in Netscape and with Internet Explorer.



CR:206418
CR Number:   206418
Product Name:   PB Enterprise
Product Component:   Jaguar Integration
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15 Feb 2000 Not a Bug
7.0.3 8014 22 Jun 2000 Fixed
Description
sqlErrText & sqlDbCode transaction properties not properly set when connecting with an invalid user to any db from a jaguar component (with or without any connection cache defined)



CR:206423
CR Number:   206423
Product Name:   PB Enterprise
Product Component:   Library Painter
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
03 Jan 2001 Not a Bug
Description
PB7 should automatically connect to the selected source control system if PB Native is used.



CR:206500
CR Number:   206500
Product Name:   PB Enterprise
Product Component:   DB ODBC
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
25 Aug 2005 Fixed
Description
Using ODBC and SQLCache. If SQLCache is set to a small number and update statements with variables are repeated, SQLSTATE 07001 will occur on a repeated update.
Workaround Description
 Set SQLCache to a large number.



CR:206510
CR Number:   206510
Product Name:   PB Enterprise
Product Component:   DB Other
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
18 Apr 2000 Not a Bug
Description
When you connect to a database using one of the following
drivers:
ODBC (Microsoft 6.5 sqlsrv32.dll 3.60.0319)
SYC (OpenClient 11.1.1)
MSS

and autocommit=false, running the following script will execute incorrect
return codes:

ls_string = "Begin Transaction"
execute immediate :ls_string using sqlca;
dw_1.update()
commit using sqlca;

The update() returns a successful return code. The sqlca.sqlcode and sqlca.sqldbcode
return 0 after the execute statement and commit statement although the database
does not get updated.



CR:206515
CR Number:   206515
Product Name:   PB Enterprise
Product Component:   DB Other
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15 Aug 2000 Fixed
Description
Connect to ms sql server 6.5 with autocommit=true and
a dw gets updated, when the following script is run the db doesn't get updated
nor do the return codes from update(), sqlca.sqlcode or sqlca.sqldbcode
indicate that.

ls_string = "Begin Transaction"
execute immediate :ls_string using sqlca;
dw_1.update()
commit using sqlca;

Using sqlsrv32.dll version 3.60.0319. Works ok with syc, mss and ASA.



CR:206560
CR Number:   206560
Product Name:   PB Enterprise
Product Component:   DW Plugin
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.5.1 1248 25 Feb 2004 Fixed
Description
Netscape browser crashes when closing browser with the following error:
The instruction at "0x115cc8b0" referenced memory at "0x115cc8b0". The memory could not be read.
Works ok with win95 and win98. Crash happens in ie 4.0 and 5.0 and netscape 4.06 and 4.5 on nt.



CR:206567
CR Number:   206567
Product Name:   PB Enterprise
Product Component:   OLE - Active X - OCX
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
04 Jan 2001 Fixed
Description
Setting a property for an OCX ( GLG.OCX ) leads to GPF



CR:206615
CR Number:   206615
Product Name:   PB Enterprise
Product Component:   DW Synchronization
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
30 Dec 2001 Not a Bug
Description
Updating a ds/dw after a setfullstate or setchanges, does not empty delete buffer.
Not a bug. If dw/ds is populated with a blob and updated, the delete buffer reset is delayed until a subsequent GetChanges is applied.



CR:206655
CR Number:   206655
Product Name:   PB Enterprise
Product Component:   SQL Painter
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
24 Jun 2003 Fixed
Description
Painting the following SQL Statement on Microsoft SLQ Server 6 (7) via the Native driver (ODBC as well) results in the Errormessage in the SQL painter: "Select Error: Query contains an outer-join request that is not permitted"
The painted syntax looks as follows:
SELECT t.tid, t.somecols, u.uuid, u.somecols, v.vid, v.somecols, w.wid, w.somecols
FROM t, u, v, w
WHERE ( t.tid *= u.tid) and
( u.uuid *= v.uuid) and
( t.tid *= w.tid)
In the trace the error is: Error 301 (rc -1) : Query contains an outer-join request that is not permitted.

Workaround:
Convert to syntax mode and replace the syntax with:
SELECT t.tid, t.somecols, u.uuid, u.somecols, v.vid, v.somecols, w.wid,w.somecols
FROM {oj {oj t LEFT OUTER JOIN u ON t.tid = u.tid
LEFT OUTER JOIN v ON u.uuid = v.uuid}
LEFT OUTER JOIN w ON t.tid = w.tid}

Per Development:
Not to be fixed. Easy workaround.
A portable datawindow that behaves identically against both ASA 6.x and SQL Server 7.0 can be easily created if the customer converts to syntax mode and uses the following select statement that is compatible with ASA 6.0, SQL Server 7.0 and DB2/CS:
SELECT t.tid, t.somecols, u.uuid, u.somecols, v.vid, v.somecols, w.wid, w.somecols
FROM {oj t LEFT OUTER JOIN u ON t.tid = u.tid
LEFT OUTER JOIN v ON u.uuid = v.uuid
LEFT OUTER JOIN w ON t.tid = w.tid}
Enhancing the SQL Painter to generate this SQL graphically won't happen anytime soon, so use syntax mode in datawindow painter. This works and lets the customer create a datawindow portable across several DBMSs.
Workaround Description
 Cobb 11/17/99 Build portable dw that behaves identically vs both ASA 6.x and SQL Server 7.0.
SELECT ... FROM {oj t LEFT OUTER JOIN u ON t.tid = u.tid
LEFT OUTER JOIN v ON u.uuid = v.uuid
LEFT OUTER JOIN w ON t.tid = w.tid}



CR:206669
CR Number:   206669
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
Doing a <dw>.saveas() to the clipboard followid by a <dw>.ImportClipBoard() may cause a GPF if an Office 2000 program has the clipboard viewer window open.
Workaround Description
 None



CR:206674
CR Number:   206674
Product Name:   PB Enterprise
Product Component:   Script Painter
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
28 Sep 1999 Not a Bug
Description
According to the documentation this is supposed to work with global variables:

Class Variables
Check to include global and instance variables that are in scope.



CR:206729
CR Number:   206729
Product Name:   PB Enterprise
Product Component:   P-Code Exe Creation
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
PB crashes in the project painter when creating a pcode or mcode
executable. Getting a reference memory exception error.

Happens only when creating an exe and no pbd's or dll's are checked off.



CR:206801
CR Number:   206801
Product Name:   PB Enterprise
Product Component:   DB Informix
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.00 7018? 04 Oct 1999 Fixed
Description
PowerBuilder 7 does not display Informix synonyms (public or private) in table lists (DB painter or DW painter) or synonym lists.
Workaround Description
 Create datawindows in syntax mode.



CR:206803
CR Number:   206803
Product Name:   PB Enterprise
Product Component:   DB Oracle
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
PowerBuilder database drivers for Oracle 8 (OR8 and O84) do not support schema/object names that begin with a numeric character.
Workaround Description
 None



CR:206805
CR Number:   206805
Product Name:   PB Enterprise
Product Component:   Language - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16 Nov 1999 Not a Bug
Description
Very similar to CR 170917. Dynamic call to protected function causes a runtime error if the function call is made from the script of a userobject on the window which is descended from the window where the protected function is declared. CR 170917 fixed this problem when the dynamic function call was made from a "regular" control on the window (eg. commandbutton) but the problem still exists in this case.

From Development:
In PB5, we had a major hole in the product. This hole was that we allowed people to make function calls using the dynamic keyword all over the place in terms of protected and private functions. There was not any checking done at all in PB5 to see what the accessibility of the function being called was.

In PB6, we closed this gap... and in doing so we have eliminated the ability to call a protected function from outside of the class it is declared in, or from one of its descendants or nested classes.

In looking at the documentation for PB7, I see that we document protected to include only descendants of the class where the function is declared. It also happens that we allow nested classes to call a protected function as well (this was the fix you mentioned in your bug description (CR 170917)). The idea is that a nested class should have access to anything that it's parent has access to.

In the case that this bug, 206805, was reported against, you have a UO (uo_button) that is dropped onto a window. The UO happens to contain the CB control and because of this, the Window Painter creates a CommandButton control on the window that inherits from the UO. If you export the syntax for the window w_genapp_sheet you will see that. This makes the UO class, where the script containing the function call lives, not allowed to call the protected function because it is not in either a nested class or a descendant class. The actual command button that is placed directly on a window, containing the same script, happens to be a nested class and therefore it is allowed to call the protected function.

The bottom line here is that it is actually a feature that we don't allow this. It is unfortunate that the hole in PB5 it was relied on by this customer. In addition, the fix to this would be an architectural nightmare and as a result we are very reluctant to go down that path without a very good reason to do so. If we were to do this it would definitely require major testing efforts and probably only be allowed to be fixed in a major release, or a specially tested EBF or something (if there is such a thing!).

I apologize that I don't have better news. I agreed that this looked like it should work, until I saw what is actually created underneath. Enforcing the protection laws of OO is what dominates this decision and if you check most other OO languages, they also would not allow this. It is unfortunate that we ever allowed this in the first place.

ALSO NOTE: In another customer test case, the UO was an SLE. Customer found that by putting the code on the SLE in the window, and choosing the option to Override the ancestor script. This makes that particular script behave as if the ancestor does not exist. That means that it acts as a nested class on the window, and then the function call works.



CR:206822
CR Number:   206822
Product Name:   PB Enterprise
Product Component:   DW Painter
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.x Catalina
Fixed Version Build Resolution Date Closure Code (If Appropriate)
05 May 2000 Fixed
Description
When maximizing the painters various GUI problems are present in both PB 7.0.1 and 8.0. The problems were also different on WIN 95 and NT 4.0. The problems were also not evident when the painters were not maximized. Problems observed ranged from illegal page faults to items under menu items not appearing.

Workaround: If experiencing problems do not maximize painters.
Workaround Description
 If experiencing problems do not maximize painters. Problems do not exist when painters are not maximized.



CR:206836
CR Number:   206836
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.5.00 28 Mar 2000 Fixed
Description
Customer has migrated from 5.0.04 to 7.0.1. Several of their migrated datawindows cannot be opened. PowerBuilder crashes. This does not apply to all of their datawindows, but they have a large set of similar datawindows which cause PowerBuilder 7 to crash.



CR:206850
CR Number:   206850
Product Name:   PB Enterprise
Product Component:   DW Painter
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.00 EBF1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0 Beta 3 05 Dec 2000 Fixed
Description
Workaround: Export syntax and delete then import new syntax.

Add a link to the link field for a web datawindow and then delete the link. Link = "" is left in the source which generates a hyperlink when the web datawindow is generated. Must export and delete.
Workaround Description
 Export syntax and delete then import new syntax.



CR:206853
CR Number:   206853
Product Name:   PB Enterprise
Product Component:   DW HTML
Status:   Open
OS:   MS Windows NT 4.0
Original Version:   7.0.00 EBF1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
Enhancement Request for Web Datawindow buttons to have HTML links allowed as button clicked action.



CR:206858
CR Number:   206858
Product Name:   PB Enterprise
Product Component:   Printing
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
14 Oct 1999 Fixed
Description
Happens when printing using the HP8000 printer and
driver. Using pfc and the print service. Powerbuilder will crash.



CR:206914
CR Number:   206914
Product Name:   PB Enterprise
Product Component:   Plug-ins
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
Numeric Edit masks when used in a Window plugin (on datawindows or on controls) corrupt data entered
in those fields .
Workaround Description
 Do not use numeric edit masks, use an edit edit style



CR:206917
CR Number:   206917
Product Name:   PB Enterprise
Product Component:   Language - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.00 EBF1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15 Jun 2004 EOL'd version. Not to be Fixed.
Description
10 - 15 % Degradation in performance from PB 6.5.1 to PB 7.0.1 when calling functions.



CR:206922
CR Number:   206922
Product Name:   PB Enterprise
Product Component:   DB Informix
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.00 8003 01 Dec 1999 Fixed
Description
Most of the time I get a Page Fault (using WIN95) in PBVM70.DLL@0137:113daa40 (build 7015). Once I did get a SmartHeap Library error MEM_BAD_POINTER and Runtime Library error Visual C++, (see zip file for .bmp files customer sent...I got those same errrors). This is all happening when connecting via the native Informix driver IN7.
However, using the ODBC driver with PB 7.x does not experience the page faults or application errors.

The problem with this application is the error does not occur in the same place consistently. Basically adding records and deleting records from one particular dw. Sometimes it takes a few minutes of using the app, other times it happens immediately. Sometimes it does not happen until the app is closed or closed and then either try to open an object like a window (in development) or re-run the application.
The only consistency is the module & address where the error occurs.

I also ran with the PB Intersolv OEM 3.11 32-bit INFORMIX ODBC driver connecting to informix and never got an error.
Also tried with ASA database and MS SQL Server via MSS, still no errors.
Workaround Description
 Get a copy of PBIN770 or PBIN970 built after 10/10/99. You need this fix to prevent overwriting memory when updating a datawindow w/ a DATE column.



CR:206934
CR Number:   206934
Product Name:   PB Enterprise
Product Component:   OLE - Active X - OCX
Status:   Closed
OS:   Microsoft Windows 98
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.5.00 31 Oct 2002 Fixed
Description
OLEObject Function SetAutomationTimeout(Interval) GPF's if the interval value is set to zero or a negative value.

To prevent the GPF, set a value greater than zero.
PowerBuilder's default timeout interval value is 300,000 milliseconds(5 minutes).
Workaround Description
 To reset to default value:
Convert 5 mins to milliseconds i.e. 300,000.
ret = xlapp.SetAutomationTimeout(300000) // set default 5 minutes.



CR:206943
CR Number:   206943
Product Name:   PB Enterprise
Product Component:   DW Painter
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.00 EBF1 20 Mar 2000 Fixed
Description
DDDW contains a column name that is the same as the table name + column name without the "." (dot).
ie tablename: product_group DBname: description.
Name in dw painter: product_group_description

If a column in a dw has an edit style of dddw and that dw is (as described above), and you click on the column with the edit style dddw, that's when the error will occur. The error: Page Fault PBVM70.DLL@1037:11239c15 (using 7.0.01).
If the name is changed in the dw (in the one that is the dddw), to something else like description, the error will not occur.

This was not a problem in 6.5



CR:206952
CR Number:   206952
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0 Beta 1 26 Apr 2000 Fixed
Description
The DataWindow.printer property which is modifiable for DataWindows is not modifiable for Datastores.



CR:207000
CR Number:   207000
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.00 EBF1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
13 Nov 2000 Not a Bug
Description
With PB 7.01 the HorizontalScrollMaximum Datawindow Object property in a datastore doesn't return a value anymore. The propertie is not documented for a datastore but worked since PB5.



CR:207029
CR Number:   207029
Product Name:   PB Enterprise
Product Component:   DW Painter
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
20 Mar 2000 Fixed
Description
When a column in a grid datawindow is made invisible, there will be an empty grid column inbetween other columns in preview or run-time, after the datawindow has been reopened. This happens in preview or at run-time.

The empty column is the result of the expression "1~t0" that gets saved for the value of the visible property.

Work-arounds :
- Export the datawindow and modify the expression to "0", i.e. remove the 1~t from the string
- Modify the datawindow column with the statement dw_x.modify("<column name>.visible=0")



CR:207086
CR Number:   207086
Product Name:   PB Enterprise
Product Component:   Menus - Runtime
Status:   Closed
OS:   MS Windows 3.1
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.5.00 1137 12 Dec 2000 Fixed
Description
On a command button I have the following script:

m_main.Item[1].Visible = true
m_main.Item[2].Visible = false
m_main.Item[3].Visible = true
m_main.Item[4].Visible = true

When I run the window and the script on the command button gets executed I get the following results:

With 32 bit PB on WIN NT/WIN 95

Menu items 1, 3 and 4 are visible ---------> works as expected.

With 16 bit PB on WIN 3.11

Menu items 1, 2 and 4 are visible ---------> Regression, because it worked with PB 5.x



CR:207110
CR Number:   207110
Product Name:   PB Enterprise
Product Component:   DW Display
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.00 EBF1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
27 Oct 1999 Fixed
Description
ReSelectRow( ) doesn't work if the dw datasource is a stored procedure.

WORKAROUND:
string ls_select
ls_select=dw_1.describe ("datawindow.table.procedure")
dw_1.modify ("datawindow.table.select=''")
dw_1.reselectrow (dw_1.getrow())
dw_1.modify ("datawindow.table.procedure='"+ls_select+"'")
Workaround Description
 WORKAROUND:
string ls_select
ls_select=dw_1.describe ("datawindow.table.procedure")
dw_1.modify ("datawindow.table.select=''")
dw_1.reselectrow (dw_1.getrow())
dw_1.modify ("datawindow.table.procedure='"+ls_select+"'")



CR:207116
CR Number:   207116
Product Name:   PB Enterprise
Product Component:   DW Painter
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
1244 03 May 2000 Fixed
Description
PowerBuilder 7 gets an access violation when the datawindow edit or editstyle CodeTable limit of
255 characters was exceeded.
There should be a validation error when the user has entered more than 255 characters and moves to another field.



CR:207120
CR Number:   207120
Product Name:   PB Enterprise
Product Component:   DW - Runtime
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 Fixed
Description
Has two datawindows dw_1 and dw_1 and wants to report changes done on dw_1 to dw_2 using Getchanges() and Setchanges().
It works fine if dw_1 was populated by a Retrieve() but not if it was populated by a SetFullState().



CR:207140
CR Number:   207140
Product Name:   PB Enterprise
Product Component:   OLE - Active X - OCX
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.00 EBF1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8008 08 Jan 2001 Fixed
25 Feb 2004 Fixed
Description
comments or script in an GLG OCX event "Input" causes an memory leak.



CR:207182
CR Number:   207182
Product Name:   PB Enterprise
Product Component:   Plug-ins
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.00 7022 11 Feb 2000 Fixed
Description
When using the window activex plugin that has a dw, you cannot tab thru the columns using the tab key. Using the page up, page down, up arrow or down arrow also don't work.

Happens on IE 4.0 and 5.0



CR:207183
CR Number:   207183
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.x Catalina 1170 01 Dec 1999 Fixed
8007 06 Mar 2000 Fixed
Description
Stored Procedure Inserts do not work with floating point datatypes



CR:207194
CR Number:   207194
Product Name:   PB Enterprise
Product Component:   DPB
Status:   Closed
OS:   Solaris 2.6
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
14 Oct 1999 Fixed
Description
While running a shellscript from a UOF within a DPB PB server application a major memory leak can be observed on both the server and client applications.



CR:207204
CR Number:   207204
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9015 29 Jun 2004 EOL'd version. Not to be Fixed.
Description
Dynamically modifying a crosstab datawindow's Columns, Rows or Values property will result in unhandled exceptions in pbvm using any of the syntax below.

dw_1.Object.DataWindow.Crosstab.Columns='Dept_name'
dw_1.Modify("Datawindow.Crosstab.Columns = 'Dept_name'")
dw_1.Object.DataWindow.Crosstab.Columns = ls_columns
dw_1.Modify("Datawindow.Crosstab.Columns = '" + ls_columns + "'")

Only workaround is to uncheck 'Rebuild columns at runtime' option in the datawindow painter but in many cases this will not be practical
Workaround Description
 Uncheck 'Rebuild columns at runtime' option in datawindow painter (if possible)



CR:207211
CR Number:   207211
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   Microsoft Windows 98
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.5.00 05 Apr 2000 Fixed
Description
The problem is regarding vertical scrollbar affecting External Tabular datawindow summary band.
When ALL detail rows fit in the dw control height setting and property vscrollbar is TRUE, the summary band is too large to display in the dw control, then a vscrollbar is appropriate.
However vscrollbar does not show.

This problem does not happen for External datawindows of type Grid or Freeform.



CR:207227
CR Number:   207227
Product Name:   PB Enterprise
Product Component:   Library Painter
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.00 EBF1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
05 Dec 2000 Fixed
Description
Access Violation in library painter when closing all views and then chosing menu item View - Tree or View - List



CR:207244
CR Number:   207244
Product Name:   PB Enterprise
Product Component:   DW DDDW
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
14 Apr 2003 Fixed
Description
If a datawindow column has a DDDW edit style with 'always show arrow' checked then any format for that column is lost.
If the 'always show arrow' option is unchecked the format appears correctly.
Workaround Description
 Uncheck the property 'always show arrow'



CR:207245
CR Number:   207245
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   Microsoft Windows 98
Original Version:   5.0.04
Fixed Version Build Resolution Date Closure Code (If Appropriate)
21 Jan 2002 Fixed
Description
The datawindow ScrollHorizontal and ScrollVertical events are not triggered with mouse movements when property LiveScroll is set to TRUE.

These 2 events are not triggered when vscrollbar or hscrollbar positions are altered with
a) click and drag mouse on the scrollbar itself
or
b) click on the arrow markers on each end of the scrollbar e.g. |<| |>|
Workaround Description
 ScrollHorizontal and ScrollVertical datawindow events are triggered correctly when property LiveScroll = false.





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

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

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

ReadASADB适用场景

各种误操作:

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

本工具的应用场景:

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