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

 

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

如有问题,请联系我!

QQ :289965371 联系我们获取数据库技术支持!
Email:
不仅仅包括BUG的详细描述信息,还包括首次报告BUG的平台、数据库版本以及BUG修复历史过程;有些BUG还提供了Workaround来临时解决该BUG带来问题。

 

CR:157191
CR Number:   157191
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.04
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.5.00 470 16 Dec 1998 Fixed
Description
Windows 95 Only. For DataWindows with the Prompt Before Printing property set, the Print Properties dialog box does indeed come up, but if nothing is changed and OK is clicked, Nothing Is Sent To The Printer! If something is changed, the print works fine.



CR:157203
CR Number:   157203
Product Name:   PB Enterprise
Product Component:   DB Oracle
Status:   Closed
OS:   MS Windows 3.1
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
Data Pipeline - destination connection is Oracle 7.x database. Table contains all primary key columns. Doing an UPDATE and INSERT in the pipeline, some of the data in the text file are duplicates. When the pipeline executes, the following error message occurs: "ora-0001 unique constraint violated"



This works in 6.0



Work around is to have a non-key column in the table.



CR:157204
CR Number:   157204
Product Name:   PB Enterprise
Product Component:   Plug-ins
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
Datawindow always has a scroll bar when using the datawindow plugin - regardless of the width you define for the client space in the html file



CR:157207
CR Number:   157207
Product Name:   PB Enterprise
Product Component:   DB Sybase System
Status:   Closed
OS:   Solaris 2.5.1
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
Enhancement. Powerscript should check the syntax and datatype of the "INTO" variables.



// emp_id is an integer column from sql anywhere



string string_var

SELECT emp_id into :string_var from employee;



will compile since the "emp_id" column and table "employee" exist but the Powerscript editor won't check to see if the "INTO" variables are compatible with the host variable :string_var.



Dynamic SQL has the same type of issue and would be even harder to check. Powerscript leaves it up to the developer to make sure the datatypes between Powerscript and the database match and are compatible.



// Dynamic SQL example



string sqlstring, ls_var

int li_var

sqlstring = "Select emp_id from employee where emp_id = 105"

...

open <cursorname>;

fetch <cursorname> into li_var;

or

fetch <cursorname> into ls_var;



both compile - and both actually work too in Wintel platforms - go figure - no runtime error.



CR:157208
CR Number:   157208
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   5.0.03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
When using Select * from table1, table2 and table1 and table2 have the same names for "n" columns (for example 2 columns each) these columns will be unnecessarily repeated in building the datawindow, the datawindow created will have the following datawindow columns:





table1.col1

table1.col2

table1.col1_1 <---- these should not be there.

table1.col2_1 <---- these should not be there.

table2.col1

table2.col2



It should be:



table1.col1

table1.col2

table2.col1

table2.col2



NOTE: This is not database specific. Recreated with Sql anywhere.



CR:157210
CR Number:   157210
Product Name:   PB Enterprise
Product Component:   TAPI
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
After running the application, if you then edit an object, you cannot save it (you get a save failed message).



CR:157211
CR Number:   157211
Product Name:   PB Enterprise
Product Component:   Window Painter
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
Control-Tab allows invisible tab pages to be selected. The top of the tab page with the label text doesn't show, just the contents.



CR:157217
CR Number:   157217
Product Name:   PB Enterprise
Product Component:   OLE - Active X - OCX
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
07 Jul 1998 Presently Not Targeted For Any Future Release Of This Product
Description
NT 4.0 problem only: Rich text control: if you change the font to a non-truetype font, and make it italic, the text display becomes garbage. Can only be reproduced on NT 4.0, other platforms are okay.



CR:157222
CR Number:   157222
Product Name:   PB Enterprise
Product Component:   Web.PB
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   5.0.03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
Application hangs or crashes when passing around 8000 characters to Web.PB



CR:157233
CR Number:   157233
Product Name:   PB Enterprise
Product Component:   DB ODBC
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
DB2 using ODBC. SELECT statements involving aggregate column functions (e.g., sum, count) on columns that contain null values fail to retrieve results in PB with the following message



Select error: SQLSTATE=01003

[IBM][CLI Driver] SQL0000W Statement processing was successful.



or



SQLSTATE 01S01 [IBM][CLI Driver] CLI 0165E Error in Row



CR:157234
CR Number:   157234
Product Name:   PB Enterprise
Product Component:   Machine Code Exe Creation
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.5.00 26 Aug 1998 Not reproducible with latest version of the product available as of Resolution Date
Description
GPF in the C-Code generation step (after full rebuild done) for 16 bit machine code in the project painter.. During creation of the DLLs (after the regeneration is complete and the process is just creating C-Code), it GPFs. This occurs in the project painter. From the Library painter the problem DLL (tracked down by seeing where it dies in the C-code and seeing what object it was compiling) builds fine.



CR:157239
CR Number:   157239
Product Name:   PB Enterprise
Product Component:   Source Control
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11 Mar 1999 Presently Not Targeted For Any Future Release Of This Product
Description
Performing a Registration Directory, filtering out objects so only those of a particular older, version appear, and then performing a TAKE operation on a single object (or all objects), does not bring back the previous version object -it brings back the latest version (i.e. the tip object); when using PVCS.



The desired object of the previous version should be created - the tip object should not be created.



CR:157240
CR Number:   157240
Product Name:   PB Enterprise
Product Component:   GenApp
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
Win 95.. pb 5.0.04 or pb 5.0.02 32 bit

