远程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:197481
CR Number:   197481
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 18 Aug 1999 Fixed
Description
6.5.00 EBF Regression. Datawindow Painter. Can't change editmask by typing over. Any datawindow column with editmask can't be changed by typing over. (all datatypes affected).

Workaround: You must paste the mask from the clipboard in order to change it. IE bring up notepad and type in the editmask you want - copy and then paste it into the Powerbuilder datawindow dialog.



CR:197488
CR Number:   197488
Product Name:   PB Enterprise
Product Component:   Library Painter
Status:   Open
OS:   MS Windows NT 4.0
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
TeamPS: Enhancement Request
Allow libraries selected in the Listview to be added to the LIbrary Search Path
with a single right mouse button click. (Add selected libraries to current library
path.)



CR:197556
CR Number:   197556
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.0.00 EBF1 6011 18 Jun 1999 Fixed
Description
Crosstab datawindows may contain zero for numeric row values.



CR:197558
CR Number:   197558
Product Name:   PB Enterprise
Product Component:   DB Sybase System
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
This ONLY happens with PBSYT (dblib) AND if server is installed on NT, if installed on UNIX and using PBSYT the behavior reported does not occur. Also, PBSYC (ctlib) works okay.
Uses embedded sql scripts for inserting into a table, an error is encountered a violation of primary key or a constraint.
After the duplicate insert we get: SQLDBCode 2601 SQLErrText =Attempt to insert duplicate row constraint violation"
Subsequent operations results in SQLDBCode = 20019 SQLErrText = attempt to initiate a new sql server operation with results pending.

Developers comments: Deferred since PBSYT60 is not strategic and was never delivered for PB 7.0



CR:197583
CR Number:   197583
Product Name:   PB Enterprise
Product Component:   PB GUI
Status:   Open
OS:   MS Windows NT 4.0
Original Version:   7.x Catalina
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
In PB 6, I could create a function, put some code in it and Save the function. If I created an object structure, I entered the details and closed it, saving the contents. Now, I create a new function by choosing the object (in the script painter), selecting New Function and entering my code. I cannot SAVE the function. Save only works on the object, so it goes through saving EVERYTHING, a process which is much slower in PB7 already. The same applies to structures.



CR:197584
CR Number:   197584
Product Name:   PB Enterprise
Product Component:   PB GUI
Status:   Open
OS:   MS Windows NT 4.0
Original Version:   7.x Catalina
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Fixed
Description
Inconvenience: When setting up a connection object using the connection wizard, when I get to profiles and the one I want i s not there, I would like to be able to create one without canceling out and starting over.



CR:197585
CR Number:   197585
Product Name:   PB Enterprise
Product Component:   PB GUI
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.00 RC2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12 Dec 2000 Presently Not Targeted For Any Future Release Of This Product
Description
The properties tab of an object invariably shows a list of available options. Many times the option is a checkbox. If you click to the right of
the checkbox name (way over to the right), it will change the option. Not all that critical, but then resize the properties tab to be much bigger, or
even full screen. Now clicking over to the way right is nowhere near the option itself, and yet it still changes. I think the options should NOT be
resize-enabled controls that resize with the screen. In fact, I think the standard Windows operation for checkboxes is that you have to click in the checkbox, not on it's name.



CR:197601
CR Number:   197601
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)
30 Jun 1999 Not a Bug
Description
When entering a partial date in a date or datetime column
and then you either tab out, press enter or use powerscript dw_1.accepttext(),
the itemerror event does not fire.

Example:
Type in 00/00/2000 and then tab out
returns 01/01/2000

Type in 01/01/0000 and then tab out
returns 00/00/0000

In the edit control validation process, the above examples should fail
in the validation process triggering the itemerror event.



CR:197642
CR Number:   197642
Product Name:   PB Enterprise
Product Component:   DB Sybase System
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 1045 12 Nov 1999 Fixed
Description
SYC Timestamp in dynamic SQL format 4 returns error on fetch.
Error 2 (rc -1)
CLI 1 #132 ct_fetch(): user api layer: internal common library error: The bind of result set item 3 resulted in truncation.
WORKAROUND :
use a datastore with a dynamically created DataWindow instead of SQL format 4
Workaround Description
 WORKAROUND :
use a datastore with a dynamically created DataWindow instead of SQL format 4



CR:197661
CR Number:   197661
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)
27 May 1999 Fixed
Description
Description: When deploying a PB jaguar component to an
existing Java package, the following error message results:
Jaguar Error Code:
SystemException: comp.sybase.CORBA.idl.SyntaxError: file
D:\Program Files\Sybase\Jaguar CTS 3.0\Repository/SVU.tmp
CTS: PB UserException : expected IDL type

Workaround:
Edit the IDL module as follows:
#include <TabularResults.idl>
#include <CTS.idl> <-- add this line



CR:197674
CR Number:   197674
Product Name:   PB Enterprise
Product Component:   DB JDBC
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 1077 07 Mar 2000 Fixed
Description
JDS - JDBC Sun VM - JDBC 2.0 driver to informix connect error. "Catalog tables cannot be created" warning. You then cannot create any tables and the metadata folder in the database painter is empty (it should have valid datatypes).
You get various errors: "No such column name", etc.

As of May 20th, 1999 only version 1.4 of the JDBC driver is supported. You need to go to the Informix.com site (which redirects you to intraware.com to get either the 1.4 or the 2.0 driver). Support for 2.0 should be added shortly.

Although not completely documented, the URL should contain the user and password fields delimited as shown. Here is a good example:

jdbc:informix-sqli://mysystem:1526/stores7:informixserver=informix7;user=myuser;password=myuser;

Workaround: Use ODBC driver or use the supported JDBC 1.4 driver.



CR:197725
CR Number:   197725
Product Name:   PB Enterprise
Product Component:   System Runtime Functions
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
Run function increases memory usage in task manager.