Customer is trying to assign an array of float variables from an external function. He has declared a bounded array of either double or real and has the same problem:





R0047:Array expected in ANY variable at line ### in Open event.



When he uses an array of strings, this works fine.





DOUBLE FloatArray[2], fl_dec

OleObject obj



obj = CREATE oleobject

obj.ConnectToNewObject("MFCAutoItem.AutoItem1")





FOR i = 1 to 2

FloatArray[i] = 1234567

NEXT



IF (obj.SetFloats(FloatArray)) then

messagebox("successful", "", Question!, OK!)

END IF



FOR i = 1 to 2

FloatArray[i] = 0

NEXT



// Error: Array expected in ANY variable when using DOUBLE

// you must use safearrays when passing arrays using OLE

// automation



FloatArray = obj.GetFloats()



The floatarray(safearray) is of data type float, if it were of string or integer there would be no problem.



CR:157252
CR Number:   157252
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   MS Windows 3.1
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
Win 3.11 or 16 bit under NT 3.51. Printing in landscape cannot be achieved by changing the orientation with Modify() or by saving "landscape" for orientation in the dataobject. Win 3.11 uses whatever is in the Print Setup dialog and this is currently the only way to change orientation (PrintSetup()). Happens on a postscript printer driver.



CR:157254
CR Number:   157254
Product Name:   PB Enterprise
Product Component:   DW SaveAs
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
Trail Footer property of a composite report isn't saved in PSReport with saveas function



CR:157255
CR Number:   157255
Product Name:   PB Enterprise
Product Component:   Language - Compiler
Status:   Closed
OS:   MS Windows NT 3.51
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
After declaring a cursor in Powerscript, Powerbuilder seems to convert the cursor name to lower case, even though it's declared in uppercase in script. You can see this using ODBC spy. It's a more generalized ODBC issue.



CR:157261
CR Number:   157261
Product Name:   PB Enterprise
Product Component:   DW Rich Text
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
Win 95 only

32 bit { pb 5.0.02, pb 5.0.03, pb 5.0.04_39 }



Keywords:: RTE, DW , print and print preview



Problem description::



Customer is using an RTE dw. If the inserted text fields are too long the text does not wrap onto the next line. Instead the line has no blank spaces between words!



In print preview you can see the first line "squashed" together. There are no spaces between the words as you would normally see in the dw design mode.



CR:157265
CR Number:   157265
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
N-up dw - expression determining whether a column is visible, if visible, it can still be tabbed to. In tabular datawindow, if column is invisible, it also cannot be tabbed to.



WORKAROUND: Use the same dw expression for the Protect property, and now you cannot tab to the column when it is invisible/protected.



CR:157272
CR Number:   157272
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.00 14 Oct 1998 Fixed
Description
Datawindow using retrieval argument of type TIME prompts user as TIMEARRAY during retrieval. If you pick a retrieval argument of type "TIME ARRAY" it prompts you for a retrieval argument of type TIME. Same in 4.0 and 5.0 so it's been in the product for awhile.



CR:157278
CR Number:   157278
Product Name:   PB Enterprise
Product Component:   C++ Class Builder
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
30 Dec 1998 Presently Not Targeted For Any Future Release Of This Product
Description
In a C++ classbuilder userobject, unable to call the following Microsoft Server 6.x API calls that provide user-supplied message and error handling:

dberrhandle((DBERRHANDLE_PROC)err_handler);

dbmsghandle((DBMSGHANDLE_PROC)msg_handler);



Error under 5.0:

"The instruction at 016a23b5 referenced memory at 00001645, Memory could not be read."



Error under 6.0:

"The instruction at 0x03063f64 referenced memory at 00001645, Memory could not be read."



CR:157304
CR Number:   157304
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   MS Windows NT 3.51
Original Version:   5.0.03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
In query mode can't build a sql statement like :

Select ....... where emp_fname LIKE 'A%' AND emp_fname LIKE '%B'



CR:157312
CR Number:   157312
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.0.04 17 Apr 1998 Fixed
Description
Small behavior problem in the setitemstatus(). Setting the row status to datamodied! and column status of the PRIMARY key to datamodified! (with the update characteristics of the primary key set to DELETE and INSERT during key modification) should always do a DELETE and INSERT. In this case, setitemstatus() of the primary key column and row status to datamodified! results in an UPDATE statement being generated.



Workaround: after setitemstatus() of row and primary key to Datamodified!, must do a setitem() of the primary key column to itself (same value). This will generate the DELETE and INSERT.



Solution:

This issue will not be fixed at this time. There is a reasonable workaround and the fix has the potential for breaking a large amount of customers already using this functionality.



CR:157314
CR Number:   157314
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   5.0.03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
When pressing a key with focus on a datawindow a GPF occurs. It only seems to occur when all of the following are true:

1. the datawindow contains a dropdowndatawindow that is editable.

2. there are rows in the filtered and/or delete buffers of the datawindow

3. there is code in the datawindow's editchanged event. Unfortunately, we have many datawindows like this and have not found a workaround yet. The code consisted simply of a comment, no actual programmed activity.



CR:157315
CR Number:   157315
Product Name:   PB Enterprise
Product Component:   Business Graphics
Status:   Closed
OS:   MS Windows 3.1
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
07 Jul 1998 Presently Not Targeted For Any Future Release Of This Product
Description
Line graph displayed using 16 bit powerbuilder results in very bizarre display. It's fine using 32 bit, and it's better using 16 bit Powerbuilder on a 32 bit machine, but running 16 bit PB on 16 bit machine, you get a very strange picture. Problem occurs with several line graphs displayed on the same window, and does not occur for most line graphs.

Per Development:
Not to be fixed.



CR:157320
CR Number:   157320
Product Name:   PB Enterprise
Product Component:   DW Painter
Status:   Closed
OS:   MS Windows NT 3.51
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10 Sep 1998 Not a Bug
Description
In the DataWindow painter the Graph and Picture Button objects names are showing numbers after obj_



CR:157335
CR Number:   157335
Product Name:   PB Enterprise
Product Component:   DW Painter
Status:   Closed
OS:   HP-UX 10.20
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
Panther 147 - Unix (HP-UX) - DataWindow -> StoredProcedure / Query

-> Crosstab : clicking on "Data Source" in the PainterBar causes "X server error..." to display on stderr.



Here is the complete error message displayed on standard error :



X server error, Message reported is: BadDrawable (invalid Pixmap or Window parameter)



There is no "fatal" event that occurs after the above error is displayed. This behavior has yet to be tested on Solaris and AIX.



*******************************************************************************



[BSmith] This bug was reported again but in Solaris It is as follows



PANTHER - B103. REGRESSION SOLARIS ONLY When creating a Quick Select DataWindow the following Console Message appears:



X Server Error, Message is: BadDrawable (invalid Pixmap or Window parameter)



Steps to recreate:



1) Create a New Quick Select DataWindow.



NOTE at the current time unable to create a SQL SELECT DataWindow.



As soon as you click the OK button after choosing the Presentation style, the above message appears 4 times.



CR:157343
CR Number:   157343
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.0.01 20 May 1998 Fixed
Description
Getting an Out of Memory error when trying to modify the sql statement of a datawindow to a size > 32k (32768). Customer notices that the limit seems to be 32k.





We currently have a 64k limit for Modify() and 32k limit for Describe() of the "datawindow.table.select" attribute.





Development: For architectural reasons , only fixed in PB 6.0.



CR:157345
CR Number:   157345
Product Name:   PB Enterprise
Product Component:   DB Informix
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
Follow-on to bug 41608 - Informix 7.11, 32bit TD1 software. Getting "-761 INFORMIXSERVER does not match either DBSERVERNAME or DBSERVERALIASES" when trying to connect to a second server on the SAME host. Seems to work OK when connecting to different servers on different hosts.



PER DEVELOPMENT:

Worked with customer and found subtle mistake in profiles being used. Under more usual circumstances this would have been obvious, but it took some investigating in this situation. No further problems here.



CR:157350
CR Number:   157350
Product Name:   PB Enterprise
Product Component:   Language - Runtime
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
According to documentation, a shared variable should persist when objects are closed, and even if all instances of an object are closed. So when you open a new instance of an object, the shared variable value should remain set to whatever it was when the most recent prior instance was open. This works for user objects which are not autoinstantiated, but when the user object is autoinstanciated the shared variable value is not maintained when all instances are closed and then a new instance is opened.



CR:157360
CR Number:   157360
Product Name:   PB Enterprise
Product Component:   DB Informix
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   5.0.03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.0.01 17 Apr 1998 Fixed
Description
Pipeline painter/Informix 7.x driver. When creating a pipeline from an Informix table using the IN7 (PBIN7050.DLL) driver, all columns to be piped are shown "NOT NULL" in the painter dialog, when in fact only a few should be. Destination database type isn't important.



Workaround: Before saving the pipe, edit the definition created by the pipeline painter so the "NULL" checkboxes match the source (Informix 7.x) table for each column being piped.



NOTE: Requires 5.0.04 version of PBIN7050.DLL to use the new functionality of reading the registry "setnet32.exe" entries and using host@dbservername syntax in sqlca.servername.



CR:157361
CR Number:   157361
Product Name:   PB Enterprise
Product Component:   DB Painter
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   5.0.03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
Enhancement. Informix 7.x (PBIN7050.DLL) driver. File/Save Rows As... "SQL Syntax" in preview mode (datawindow or database painter) does not save the CREATE syntax correctly for the driver. When this SQL is executed in the DBA Notepad, you receive a -201 Syntax Error.



The Save Rows As... bugs are:



-datetime columns, YEAR TO FRACTION(5) isn't generated.

-integer columns are converted to FLOAT.

-primary keys, the "NOT NULL" attribute is NOT generated.

-decimal(5,2) becomes the default decimal (16,2)

-smallint becomes FLOAT.

-real becomes FLOAT.

-money(8,2) becomes the default decimal (16,2)

-varchar(10) beomes char(10)



Workaround:

1. Object/Export Syntax to Log in the DB painter. This saves the CREATE syntax correctly - unlike the Save Rows As.... Save this syntax without the INSERTS into the PBCatXXX tables.

2. Preview table in DB painter. Save Rows As... SQL.

Take out the CREATE syntax since this is messed up. Cut and Paste the INSERT SQL (for the rows to be inserted) - this syntax is OK.

3. Add the two files together.



Development: Currently this generation does not involve the database drivers. In a future release, we could leverage our "Export Syntax to Log" functionality to generate vendor-specific syntax here as well.



CR:157363
CR Number:   157363
Product Name:   PB Enterprise
Product Component:   Window Painter
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
Window painter bug. General Property page of a datawindow control has "Title Bar", "Control Menu", "Minimize", "Maximize" checkboxes.