CR:197749
CR Number:   197749
Product Name:   PB Enterprise
Product Component:   Window Painter
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.04
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16 Sep 1999 Presently Not Targeted For Any Future Release Of This Product
Description
Resizing bitmap in window painter causes lines to disappear.

Per Development:
Resizing a bitmat may alter the view of the bitmap, such as the disappearance of line segments. This change was cause by a deliberate behavioral change in PB 5.0.04 where the default StretchBit mode was changed from BLACKONWHITE to COLORONCOLOR. This introduced the problem with lines in the black and white BMP images.



CR:197755
CR Number:   197755
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.x Catalina 30 Mar 2000 Fixed
Description
Sending a Tab message to the datawindow control from the EditChanged event causes PB to crash.



CR:197770
CR Number:   197770
Product Name:   PB Enterprise
Product Component:   OLE - Active X - OCX
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
When using the Formula One OCX on a PowerBuilder window, the mouse pointer does not change to an arrow when it passes from the cell area over the scroll bar area.



CR:197776
CR Number:   197776
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 1005 18 Aug 1999 Fixed
Description
When a datawindow is modified (whether modify function or dot notation) in the editchanged event, in this case a protect property for a different column is changed, the itemchanged event is fired. This did not occur in PB 5.0.04 and does not occur in PB 7.0 build 5031. The following results were found when testing the sample.

PB Version/build Occurs in Development Occurs in EXE
--------------------------------------------------------------------------------------------------
PB 5.0.04 NO NO

PB 6.0 GA NO YES

PB 6.0/620 YES YES

PB 7.0/5031 NO NO



CR:197805
CR Number:   197805
Product Name:   PB Enterprise
Product Component:   DB Oracle
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
PowerBuilder 6.5 and 7.0:
When using UPDATEBLOB to update an Oracle 8 LOB dataype, a ROLLBACK will make the LOB column empty.

Work-Around :
Use a LONG RAW column when clobs or blobs can be ROLLBACKed in script.
Workaround Description
 Use the LONG RAW datatype.



CR:197830
CR Number:   197830
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
The buttonclicked (and probably buttonclicking event) returns the wrong row in the row argument in an n-up style datawindow. It seems to do what an earlier bug with n-ups and the datawindow clicked event (since fixed) giving the user the rightmost element row number (ie if it's a 3-UP, it would only return 3,6,9 for the row argument) in the horizontal row.



CR:197841
CR Number:   197841
Product Name:   PB Enterprise
Product Component:   DW SaveAs
Status:   Open
OS:   MS Windows NT 4.0
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
Enhancement. Excel 97 format for SaveAs() function.



CR:197862
CR Number:   197862
Product Name:   PB Enterprise
Product Component:   DW ActiveX
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.5.00 1006 31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
OLE1 blobs do not activate in datawindows in PowerBuilder 6 and above.



CR:197868
CR Number:   197868
Product Name:   PB Enterprise
Product Component:   DB Sybase System
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 Leak when using a dynamic cursor. Possibly related to an open CR - 159694.

Customer reported this when connected to Microsoft SQL Server but it also occurs with Adaptive Server Anywhere. Loses between 1000-1500K per 9900 records processed. Similar results when run with PB 7.0 build 5031.

Each run represents processing of 9901 records
Using NT 4.0 Task Manager to see Memory Usage

Results when run with PB 6.5 build 620 and EA Studio
----------------------------------------------------------------------------------
Memory Difference
Memory Usage at Start 52344K 0
Memory after 1st run 53452K 1108K
Memory after 2nd run 54436K 984K
Memory after 3rd run 55836K 1400K

Close out of app 55712K
Close out of PB 6.5 Memory returned

Results when run with PB 6.5 build 620 and MSS SQL Server
----------------------------------------------------------------------------------
Memory Difference
Memory Usage at Start 45664K 0
Memory after 1st run 46956K 1292K
Memory after 2nd run 48124K 1168K
Memory after 3rd run 49284K 1160K

Close app PB still running 49150K
Close out of PB 6.5 42224K



CR:197880
CR Number:   197880
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
Using window activeX, a backspace in an SLE causes the prior page to display.



CR:197884
CR Number:   197884
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   5.0.04
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0 Beta 2 16 Oct 2000 Fixed
Description
When the client PC is set up for Regional Settings yyyy/dd/mm, datawindow columns of type DATE with edit style "edit" (NOT editmask), tabbing off after data entry causes the month and day portions of the entered date to get switched before your eyes. This bug has been in the product since 5.0.

This is a dangerous bug since it affects data entry, validation (and validation rules) and datawindow expressions using this date column.

Closely related to 197886 and 193284.



CR:197886
CR Number:   197886
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   5.0.04
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0 Beta 3 22 Dec 2000 Presently Not Targeted For Any Future Release Of This Product
Description
If your control panel regional settings are set to yyyy/dd/mm, retrieval arguments sent will switch the day/month and submit incorrect queries. The retrieval argument dialog is an Single line edit with no editmask so this is like an edit style "Edit".

Example: enter 1999/03/05 in a retrieval argument dialog for a date column (May 3, 1999). The pbtrace.log shows:
1999-03-05 which is really March 5th, 1999.

IE. For SQL Anywhere, the PBDateFmt default in the PBodb<60,70>.ini is 'yyyy-mm-dd'.

Closely related to CR197884 and CR193284.

Development: We ask Windows what the date sequence is ( 0=m/d/y, 1=d/m/y, 2=y/m/d, note there isn't one for y/d/m). Windows says the sequence is "2" which is what we use.

Expanded note in User's Guide on date columns and regional settings. See pbman.chm dated 12/11/00 or later.

This requires the use of an edit mask. Sorry, not a bug and here's why; when we read a date column with no editmask, we ask windows what the date sequence is ( 0=m/d/y, 1=d/m/y, 2=y/m/d, note there isn't one for y/d/m). Windows says the sequence is "2" so we interpret that way. yyyy/dd/mm is kind of unusual as a date format and evidently isn't something Windows recognizes either. However, an edit mask ought to work fine for them.

As part of work on CR 193284 it has been determined that the support for yy/dd/mm will NOT be added to PowerBuilder in order to preserve the current applications that may be relying on the current behavior of switching to yy/mm/dd when yy/dd/mm is encountered. We believe that it is too high a risk to be changing at this stage and since this is a very unusual, an unsupported by WIN32 date format, we will not be supporting it.



CR:197928
CR Number:   197928
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)
17 Apr 2000 Fixed
Description
7.0 Datawindow painter issue. With Regional Settings yyyy/dd/mm and a date column of edit style "edit"... the Format tab of a date column is shown as 15989/??/??.