"Title Bar" should be linked to the other three. You can't have the Control Menu, Minimize, Maximize Buttons without first having a title bar on the datawindow control. Notice if you right mouse on any datawindow control, you'll see "Title Bar" checked OFF but the "Minimize", "Maximize" and "Control Menu" are still enabled but they shouldn't be.



If you play around with it enough, it eventually acts correctly but not with a newly-placed datawindow control.



CR:157364
CR Number:   157364
Product Name:   PB Enterprise
Product Component:   Business Graphics
Status:   Closed
OS:   MS Windows 3.1
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
SaveAs of graph control on window to PSR report produces invalid psr file. Is this a doc error, also, should SaveAs return an error if this is attempted ? SaveAs of graph datawindow to PSR is fine.



Probably PSReport! should not be allowed as a saveas format for a graph control on a window, but the documentation indicates that this is a valid format.



WORKAROUND: Use a datawindow graph object instead of just a graph on a window.



CR:157375
CR Number:   157375
Product Name:   PB Enterprise
Product Component:   Shared Objects
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
GPF when building the instance image.



CR:157384
CR Number:   157384
Product Name:   PB Enterprise
Product Component:   DB MS SQLServer
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   5.0.03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.0.03 17 Mar 1999 Not a Bug
Description
Customer is seeing a performance degredation with the native Microsoft SQL Server 6.5 driver (MSS). He does not see the same performance problem with ODBC with relatively small result sets.

Development: Microsoft has made huge improvements in their ODBC driver to offer built in networking etc right in the ODBC driver. As a result, the Microsoft ODBC driver is not like traditional drivers (like Intersolv) where the ODBC driver is a layer on top of the native software.

IT IS A MYTH that ODBC must be slower than native protocols. Intersolv's driver is slower since it sits on top of the native SQL Server drivers.

NOTE: PB Desktop does not allow access to the SQL Server ODBC driver.



CR:157394
CR Number:   157394
Product Name:   PB Enterprise
Product Component:   Plug-ins
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   5.0.04
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.5.00 541 21 Jan 1999 Fixed
Description
Window PlugIn containing a datawindow with a bitmap on a datawindow picture control will not display the bitmap although the same bitmap displays on a picture control on the window used for the plugin. (this means the bitmap actually resides in the .PBD but the window is displaying it and the datawindow is not).



CR:157412
CR Number:   157412
Product Name:   PB Enterprise
Product Component:   Language - Runtime
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
Comparing to two dates with different microseconds pb says they are the equal.



datetime ldt_1, ldt_2



ldt_1 = Datetime(today(),Time(3,36,12,45))

ldt_2 = Datetime(today(),Time(3,36,12,89))



sle_1.text = string(ldt_1,"mm/dd/yy hh:mm:ss.ffffff")

sle_2.text = string(ldt_2,"mm/dd/yy hh:mm:ss.ffffff")

mle_1.text = "Notice that the only difference is in the microseconds portion of the 2 datetime variables"



IF ldt_1 = ldt_2 THEN

messagebox("equal","If you see this message PB thinks that the 2 datetimes are equal even though they are not. Congratulations you've reproduced the bug")

ELSE

messagebox("not equal","Looks like the version of pb you're using doesn't exibit the bug behavior")

END IF



See also bug 43835



CR:157413
CR Number:   157413
Product Name:   PB Enterprise
Product Component:   DW Painter
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
DataWindow painter GPFs if you select all items and attempt to change the font point-size.



CR:157423
CR Number:   157423
Product Name:   PB Enterprise
Product Component:   Window - Runtime
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
18 Nov 1998 Presently Not Targeted For Any Future Release Of This Product
Description
Regression/migration issue, 4.0 to 5.0,6.0: Using 4.0, pressing the tab key while editting in a mle control fired the key event of the window, and changed focus to the next control. Doing the same in 5.0 and 6.0, the key event is not fired, just focus changes.
Is this a bug or change in behavior by design ?

PER DEVELOPMENT:
It is standard behavior for the tab key to to move focus between controls. To enter a tab in an mle, the user should use the Control-Tab
(CTRL-Tab) key combination.



CR:157429
CR Number:   157429
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   MS Windows 3.1
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
16 bit. Large GDI leak printing a datawindow with multiple graph objects set to Foreground. Can lose 10-15% of system resources when printed.



NOTE: There are several other graph object printing bugs. 40131 was a problem with a graph object in the detail band and set to foreground. 42432 was another similar one - both fixed in 5.0.03. This bug is different and wasn't fix until 5.0.04.



CR:157431
CR Number:   157431
Product Name:   PB Enterprise
Product Component:   System Runtime Functions
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description



CR:157440
CR Number:   157440
Product Name:   PB Enterprise
Product Component:   Menu Painter
Status:   Closed
OS:   MS Windows NT 3.51
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
In the menu painter, if you add a new menu item to the parent menu, then when you open the inherited menu item and press save it gives you compiler errors.



CR:157445
CR Number:   157445
Product Name:   PB Enterprise
Product Component:   Menu Painter
Status:   Closed
OS:   MS Windows NT 3.51
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
In the menu painter, if you are in the script painter and select the object browser you will get an assertion failure and then a gpf.



Development: Cannot recreate in 6.0 build 156.



CR:157449
CR Number:   157449
Product Name:   PB Enterprise
Product Component:   DW Painter
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.04
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.x Catalina 1047 04 Aug 2000 Fixed
Description
Print a datawindow wich contains horizontal pages gives a wrong result on paper.

The preview works fine. On paper, the first column values of the horizontal pages are shifted to the right. The printer is an HP 4si.



CR:157459
CR Number:   157459
Product Name:   PB Enterprise
Product Component:   Toolbar
Status:   Closed
OS:   MS Windows NT 3.51
Original Version:   5.0.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
fixed in pbsys60.dll.



CR:157463
CR Number:   157463
Product Name:   PB Enterprise
Product Component:   OLE - Active X - OCX
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   5.0.04
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
Adding an OLE server - the "display as icon" would be ignored. It will always display as content.



CR:157465
CR Number:   157465
Product Name:   PB Enterprise
Product Component:   Menu Painter
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
14 Dec 1998 Presently Not Targeted For Any Future Release Of This Product
Description
GPF in PBRTE050.DLL 0001:97DC when opening up a decendent menu in the menu painter that has the same name as a menuitem in the ancestor menu



Example:



m_ancestor - ancestor menu

m_decendent - decendent



Opening m_decendent when m_ancestor has a menu item colliding with global menu object m_decendent causes the GPF. It's generally with migrated applications since the painter now checks for this case. Migration and regeneration doesn't catch this. Very hard to track down.



CR:157475
CR Number:   157475
Product Name:   PB Enterprise
Product Component:   DB Informix
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   5.0.03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
Pipeline to Informix using the IN7 driver creates syntax that causes -201 errors with an incomplete table with no indexes or primary key flags showing and preceded with a dot (example '.employee') when executing in development.



When you use 'USER ID' - in the profile painter as "informix" (owner of the catalog tables) for example, the data pipes fine. The USERID is required ONLY AT RUNTIME for most of the native drivers as a feature that allows runtime overrides for generating prefixed sql.



CR:157476
CR Number:   157476
Product Name:   PB Enterprise
Product Component:   DB Informix
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   5.0.03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
Save Log As... in the DB painter for Informix 7 (IN7) saves incorrect or un-executable syntax for the DBA Notepad . You get -201 errors.



Workaround: Set USERID in the profile painter to be the owner of the tables. You shouldn't have to do this in development.



CR:157478
CR Number:   157478
Product Name:   PB Enterprise
Product Component:   Profile Painter
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
If you edit a shared database profile and save a copy locally the treeview will not update until you reopen the dialog.



CR:157493
CR Number:   157493
Product Name:   PB Enterprise
Product Component:   GenApp
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
Assertion failure message when generating application with template



PER DEVELOPMENT:

Problem caused due to pb.ini having the read-only attribute set. Fixed after making the file read+write.



CR:157496
CR Number:   157496
Product Name:   PB Enterprise
Product Component:   Application Painter
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
Application Painter : Select Application Dialog : When Opening a existing application, no applications are displayed in the Select Application dialog. When you click on Open Application icon and select a PBL, the Select Application dialog appears, but in this dialog, the application list is empty. The Application Library list also contains only a library icon and no library name. To select the application you need to click on the "Other" button and re select the library.



CR:157500
CR Number:   157500
Product Name:   PB Enterprise
Product Component:   Application Painter
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
Library search path not being saved because PB.INI was read-only.



CR:157502
CR Number:   157502
Product Name:   PB Enterprise
Product Component:   Menus - Runtime
Status:   Closed
OS:   MS Windows 3.1
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
14 Dec 2000 Fixed
Description
Problem: Inconsistent bahavior of toolbar icon when asociated menuitem is made visible and then invisible. In some cases the toolbar item will still work, in others it won't. This scenario is bad programming practice because toolbar items should be made invisible if the associated menuitems are made invisible.



CR:157508
CR Number:   157508
Product Name:   PB Enterprise
Product Component:   Window - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description



CR:157516
CR Number:   157516
Product Name:   PB Enterprise
Product Component:   DPB
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
Client continued to listen to pipe when Disconnected from server only if server host name was specified.



CR:157518
CR Number:   157518
Product Name:   PB Enterprise
Product Component:   Window - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
Window properties minimize / maximize are different on different OS's. Bug or doc problem ? On Win95 and NT 4.0, Control Menu must also be checked to have minimize button. On NT 3.51 and Win 3.11, you can have minimize alone. Doc and behavior only ties property to Title Bar.



CR:157520
CR Number:   157520
Product Name:   PB Enterprise
Product Component:   Window - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
If you put a object on a tab page, Change the border, Cut and Paste the object on the window and then drag it back to the tab control, the border changes to box.



PER DEVELOPMENT:

Shadow borders only appear on their parent window. Moving a control over a tab page only moves it over the tab page, it does not make it a part of the page. The tab control and listview are siblings in that situation. Not a bug.



CR:157521
CR Number:   157521
Product Name:   PB Enterprise
Product Component:   Window Painter
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
If you drag a groupbox, line, rectangle, round rectangle, or oval onto a tab control in order to see it you must send the tab control to back.



PER DEVELOPMENT:

This is not a bug. It is expected behavior.

The group box, and indeed any control, is not part of the tabpage unless it is created on the tabpage. Note that you cannot drag a control off the tabpage either. This is by design.



CR:157535
CR Number:   157535
Product Name:   PB Enterprise
Product Component:   Window - Runtime
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
29 Jan 1999 Not a Bug
Description
Win95 Only. Using custom user events pbm_windowposchanged, pbm_windowposchanging on a datawindow with a titlebar works correctly in NT 4.0 and the events fire multiple times while dragging the datawindow but only fire ONCE in Win95 and only when the datawindow is dropped after dragging.