CR:197934
CR Number:   197934
Product Name:   PB Enterprise
Product Component:   Web.PB
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
07 Sep 1999 Not reproducible with latest version of the product available as of Resolution Date
Description
When in the webpb wizard and you select the pbl, the
next screen displays the uo's in the pbl. In this case only three out of the
six uo's appear.

It appears from the test case that uo_listener is the problem preventing
the rest of the uo's from showing in the list.

Workarounds: Export the uo_listener uo. Delete uo_listener. Import
the uo back into the pbl. Now when you go into the wizard all the uo's will
show up.

Another workaround is to modify the comments for uo_listener in the
library painter. When you go back into the wizard all the uo's will show up.



CR:197936
CR Number:   197936
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)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
Scrolling a datawindow with a scroll bar may cause the data in wide text columns to not scroll with the datawindow.



CR:197937
CR Number:   197937
Product Name:   PB Enterprise
Product Component:   Web.PB
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
After selecting the object from the webpb project wizard
and then populating the properties, the webpb wizard does not populate
the function, page title, page style and link text. You can select a function
from the ddlb and populate the rest of the fields. After hitting ok, the above
properties are not populated. The "apply" cb button remains disabled.



CR:197962
CR Number:   197962
Product Name:   PB Enterprise
Product Component:   Script Painter
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 22 Jun 1999 Fixed
Description
5.0/6.0/6.5 (not in 7.0). Severe handle leak - 80-100 handles - each time you enter and exit the script painter. Over time, in NT, if you get to around 6000 handles (as viewed through Task Manager/Performance Tab), you won't be able to open another script painter or do anything in PB. Sometimes when you hit a high number of handles, the next action causes PB to just disappear (GPF). This can also cause other programs (Explorer) to GPF or not be able to bring up simple dialogs.

Exiting PB frees all the handles.

Other related handle leaks:
Saving an object leaks around 40 handles.
Going in and out of the library painter leaks 80 handles.

Several painters: Profile (350), DB (100), Function (100-110), Application, Project, Menu leak at least 50 handles opening them and 20-40 handles saving an object.



CR:197982
CR Number:   197982
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 have three levels of DDDW PowerBuilder will terminate with an application error if you try to preview the DataWindow in the DataWindow painter.

PowerDesigner generates such DataWindows in certain scenarios.



CR:198030
CR Number:   198030
Product Name:   PB Enterprise
Product Component:   DW Painter
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
18 Aug 1999 Not a Bug
Description
Grid datawindow column expression width=0 makes column disappear in painter. This is a behavior throughout 5.0-7.0. Since changing the visible attribute of a column to "0" in the expression leaves the column STILL VISIBLE in the painter, it's hard to say why the width with an expression of "0" would immediately shrink the object to '0' width in DESIGN mode. This only happens for a grid datawindow and the width is a "live" property in grids.

Development: This is actually a feature. In the case of objects with attribute moveable/resizable specified or when presentation style of grid, actions in preview will be reflected back to the design view. Forget, for a moment, the expression thing: with grid, resizing columns will immediately take effect in design. When expression has been set, we won't react immediately in design view BUT, as soon as you do another move of column in preview, we'll rebuild the whole dw in design based on how it currently looks in preview.
NOTE: You can also simulate this same behaviour using expression on an object that has moveable and/or resizable options set.



CR:198032
CR Number:   198032
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)
22 Jun 1999 Duplicate
Description
A static text control on a window or datawindow allows multi-line properties. A long string can word wrap if you make the static text control narrow in width. When you modify the long string that is already word-wrapped in the control, it automatically resizes the static text control onto ONE line. This is an old reported behavior.



CR:198044
CR Number:   198044
Product Name:   PB Enterprise
Product Component:   DW Printing
Status:   Closed
OS:   Microsoft Windows 98
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.00 27 Apr 2000 Fixed
Description
PB7.0 does not print correctly a datawindow which has a jpg/jpeg picture control object.
The result is a solid black filled in/ shaded rectangle instead of the graphic/picture.
Workaround Description
 Use bmp or gif formats till a fix is available.



CR:198052
CR Number:   198052
Product Name:   PB Enterprise
Product Component:   TAPI
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 1999 Fixed
Description
Suspected memory leak with describer() method of Test_DW, using pbtapi.h.



CR:198058
CR Number:   198058
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 18 Jun 1999 Fixed
Description
SetItemStatus() is performed on a key col of the datawindow to change it to DataModified(), if the row has the status of NewModified!, PB generates a Delete and Insert statment as if the row had the status of DataModified()



CR:198061
CR Number:   198061
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
There is a memory leak when you use OLE automation and an array of OleObject[] instances. Destroying the instances doesn't release all the memory.



CR:198062
CR Number:   198062
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.0.00 EBF1 18 Jun 1999 Fixed
Description
The combination of GetChanges()/SetChanges() will not set the column flag to DataModified! if the value of the changed column is NULL.



CR:198063
CR Number:   198063
Product Name:   PB Enterprise
Product Component:   DW SaveAs
Status:   Open
OS:   MS Windows NT 4.0
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
Enhancement. SaveAs() rich text format for regular and nested datawindow.