CR:157536
CR Number:   157536
Product Name:   PB Enterprise
Product Component:   DB ODBC
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description



CR:157550
CR Number:   157550
Product Name:   PB Enterprise
Product Component:   DB Oracle
Status:   Closed
OS:   Solaris 2.5.1
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
O73 DBMS appears with O72 profile dialog.



Per Development:

Original problem fixed.

Also, unlike NT, the Oracle 7.3 API (OCI) for Sol/HP/AIX does not provide a call to invoke thread-safe mode, therefore no checkbox. We'll have to take Oracle's word that these APIs are thread-safe by default.



CR:157589
CR Number:   157589
Product Name:   PB Enterprise
Product Component:   Printing
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
04 Aug 2004 Not reproducible with latest version of the product available as of Resolution Date
Description
win 95b. printing to a printer using the dw preview pb 5.0.02, pb 5.0.03 pb 5.0.04



There are problems at the moment with windows 95 plus. If the customer uses the above workarounds he is all set.

The combination Win 95 4.00.95.0b and Novell network driver is failing the printing of a dw to a printer queue. If you do one of the following, it works fine:

- use an earlier version of Win 95

- use the Microsoft Novell client instead of the Novell Novell client

- print from PB something else than a dw (a script or an object)

- redirect the queue to a port and print to that port instead of directly to the queue



CR:157616
CR Number:   157616
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
Problem Description:Customer is trying to display bitmap in a dw. It shows as the path to the bitmap instead of the picture.



Customer is trying to display bitmap in a dw. Has a dddw, which has been mapped to several bitmaps from parent dw. The property of the column object has set to Display as Picture, and for the edit style (DropDown Dw), the property has set to Always show List. When list is displayed if any of the items get focus, it shows as the path to the bitmap instead of the picture.



CR:157623
CR Number:   157623
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.04
Fixed Version Build Resolution Date Closure Code (If Appropriate)
29 Jan 1999 Not a Bug
Description
When a DataWindow is shared with data from a DataStore, deleting a row behaves differently than when data is not shared. After a row is deleted, the current row always becomes 1. Also, sharing data with another DataWindow, if a row is deleted from the secondary DataWindow, the current row is changed to 1.



CR:157626
CR Number:   157626
Product Name:   PB Enterprise
Product Component:   DB Sybase System
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.x Catalina 1042 18 Apr 2000 Fixed
6.5.00 610 18 Apr 2000 Fixed
7.0.00 EBF1 6005 18 Apr 2000 Fixed
Description
Using a stored procedure to update the database. The DBError event has some arguments, two that are being used: SQLDBCODE & SQLERRTEXT are not getting populated when a database error occurs. SQLDBCODE = 0 and SQLERRTEXT is blank.

If you do a regular datawindow update and a database error occurs, the DBError event fires and SQLDBCODE & SQLERRTEXT are populated with the correct information.



CR:157627
CR Number:   157627
Product Name:   PB Enterprise
Product Component:   Source Control
Status:   Closed
OS:   MS Windows NT 3.51
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
16 bit Powerbuilder "PVCS Interface Error - PVCSGetArchiveInfo Achive File was not found" and "PVCS Interface Error - PVCSCreateArchive: Unexpected Error (219). PB 16bit, NT 3.51/4.0, PVCS 5.2.20



PER DEVELOPMENT:

Verified NAB in 6.0.0.248 and 5.0.04.67

Please check your islv.ini file living either in the windows directory or dir defined by system variable ISLVINI.



CR:157629
CR Number:   157629
Product Name:   PB Enterprise
Product Component:   DW SaveAs
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   5.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Aug 2001 Fixed
Description
SaveAs of Crosstab to PSReport!, the report does not show date retrieve argument displayed in the footer (in a computed field). If the datawindow is Freeform instead, the date retrieve argument in the footer saved to PSR shows up just fine.



The same problem occurs if the computed field referencing a retrieve argument is in the header.



CR:157631
CR Number:   157631
Product Name:   PB Enterprise
Product Component:   DW SaveAs
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
SaveAs with PsReport format generates a wrong file name when using a name with special characters like 猷



CR:157634
CR Number:   157634
Product Name:   PB Enterprise
Product Component:   DB Sybase System
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.00 1009 05 Apr 1999 Fixed
Description
The SYB, DBLIB interface does not return a valid SQLDBCODE for a divide by zero; however it returns a valid SQLCode (-1), that an error did occur. The SQLDBCode should be 3607 which returns properly if using the SYC, CTLIB interface



CR:157640
CR Number:   157640
Product Name:   PB Enterprise
Product Component:   Window - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
While application is running, in development or exe, changing system fonts, color, etc... through Display Properties -->Appearances-->Selected Items and then applying changes, the ddlb's on the opened window that 'Allow Editing' constantly flicker and eventually a page fault (WIN95) or Dr. Watson (NT4.0) will occur.



CR:157641
CR Number:   157641
Product Name:   PB Enterprise
Product Component:   DW Expression
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.00 23 Sep 1998 Fixed
Description
When retrieving a datawindow for which the filter expression contains "col like '%%' ", the PC hangs or PB crashes.



CR:157644
CR Number:   157644
Product Name:   PB Enterprise
Product Component:   DB Informix
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   5.0.03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
32 bit PB. Connecting using Informix I-Connect to 7.2 server(s) on both Unix and NT. Getting errors switching back and forth if the default server in setnet32.exe is the NT 4.0 server. " -25596 Informix server value not listed in SQLHOSTS". Doesn't get any error switching back and forth if the Unix server is the default server in Setnet32.exe on the client.



CR:157645
CR Number:   157645
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)
17 Apr 1998 Fixed
Description



CR:157657
CR Number:   157657
Product Name:   PB Enterprise
Product Component:   DB Painter
Status:   Closed
OS:   Solaris 2.5.1
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
PB 6.0 build 153 on Solaris. Saving log file in the Database Painter fails with "Can't access this folder - path is too long" error message.



CR:157658
CR Number:   157658
Product Name:   PB Enterprise
Product Component:   Installation
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
5.0.03 INSTALL. Setup is installing the 32 bit version of PBTYP050.DLL for 16 bit deployment. This causes several errors in 16 bit executables:



R0014: Error opening dll library pbtyp050.dll for external function



Workaround: Use the 5.0.02 16 bit PBTYP050.DLL for development. They should be 974k.



The 32 bit versions are 964k.



NOTE: The maintenance release for 5.0.03 on the Web site will have the correction as will any new CD's that are built. Affects customers who received the first set of CDs.



CR:157659
CR Number:   157659
Product Name:   PB Enterprise
Product Component:   Menus - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
Messageboxes in close event on sheet can mess up frame menu such that it contains the previous sheet menu when closing the very last sheet rather than its own frame menu. (the frame and sheet have different menus)



Development: This was fixed with other changes to the runtime.



CR:157661
CR Number:   157661
Product Name:   PB Enterprise
Product Component:   OLE - Active X - OCX
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   5.0.03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
5.0.03 Regression. Receiving R0034 app error - Incorrect number of parameters calling ColText function when using the VCI Formula One Workbook with PB 5.0.03. The same code works in 5002.



CR:157665
CR Number:   157665
Product Name:   PB Enterprise
Product Component:   Table Painter
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description



CR:157669
CR Number:   157669
Product Name:   PB Enterprise
Product Component:   DB MS SQLServer
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.5.00 525 13 Jan 1999 Fixed
Description
RPC function call using a decimal value as decimal{6}, where the actual size is 14,6 loses the last 2 digits of precision on an INSERT in the stored procedure. 1234.123456 gets inserted as 1234.123400.



CR:157673
CR Number:   157673
Product Name:   PB Enterprise
Product Component:   Business Graphics
Status:   Closed
OS:   MS Windows 3.1
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
If a whole pie graph is one category then a vertical line appears in the graph. How do we remove the line?



Workaround: in this situation, if you can change the graph line color to be the same as the color of the category, it doesn't show.
Workaround Description
 If a whole pie graph is one category then a vertical line appears in the graph. How do we remove the line?

Workaround: in this situation, if you can change the graph line color to be the same as the color of the category, it doesn't show.



CR:157676
CR Number:   157676
Product Name:   PB Enterprise
Product Component:   Application Painter
Status:   Closed
OS:   Solaris 2.5.1
Original Version:   5.0.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
UNIX ONLY scroll bar has disappeared in the "Select Application Library", and "Select Bitmap" (Inside Menu painter) dialog box. There could be more Browse type windows affected.



CR:157678
CR Number:   157678
Product Name:   PB Enterprise
Product Component:   Script Painter
Status:   Closed
OS:   MS Windows NT 3.51
Original Version:   5.0.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description



CR:157679
CR Number:   157679
Product Name:   PB Enterprise
Product Component:   DW SaveAs
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
05 Jan 1999 Not reproducible with latest version of the product available as of Resolution Date
Description
SaveAs() - ex. dw.SaveAs() which saves a file as a PSReport! will cause a leak with virtual memory(VM). It's worse on NT 3.51 where virtual memory goes up very high with the first SaveAs() call. NT 4.0 is better.



Watching the resource monitor on NT 4.0 you notice that resources move up about 10%, but never fall back down the way it should. It appears that resources are being taken up but never freed.



CR:157680
CR Number:   157680
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
Need the ability to have Bitmaps referenced in picture controls on a datawindow to be saved with a PSR. Today, users have to supply PSR + BMP file(s). This is a datawindow enhancement that applies to plug-in and plain PSR alike.



CR:157684
CR Number:   157684
Product Name:   PB Enterprise
Product Component:   Installation
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
Makefile specified the wrong .odl file for the secure mode Window ActiveX.



CR:157689
CR Number:   157689
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
Enhancement. NUP Datawindow doesn't support placing blob columns. For each row, you get the same blob object that is contained in the LEFTMOST row.



CR:157690
CR Number:   157690
Product Name:   PB Enterprise
Product Component:   DPB
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   5.0.03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
02 Nov 1999 Presently Not Targeted For Any Future Release Of This Product
Description
All versions/maintanance releases of pb 5.0 up to and including pb 5.0.04 32 bit WIn 95 and win NT



Using LibraryImport in a distributed server app always fails if their is a client connected and you are trying to import into a pbl that is in the server's library list.



LibraryImport will work with a standalone application and should work in a distributed application . According to development it should work but something is going wrong



From Development (8/20/97)

This is an architectural problem that cannot be fixed until 7.0.



transferring as an enhancement



CR:157692
CR Number:   157692
Product Name:   PB Enterprise
Product Component:   Window Painter
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
When the amount of text in an MLE is greater than 32K, the mle. Position() and the MLE.SelectedStart() functions don't work correctly. Loading 63466 characters into the MLE worked, but trying to load 63467 characters, the MLE went blank.



Developer: Cannot be fixed in 5.0 because it would require a migration