CR:198123
CR Number:   198123
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
ActiveX created in VB5 has a couple of functions, one of them contains code Form1.Show. If the style = 1, the form is modal, if style = 0 the form is modeless and PB displays an error when the function is called: R0035 Application Terminated. Error calling external object function...



CR:198184
CR Number:   198184
Product Name:   PB Enterprise
Product Component:   Jaguar Integration
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
25 Feb 2004 Fixed
Description
If a structure passed by reference to a PB Jaguar component passes the structure to another method in a different component, an error occurs.
Workaround Description
 Make a local copy of structures passed in by reference and pass the local copy to the called method.



CR:198193
CR Number:   198193
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)
27 May 1999 Duplicate
Description
In the Define Result Set dialog, if you tab out of the 'Type' column, instead of tabbing to the next column (Size), you tab to a new row.



CR:198197
CR Number:   198197
Product Name:   PB Enterprise
Product Component:   Function 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 1072 22 Jun 1999 Fixed
Description
7.0 Regression. Creating a user object function that overrides an existing function deletes the original function from the object. The missing function is no longer found in the source either.



CR:198207
CR Number:   198207
Product Name:   PB Enterprise
Product Component:   DW Plugin
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
Datawindow Plugin from 6.x and 7.x does not display a 5.x PSR reports properly



CR:198214
CR Number:   198214
Product Name:   PB Enterprise
Product Component:   DW Synchronization
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   7.0.00 EBF1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.5.00 1096 03 Jan 2002 Fixed
Description
Memory leak with datawindow synchronization in 7.0
Verified fixed in 6.5.1 "MJD" EBF (build 7021), and in 7.0 build 7014



CR:198265
CR Number:   198265
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 Feb 2000 Fixed
Description
OLE custom control events Clicked and DoubleClicked are not fired



CR:198348
CR Number:   198348
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)
16 Mar 2004 EOL'd version. Not to be Fixed.
Description
When in the Edit tab of the Properties View in the DataWindow Painter if you drop down the choices for Style Type and click the same choice you had originally ( say DropDown DW) it blanks out everything else that had been set originally. Even if you simply drop down the list and move the mouse to a different choice, but do not click anything and then try to close the painter by clicking the' X' in the right hand corner all properties are set to the defaults although the Type has not changed. You do have to close the painter again, but unless you notice that these properties have been changed, the defaults are now saved. In Pb 6.5 if you choose the same edit style no changes are made.

Additional regression in the Edit Tab of the Properties View in the DataWindow Painter is that in PB 6.5 if there is any change to any of the the properties the Style Name is removed but in 7.0 it allows you to make changes to the properties but the Style Name remains.

Additionally an enhancement to be able to remove the Style Name without the other properties changing would be helpful.



CR:198410
CR Number:   198410
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)
25 Feb 2004 Fixed
Description
Trying to develop a way to communicate errors to the client in a stateless environment and are running into problems not being able to raise exceptions.



CR:198423
CR Number:   198423
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)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
If you declare a variable of type char in a PB script and pass the value in SQL statement with DisableBind set to one, an error will occur during the database update.
Workaround Description
 1) Do not set DisableBind to 1

2) Use string variables instead of char variables in the script.



CR:198447
CR Number:   198447
Product Name:   PB Enterprise
Product Component:   Pipeline Painter
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.5.00 1013 15 Jun 1999 Fixed
Description
Piping a table (while creating the new table in the pipeline) from a MS SQL server 6.5 database to an MS SQL server 6.5 database may fail due to an ill-formated table create statement



CR:198459
CR Number:   198459
Product Name:   PB Enterprise
Product Component:   DW SaveAs
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
If you try and save microseconds into a time datatype and retrieve the data back again. The value is saved as zero e.g. 12:12:12.12 -> 12:12:12.00
This can be done using ISQL. Using ISQL I can save 12:12:12.12 into the database. If I retrieve this in PowerBuilder I get 12:12:12.00.

Note: Microseconds can be saved using the timestamp datatype.



CR:198499
CR Number:   198499
Product Name:   PB Enterprise
Product Component:   Inheritance
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
Ancestor object needs regeneration when controls added or deleted to/from last descendant given there is a Dynamic event call from an ancestor user object/ window function.

PB procedure: The descendant object modified and it's parent need regeneration so that the parent is aware of
the descendant's changes - so regenerate object at current (level) and (level - 1).

In this scenario:
w_charity (Grandfather) has function wf_valid()
|
w_main (Father)
|
w_support (Child)

A cmdbtn on the ancestor window (w_charity) has this code:
boolean lb_test
lb_test = wf_valid() //call window function on ancestor

//////////////////////////////////
Window function: wf_valid() has the following code:
Long i, max_number_of_objects
boolean lb_success = TRUE , lb_newvalue = TRUE

string ls_str , ls_powerbuilder_object
ClassDefinition cl_def

max_number_of_objects = upperbound(Control[])

for i = 1 to max_number_of_objects
ls_str = this.control[i].classname()
ia_any = this.control[i].event dynamic ue_invest() //returns classdefinition instead of null value for ia_any if the family hierarchy has not be //regenerated after new control objects added to last descendant
//
IF IsNull(ia_any) THEN
messagebox('At grandparent Level 1:object ' + ls_str , 'NULL value returned from dynamic event call because this control does not have this User Event defined.')
ELSE
cl_def = ia_any
ls_powerbuilder_object = cl_def.classname()
if ls_powerbuilder_object = 'classdefinition' then messagebox('ia_any ', ls_powerbuilder_object )

lb_newvalue= ia_any //this line has problem with new control objects added to LAST/FINAL descendant only
//error msg- Cannot convert classdefinition to boolean from any value
// however if regenerate family hierarchy ,then works fine
if NOT lb_newvalue then lb_success = lb_newvalue //Change variable only if result is Boolean FALSE

END IF
next

return lb_success // return TRUE only if all control objects perused returned TRUE
///////////////////////////////

When controls are ADDED or DELETED on the last descendant window (w_support) the following error occurs:
PB Application Execution Error R0063:
Function/Event with no return value used in expression at line XX of wf_valid of object
w_charity.

The customer reported this problem when using User objects and user object functions.
I expanded my tests to use standard control like window objects with window functions.

PB6.5.444 and 70_5031 on Win98:
Type of object Type of function having dynamic call Result
Visual User object User object function in ancestor Broken
Window object Window object function in ancestor Broken

Testing log PB6.5.444 and 70_5031 on Win98:
1)
Add/Delete control on w_main, regenerate next descendant w_support.
Run app, call ancestor window function --> Result OK.

2)ACTION: Test dynamic event call in an ancestor window function:
Add new controls on last descendant w_support
Call ancestor window function --> gives error msg above.
Regenerate w_support, run app --> gives error msg above.
Regenerate w_main, run app --> gives error msg above.
Regenerate w_charity, run app --> Result OK.

3)ACTION: Test dynamic event call in a window function on last descendant:
a)
Cmdbtn on ancestor window has code:
boolean lb_test
lb_test = parent.function dynamic wf_pay()
b)
wf_pay() is a window function in the last descendant w_support which has the same code
as above for the wf_valid function.
c)
Add new controls on last descendant w_support
d)
Run app, call descendant window function --> Result OK.
Workaround Description
 Regenerate the family of inherited objects concerned.



CR:198545
CR Number:   198545
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 Fixed
Description
If you have an edit mask of ##-##-## on a window object and if copy and paste 123456 into the edit mask. The edit mask will display 00-12-45 instead of 12-34-56 as you would expect.



CR:198637
CR Number:   198637
Product Name:   PB Enterprise
Product Component:   Language - Runtime
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
Setvalue() causes gpf when when populating ddlb. Using PFC and of_additem function to a uo.
In pfc we are using setvalue() which causes a gpf depending on the index order.
uo_1.of_additem(70, "Hair")
uo_1.of_additem(60, "Slisk")


causes a crash


workaround:
uo_1.of_additem(60, "Slisk")
uo_1.of_additem(70, "Hair")
Workaround Description
 inser items in decending order
uo_1.of_additem(60, "Slisk")
uo_1.of_additem(70, "Hair")



CR:198670
CR Number:   198670
Product Name:   PB Enterprise
Product Component:   Language - Runtime
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
if you use a trim() function without a retrun value the machinecode executable causes a Dr. Watson
Example:
string mystring
mystring = " hallo "
trim(mystring) -> Dr. Watson

Workaround:
use the trim() function with a return value.
Example:
string mystring
mystring = " hallo "
mystring = trim(mystring)
Workaround Description
 use the trimfunction with a return value.
Example:
string mystring
mystring = " hallo "
mystring = trim(mystring)



CR:198709
CR Number:   198709
Product Name:   PB Enterprise
Product Component:   DB Oracle
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 1201 31 Oct 2002 Fixed
Description
O84 driver: OS authenticated connection to Oracle 8 without user/password fails with Error:
ORA-01017: invalid username/password; logon denied
Workaround - use o73 driver with required support files



CR:198710
CR Number:   198710
Product Name:   PB Enterprise
Product Component:   DW Printing
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 use a rectangle object in a datawindow to hide other objects underneath the rectangle, when the datawindow is printed, it still prints the hidden objects. The strange thing is that print preview hides the objects correctly. You can see this behavior using HP IV drivers. (you do have to use "Bring to Front" on the rectangle object so the drawing order is correct to hide the objects.

Workaround: Use Modify() to set the visible attribute of all objects you want to hide.



CR:198719
CR Number:   198719
Product Name:   PB Enterprise
Product Component:   Menus - Runtime
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.00 EBF1 6012 24 Jun 1999 Fixed
Description
PB7 regression
When one sheets uses ChangeMenu , then this menu will stay in the menu bar when closing the sheet or clicking on another sheet. Only opening the next sheet will work.

Work-around : add a proper changemenu call in the activate event of the sheets



CR:198743
CR Number:   198743
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)
7.x Catalina 19 Jul 1999 Fixed
Description
Setfullstate() does not draw/redraw data on a graph object placed on the datawindow. You will see the graph object but it will be blank after the setfullstate().

Workaround: The setfullstate does not bubble up information into the "child" graph object but should. To get around this, you can do one of 2 things.

// force it to redraw by forcing the visible attribute to 1 (yes, it's already visible). Make sure you name the graph object "gr_1"
dw_1.getfullstate(blob_variable)
dw_2.setfullstate(blob_variable)
dw_2.object.gr_1.visible=1

// or
dw_1.getfullstate(blob_variable)
dw_2.setfullstate(blob_variable)
dw_1.filter() // This is a little more "destructive" - and might affect the data if you have a filter defined.



CR:198752
CR Number:   198752
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 Fixed
Description
Getfullstate()/Setfullstate() has a noticable memory leak after many iterations. It looks like it's not cleaning up the blob from the previous setfullstate() in the datawindow control. (very similar to CR192073, 198214.)

Works fine in 7.0.1 build 6012.



CR:198780
CR Number:   198780
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)
6.5.00 1042 19 Jul 1999 Fixed
7.0.00 7006 19 Jul 1999 Fixed
Description
Informix 7 IN7 - serial value shows as zero after DataWindow update() when DisableBind=1



CR:198840
CR Number:   198840
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 29 Mar 2000 Fixed
Description
Passing a numeric argument to a stored procedure or returning a numeric argument (Sybase SYB driver) may cause a data conversion error.



CR:198851
CR Number:   198851
Product Name:   PB Enterprise
Product Component:   DW HTML
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
HTMLDataWindow component is spelled incorrectly in the

\powerbuilder 7 \code examples\HTMLdw in the Remote datawindow example pbl (PBDWRMT.pbl).