CR:157697
CR Number:   157697
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
For a column on a Label style datawindow, although Width and Height are listed on the Expressions property sheet for a column, nothing entered there changes the width or height of the column. There is no conflict with the size of the data, either value entered for the width and height easily fits within the label itself.



This may be a limitation of the Label datawindow style, but it is not documented. Also, the expressions property sheet for the label datawindow column does not include other properties that can apply to a column, so just the fact that width and height are listed would imply they could be modified. (Example, the Visible property, valid for columns in most datawindow styles, does not appear in the expressions property sheet for a column on a label style datawindow.)



Possible workaround: Use an n-up datawindow presentation style.



CR:157715
CR Number:   157715
Product Name:   PB Enterprise
Product Component:   Window Painter
Status:   Closed
OS:   Solaris 2.5.1
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
Window with 3 sle. Type some text into the first SLE, hit tab and keep typing and hit tab again still keep typing. Only the first and the third sle are populated. This problem is dependent on the performance of the UNIX box. If the code on the modified event of the SLEs is small (or the UNIX box is very fast), this problem doesn't appear.



Development: Bristol layer fix.



CR:157726
CR Number:   157726
Product Name:   PB Enterprise
Product Component:   Window - Runtime
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
Problem: Access and updates to windows instance variables is inconsistent. Command buttons have access for private variables and those with readaccess set to protected or private read.



CR:157737
CR Number:   157737
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
Checkboxes for 5.0.03 now have the Win95 style but the 3rd state is shown as a dark grey check with an almost white background. Similar to the "checked" state which uses a black check and white background. The checkbox needs 3D and third state checked in properties.



Confusion between checked and 3rd state.



The window control - correctly - has a dark grey background with a slightly darker grey check - like VB 4.0.



WORKAROUND: We're not picking up the default Buttonface color.

For NT 4.0.

-Go into Display settings

-Appearance Tab Folder

-Item: 3D Objects (dropdown)

Notice, the color default will be buttonface. Click Apply and the next time you preview the column, the 3rd state will magically show correctly.



For Win95, it's slightly different. Simply clicking apply doesn't work.



-Go into Display settings

-Appearance Tab Folder

-Item: 3D Objects (dropdown)

-Change buttonface to some other color like Red and "Apply"

-Change Red back to buttonface and you'll see the 3rd state correctly.



CR:157751
CR Number:   157751
Product Name:   PB Enterprise
Product Component:   Business Graphics
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.04
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.x Catalina 1011 14 Apr 1999 Fixed
Description
There is a problem with the SumForCategory column in a bar graph DataWindow. It will always display the value of the first catagory as opposed to the value of each category.



CR:157755
CR Number:   157755
Product Name:   PB Enterprise
Product Component:   Pipeline Painter
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.00 200 25 Sep 1998 Fixed
Description
Workaround: If the max errors is set to anything but one, this problem will not occur. Changed code to propagate error as in pb5.0.03.



CR:157761
CR Number:   157761
Product Name:   PB Enterprise
Product Component:   DB MS SQLServer
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.00 02 Jul 1998 Fixed
Description
Datawindows using date or datetime columns sometimes show incorrect data or ?? when retrieved. Happens most often when a datawindow is built against a database using date and deployed to a database that uses datetime.



Development: For datawindows to be transparently used across databases, developers must set staticbind=0 in their SQLCA.DBPARM (script) or database profile painter. Unfortunately, the default for any connection is staticbind=1 (do not re-bind result set).



No fix is planned. We will try to document this better so users migrating from one database platform to another will be aware of this requirement.



CR:157762
CR Number:   157762
Product Name:   PB Enterprise
Product Component:   Printing
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   5.0.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
Enhancement. Datawindow long text column with embedded linefeeds and formfeeds or carriage returns does not translate character codes <nl> <cr> <ff> to the printed output or print preview in this case.

Development: This is not a feature of the datawindow currently. Users could use ole1 blob column or some other way so saved data with embedded control chars can be interpreted corrrectly.



CR:157766
CR Number:   157766
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   5.0.03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
5.0.03 regression. Scrolling with the thumb knob and resizing the sheet causes display problems. You can't scroll to the first row and the bottom of the datawindow shows blank space.



CR:157773
CR Number:   157773
Product Name:   PB Enterprise
Product Component:   Function Painter
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   5.0.03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
Function painter losing scripts when objects passed in through an argument are not in the library list.





This happens, for example, when an argument to the global function is a user defined object (structure, window) contained in a library not on the library list. (could be an object function too)



The message you'll get when you try to re-open the function:w



Open of function f_anymath failed. Possible Causes:



1. Object has been deleted.

2. Its ancestor has been deleted.

3. An object it references has been deleted

4. Object was created with a newer version of Powerbuilder.



Migrating after adding the missing PBLs containing the missing objects does not fix the problem. If you export the object or global function, you'll see there is no script in it.



CR:157775
CR Number:   157775
Product Name:   PB Enterprise
Product Component:   Source Control
Status:   Closed
OS:   MS Windows NT 3.51
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Apr 1998 Fixed
Description
PBLIB050 & 60. PBNative Source Clear Checkout Status always returns false internally. This results in log message "RC=Failure" instead of "RC=Success".





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

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

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

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

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

各种误操作:

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

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

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


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

Sybase ASE数据库恢复工具READSYBDEVICE:

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

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

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

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

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


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

SQL Server数据库恢复工具SQLRescue:

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

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

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

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

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

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

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