CR:198865
CR Number:   198865
Product Name:   PB Enterprise
Product Component:   DW Printing
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 7002 22 Jun 1999 Fixed
Description
If you use modify or dot notation to change the number of copies to be printed (datawindow.Print.Copies) the number of copies that gets printed is squared, i.e. if you set it to print 2 copies, you will get 4 printed, if you set to 3, it will print 9, etc.



CR:198909
CR Number:   198909
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 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
Enhancement Request: IN7, SYC, & ODB RowsCopy should refresh autoincrement after DataWindow update() automatically



CR:198952
CR Number:   198952
Product Name:   PB Enterprise
Product Component:   Language - Compiler
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
Compiler should check all possible paths through a function in order to ensure that a correct value is returned in all possible cases. This would safeguard against coding errors.



CR:198955
CR Number:   198955
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 07 Jul 1999 Fixed
Description
6.5.1 Regression. The rowfocuschanged event fires when the Sort() function is invoked after a retrieval when the user clicks to a row > 1 and then uses the tab key or clicks into another column of the same row.



CR:198959
CR Number:   198959
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)
19 Jul 1999 Not reproducible with latest version of the product available as of Resolution Date
Description
6.5.1 Regression. Setfullstate no longer works correctly on NT 3.5.1 Nothing displays in the destination datawindow though the return code is good.



CR:198968
CR Number:   198968
Product Name:   PB Enterprise
Product Component:   Application Painter
Status:   Open
OS:   MS Windows NT 4.0
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
Enhancement Request:
Customer would like a way to add defaults to the to-do list. This facility should support multiple developers using PB. They would like to update the pre-defined list of To Do's for each wizard. For instance, say the Jaguar Component Wizard has 8 To Do's which normally pop up after the wizard. Customer would like to modify the list of 8 default To Do's to delete one and add 3 more customized for their purposes. Not a huge issue but would be nice. These lists should be available to transfer among all the developers in each company for standardization.

See TechDoc for PB 7.x & 8.x (#1013138)
Adding Customized Items to Wizard Generated To-Do Lists (PowerBuilder 7.x & 8.x)
http://my.sybase.com/detail?id=1013138



CR:198983
CR Number:   198983
Product Name:   PB Enterprise
Product Component:   File Editor
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.00 RC1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
24 Jun 1999 Not a Bug
Description
The file editor behaves differently than before. PB6 behavior - Click on the File Editor Icon and you get a File Open Dialog to choose the file to edit. PB7 behavior - Click on the File Editor Icon and you get the File Editor. Click on File Open to get to the Open File Dialog.



CR:198988
CR Number:   198988
Product Name:   PB Enterprise
Product Component:   Script Painter
Status:   Open
OS:   MS Windows NT 4.0
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
Variable Access Not good. Getting to Instance Variables has to be made easier.

1. From a script painter - I have to open another script painter and select DECLARE (which is not intuitive), or use the popup menu and choose
GoTo | Instance Variables (which I can't do if I'm in the middle of a piece of script), or choose Edit... GoTo... Instance Variables from the menu.
Instance Variables whould be selectable from the View menu.

2. If I do NOT have a script painter open, I cannot get to instance variables at all. Why do I have to open a script painter to get to
instance variables? They belong to the object not the script.

3. If I do NOT have a script painter open, I can't get to Global Variables. I should have access to Global Variables from ANYWHERE. They're not tied to an object, but to an application.



CR:198996
CR Number:   198996
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 Fixed
Description
Receive a PowerBuilder Application Execution Error (R0035) when running an Excel Macro using OLE Automation. Receive different results when run on different platforms and with different number of rows as input. Initially also recieve a MicroSoft RunTime Error '1004' . The text of the Microsoft error is 'You cannot save this workbook with the same name as another open workbook or add-in. Choose a different name, or close the other workbook, or add-in before saving. there is a choice to choose a Debug Command button and this brings you intot he Visual Basic Debugger within the custoemr supplied Macro. The MicroSoft Error did not consistently come up when running on NT 4.0. Also when run with a smaller numebr of rows in WIN95 neither error came up and the Macro completed successfully.

When run on WIN 95 the resulting Excel report appears to actually be generated although when the number of rows selcted is greater than 2500 the error is still generated. When you exit PB and go into Excel the report appears to be complete. In NT 4.0 regardless of the number of rows the error is generated although again the actual report appears to be created properly.

When the macro is run directly through Excel or through OLE in VB 6.0 it runs without the problem.

Solution is to add the following line of code right before running the macro:

excelobj.SetAutomationTimeout( 900000 ) // 15 minute timeout

The documentation states that if you timeout you will receive a 1037 runtime error but in this case we received a R0035 instead.



CR:199079
CR Number:   199079
Product Name:   PB Enterprise
Product Component:   DB OLE DB
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0 Beta 2 2049 24 Oct 2000 Fixed
Description
MS SQL Server columns of data type bit do not display properly using the PB OLEDB driver. Instead of displaying as 0 or 1, a floating point external value is displayed.



CR:199089
CR Number:   199089
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)
6.5.00 16 Sep 1999 Fixed
Description
6.5 Regression: Passing decimals in a structure; something has changed from 5.04



CR:199110
CR Number:   199110
Product Name:   PB Enterprise
Product Component:   DW HTML
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 6011 18 Jun 1999 Fixed
Description
The browser ignores style sheet rules with _ in their names. The HTML generation uses the ObjectName to generate the rule names. IE5 works fine, but IE4 does not display it correctly.



CR:199111
CR Number:   199111
Product Name:   PB Enterprise
Product Component:   DW HTML
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 6011 18 Jun 1999 Fixed
Description
Without diving into the implementation, it is not possible to keep two Web DW's on the same page in sync.



CR:199190
CR Number:   199190
Product Name:   PB Enterprise
Product Component:   DB OLE DB
Status:   Open
OS:   Microsoft Windows 95
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
New Feature Request: Microsoft has OLE DB providers for OLAP but they are not supported by PowerBuilder.



CR:199199
CR Number:   199199
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)
20 Jun 1999 Not a Bug
Description
Datawindow goup headers may repeat when a datawindow is printed.

Per Development:
No Bug -- DW design breaks the DW header/row size-restriction rules (it was only a fluke that it worked in 5.04 as this design is NOT supported). The user has the wrong DW design for the desired report. Instead of huge page headers and group headers, that break DW design rules, the data should be presented in a series of nested DWs. The nested DWs would ensure proper pagination.



CR:199204
CR Number:   199204
Product Name:   PB Enterprise
Product Component:   DW Expression
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 7003 01 Aug 2000 Fixed
Description
PB7.0. If a DW select statement contains an ORDER BY and this DatwWindow also prompts for criteria (column specification) Powerbuilder places the ORDER BY clause between the first part of the where clause and the second part which is generated from the criteria column specification. On retrieve the DataWindow gives a Syntax Error



CR:199209
CR Number:   199209
Product Name:   PB Enterprise
Product Component:   Language - Compiler
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15 Jun 2004 EOL'd version. Not to be Fixed.
Description
Within the PFC pbls if you try to declare an instance variable of type u_dw PB crashes when trying to save the variable. If you migrate a copy of the object that already has an instance variable of this typ,e and then try to declare another one it works fine. Also tried with u_tab and it did not have a problem. This did not happen in PB 6.X. Also if you create the same type of object with a small sample the instance variable saves without a problem. Object is corrupted after this happens.

Workaround: To recover object. Export the object in the Library Painter. Edit it to remove references to the instance variable and then reimport it back in.



CR:199219
CR Number:   199219
Product Name:   PB Enterprise
Product Component:   Jaguar Integration
Status:   Open
OS:   MS Windows NT 4.0
Original Version:   7.0.00 RC0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
Enhancement Request:
Add the java package name as part of the properties in the java deployment in Powerbuilder.

Java package name is the name of the java "package" ( basically directory
off the Classpath ) that you will deploy generated stubs to. For example,
the way it is setup now, you will by default generate stubs to a directory
that is the same name as your Jaguar package. You can change this by
setting the "java package name" property in module properties in Jaguar
Manager. This is helpful when creating a commerical application as the
stubs should go in the "com" directory off the classpath. For us, the java
package names that we assign are something like com.dds.jaguarpackagename.
The problem that we are having is that we often have to deleted entire
modules and we lose these settings every time that we do. We have to go
into Jaguar Manager and set these properties for each module. It would be
nice if the PB deployment projects supported this property as well as the
other Jaguar properties that it does not.



CR:199220
CR Number:   199220
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)
26 Mar 2001 Fixed
Description
Enhancement: Animated gif support has not been added for picture objects in a datawindow. It has been added for picture controls on a window.



CR:199221
CR Number:   199221
Product Name:   PB Enterprise
Product Component:   Jaguar Integration
Status:   Open
OS:   MS Windows NT 4.0
Original Version:   7.0.00 RC0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
Add transaction timeout to project properties in PB.

In Jaguar there is pool timeout and transaction timeout.
In the PB project, only one is supported. If we change the other's value in
Jaguar Manager, it gets overwritten every time we redeploy.



CR:199244
CR Number:   199244
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)
03 Nov 1999 Not reproducible with latest version of the product available as of Resolution Date
Description
<ALT><ARROW DWN> and <ALT><ARROW UP> no longer opens and closes DropDownDataWindows and DropDownListboxes within a datawindow



CR:199250
CR Number:   199250
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 1021 29 Jul 1999 Fixed
Description
The PB6.5.1 maintenance release has memory leaks with some Scroll type Functions.

Scroll functions tested:

ScrollToRow() // dw_test.scrolltorow(ll_nr)
ScrollPriorRow()
ScrollNextRow() // li_ret = dw_test.scrollnextrow()
ScrollPriorPage()
ScrollNextPage() // li_ret = dw_test.scrollnextpage()

Action:PB6.5.1 on NT4.0(Build 1381 SP3) in development environment.
Iteration RESULT
il_max=1000 | 2000 | 6000
No Scroll function in DO LOOP :
Before run app 60348K | 60944 | 60916
Exit App 60240 | 60948 | 60924 OK

With ScrollToRow function statement:
Before run app 61388K | 60864 | 60916
Exit App 62092 | 62000 | 63644 Leak

With ScrollPriorRow function statement:
Before run app 62212K | 60936 | 60924
Exit App 62148 | 60944 | 60916 OK

With ScrollNextRow function statement:
Before run app 62148K | 61996 | 60472
Exit App 62896 | 63532 | 63276 Leak

With ScrollPriorPage function statement: il_max = 10,000
Before run app 60516K | 60740 | 60568 | 60868
Exit App 60524 | 60840 | 60552 | 60912 Leak

With ScrollNextPage function statement:
Before run app 60516K | 57612 | 54432
Exit App 60516 | 57608 | 57580 Leak

2)
Action:PB6.5 on NT4.0(Build 1381 SP3) in development environment.
Result: No memory leaks with any of the scroll functions.
Workaround Description
 None available.



CR:199252
CR Number:   199252
Product Name:   PB Enterprise
Product Component:   Library Painter
Status:   Open
OS:   MS Windows NT 4.0
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
Enhancement request: Need the ability to specify opjects as READONLY so that their code can be viewed, stepped through in the debugger etc, but may not be changed in any way unless "Protection" is deactivated.



CR:199255
CR Number:   199255
Product Name:   PB Enterprise
Product Component:   PB GUI
Status:   Open
OS:   MS Windows NT 4.0
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
Enhancement request : Would like Object Browser as an additional view in painters.



CR:199256
CR Number:   199256
Product Name:   PB Enterprise
Product Component:   PB GUI
Status:   Open
OS:   MS Windows NT 4.0
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
Enhancement Request: Views: Add capability to place Instance Variables, Arguments etc (Paste Special List) as separate "lists" such as Function and event lists. Double click on an item to copy into your code. (Edit | Paste Special | Arguments | Choose from list does not seem to be a good replacement for the dropdown list of arguments that were available in PB6).



CR:199289
CR Number:   199289
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 1048 30 Mar 2000 Fixed
Description
Scrolling a DW with an Intellimouse produces an application error when the height of the detail band is set to 0 :
Application error : The exception Integer division by zero .......

Fixed in 6.5 1048, 7.0.2 build 8025
Workaround Description
 In the other event of the datawindow control put :
IF Message.number = 522 THEN
IF long (dw_1.Object.DataWindow.Detail.Height) = 0 THEN return -1
END IF



CR:199299
CR Number:   199299
Product Name:   PB Enterprise
Product Component:   DW SaveAs
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 1087 16 Nov 2000 Fixed
7.0.3 10005 16 Nov 2000 Fixed
Description
SaveAs PSR (Powersoft Report format) only saves 2 levels of nesting. The 3rd and subsequent levels are missing. causing: "Load of nested report <report name> failed" error when loading PSR into a plug-in, datawindow control or in InfoMaker..



CR:199300
CR Number:   199300
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.0.00 18 Jun 1999 Fixed
Description
7.0 regression: Declaring large instance arrays hangs when saving object.



CR:199340
CR Number:   199340
Product Name:   PB Enterprise
Product Component:   UO 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 28 Jan 2000 Fixed
Description
Structure view open in the UserObject Painter causes PB to crash if the structures have long names
Declaring structures with long names in the user object painter causes PB7 to crash



CR:199349
CR Number:   199349
Product Name:   PB Enterprise
Product Component:   DW Display
Status:   Open
OS:   MS Windows NT 4.0
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
Provicde option to print footer only on last page .

As far as an enhancement request, giving the Footer band an option to only print
on the last page would do the job.

I would also request something a little more generic. I would propose what
I would call a "Positioning" band that the user could chose to put anywhere
(within any band) within a datawindow (maybe even limited to a report type
datawindow - one that does not allow updates). This "Positioning" band
would have characteristics as follows:

Have it start immediately following a previous item (autosize height) or
give it space increment (inches or powerbuilder units). The previous item
could be a previous band (top of the band or bottom of a band), or could be
the top or bottom margin of the datawindow (report).

It would be nice if it would allow you to specify that this "Positioning"
band would have some "Page" mode options such as 1) no page break, 2) always
start a new page or 3) start a new page if less than xxx inches/pb units
available on bottom of page."



CR:199364
CR Number:   199364
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)
08 Jun 2000 Fixed
Description
Create a New DW presentation style with Data Source - Query with retrieval arguments.
Powerbuilder/ Infomaker error message at the end of the DW Wizard :
'Arguments for select are invalid or incorrect'



CR:199388
CR Number:   199388
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)
22 Sep 1999 Presently Not Targeted For Any Future Release Of This Product
Description
For a listview, the rightclicked event and the rbuttonup event are not firing in the proper order.
In 6.5.1 the order of the events are reversed when right clicking on an item.
In PB7 the rbuttonup event is not firing at all.

====
Resolution:

There was a fix in pb6.5 for issue # CR 183803 that was made specifically to change the behavior of ListView Right Mouse processing. With this fix, the behavior should match what is expected and that is in fact why the behavior changed between builds mentioned in the description.

In PB7, we are using Microsoft's ListView and TreeView controls and the behavior we are seeing is the way it is intended to work per Microsoft and we cannot change that behavior without doing something very ugly in PB which we want to avoid doing. In PB7 the rbuttonup is never received by the application, however, this is the way Microsoft has coded it.



CR:199395
CR Number:   199395
Product Name:   PB Enterprise
Product Component:   DB Oracle
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
Retrieval argument on a decimal datatype (ex numeric 7:2) does not work properly.
The SQL statement sent to the server truncate the decimal part of the variable.
for instance : where variable = 24,24 is sent like this : where variable = 24,00 (see pbtrace.log )

dw_1.retrieve(24,24) will send to the server as 24,00

If you specifiy the retrieve like

dw_1.retrieve(24.24) will send to the server as 24,23



CR:199407
CR Number:   199407
Product Name:   PB Enterprise
Product Component:   Jaguar Integration
Status:   Closed
OS:   Microsoft Windows 95
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
If you deploy an object to jaguar with the option to include inreferenced objects in consolidated PBDs, you may not be able to open the object because the constructor event fires.



CR:199427
CR Number:   199427
Product Name:   PB Enterprise
Product Component:   Web.PB
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
UNIX: App server crashes with a segmentation fault using
webpb on solaris 2.5.1. Using performix test tool to stress test app server.

Using Open Client 11.1, ASE 11.5, pb 6.5 with windu 4.2, netscape 3.61 web server.



CR:199433
CR Number:   199433
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
Memory leak using datawindow dot notation on a large range of data and populating an array of type Any. Becomes a problem when this is done repeatedly within a loop.



CR:199439
CR Number:   199439
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)
6.5.00 1022 08 Jul 1999 Fixed
Description
Disconnect using pbmdi takes longer in PB 6.5 than it did in PB 5.0.04
Workaround Description
 None



CR:199447
CR Number:   199447
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
Using the WheelMouse or Intellimouse with a wheel sometimes hides items in a listview or treeview. In the cases with the problem, there is no vertical scrollbar on the particular listview so the scrolling gets a little confused. (#1. It scrolls all items up through the top of the listview. #2. PB forgets to repaint the area so if you scroll the items back down using the wheel, the items aren't visible).

NOTE: Using lv_1.setredraw(true) will display the items when you scroll them back on the screen. Unfortunately, there is no event that captures this easily (no pbm_mousewheel) to script a setredraw(). An enhancement has been entered for this support.





--------------------------------------华丽的分割线-------------------------------------------------------------------------
之前就已经研发成功了能够从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等等。
+-------------------------------------华丽的分割线-------------------------------------------------------------------------