Sybase数据库技术,数据库恢复

• 首页
• 关于
• 订阅
• 归档
• 留言
• 标签
• 免费ASE测试环境
• 镜像站
• 恢复工具

CR:169977

CR Number:   169977 Product Name:   PB Enterprise Product Component:   DW - Runtime Status:   Closed OS:   Microsoft Windows 98 Original Version:   6.0.01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product Description PFC-help mentions for the n_cst_dwsrv object in the function of_GetObjects description : dwcontrol.instancename.of_GetObjects ( objectlist[ ] {, objecttype, band, visibleonly } ). ... see case notes

CR:169983

CR Number:   169983 Product Name:   PB Enterprise Product Component:   Language - Runtime Status:   Closed OS:   MS Windows NT 4.0 Original Version:   6.0.01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12 Dec 2000 Presently Not Targeted For Any Future Release Of This Product Description calling "post open(w_response)" in a script causes a Dr. Watson ( 0x000005 0x10c8beea ) w_response wi_response post open(wi_response) instead of post open(w_response) Workaround Description  use: w_response wi_response post open(wi_response) instead of post open(w_response)

CR:169996

CR Number:   169996 Product Name:   PB Enterprise Product Component:   DW - Runtime Status:   Closed OS:   Microsoft Windows 95 Original Version:   6.0.01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 30 Sep 1998 Presently Not Targeted For Any Future Release Of This Product Description AcceptText in a dw LoseFocus event causes an infinite loop on a validation error. Per Development: This is a problem with running the ue_accepttext event when the DataWindow control has focus. By running AcceptText(), the validation is triggered again, which pops up a message box, which causes the control to lose focus, which run the LoseFocus() event which posts another event. In 5.0, the ue_accepttext event ended up running while the message box was up, so the DW did not have focus. The fact that the event ran while the message box was up was a bug that was fixed in 6.0 (it was causing lots of problems). Coding the event in this way is incorrect for 6.0. A way of fixing it in the PowerScript would be to keep track of whether the DW has focus (using an instance variable and the GainFocus()/LoseFocus() events) and not running the AcceptText() in ue_accepttext if the DW has focus. I tried this solution in the supplied example and it fixed the problem. Workaround Description  Inhibit the PowerBuilder validation error by using Return 1 in the ItemError event. Put up a respose window instead of a messagebox. But with this you lose all the datawindow validation error messages. Ugly.

CR:169998

CR Number:   169998 Product Name:   PB Enterprise Product Component:   Automation Status:   Closed OS:   Microsoft Windows 95 Original Version:   6.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 17 Nov 1998 Not a Bug Description Registered an NVO as a PB Automation Server. Method on NVO takes an argument of type DATE by REF. When called from any client application, an error occurs: R0085 Error in reference argument passed to function. Arguments of type DateTime, String, Int ... are ok. Workaround Description  Use DateTime datatype.

CR:170009

CR Number:   170009 Product Name:   PB Enterprise Product Component:   Language - Runtime 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 Application Close event not firing when a datastore is instanciated (5.0.04)

CR:170025

CR Number:   170025 Product Name:   PB Enterprise Product Component:   DW Painter Status:   Closed OS:   Solaris 2.5.1 Original Version:   6.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 05 Aug 1998 Duplicate 29 Jul 1998 Not a Bug Description PB 6.0 on Solaris - Signal Fault when resizing columns in the dw painter. The error is signal fault in critical section signal number:10 signal code: (, fault address:0x5a,pc dd35384, sp: 0xeff430 Abort: core dump Bus Error

CR:170076

CR Number:   170076 Product Name:   PB Enterprise Product Component:   Source Control Status:   Closed OS:   MS Windows NT 4.0 Original Version:   6.0.01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 7.0.00 RC0 4019 18 Jan 1999 Fixed Description Regression: Unable to clear check-out status if the work PBL does not exist (or was renamed), or if the drive letter where the work PBL resides has changed. Error message: "Clearing check out status of library entry failed. Probably library I/O error."

CR:170164

CR Number:   170164 Product Name:   PB Enterprise Product Component:   DB Informix Status:   Closed OS:   Microsoft Windows 95 Original Version:   6.5.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 6.5.00 512 04 Dec 1998 Fixed Description Cust updated a datawindow (based on a table containing a serial column) with an identity column. Then cust used selectBlob function and application crashed in KERNEL32 at 0137 or hang. This can be reproduced on both pb6.0 and pb6.5 build 444 while it worked fine with pb5.0.04 Same test works fine with sql anywhere and pb6.0 or pb6.5 Workaround Description  Should work with two transactions : one to work on all blob column datatype the other to work on all other column datatypes

CR:170175

CR Number:   170175 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 PowerBuilder will give an access vilolation if an array of structures is passed as an argument to ClassName(). The following script will produce the access violation: lstr ls_mystructure[] any la_any la_any= ls_mystructure cb_1.text = classname(la_any) Workaround Description  The following script will work. But the customer wants this functionality to work with an array of structures. lstr ls_mystructure any la_any la_any= ls_mystructure cb_1.text = classname(la_any)

CR:170309

CR Number:   170309 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) 7.0.00 02 Nov 1998 Fixed Description 6.0.00 Regression : edit mask ##.00,allows to type more digits than allowed after the decimal point if the number being entered has only a decimal component (.39, etc). Workaround: Use 0.xx for data entry. That is, enter a zero, then a dot (or comma if your decimal separator is set up as such) then the decimal number. Workaround Description  (Due to limitation size up to 254 characters of the workaround field, see Class issue 201082252)

CR:170311

CR Number:   170311 Product Name:   PB Enterprise Product Component:   Machine Code Exe Creation Status:   Closed OS:   Microsoft Windows 95 Original Version:   6.5.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 09 Feb 1999 Not reproducible with latest version of the product available as of Resolution Date Description Can't generate an exe in Machine code with czech characters. Workaround Description  use p-code.

CR:170316

CR Number:   170316 Product Name:   PB Enterprise Product Component:   Language - Runtime Status:   Closed OS:   MS Windows NT 4.0 Original Version:   6.0.01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 6.5.00 21 Sep 1998 Fixed Description 6.0.00 Regression. PB 6.0 is using significantly more memory than PB 5.0 when using visible datawindows. (virtual memory)

CR:170324

CR Number:   170324 Product Name:   PB Enterprise Product Component:   Debugger Status:   Closed OS:   Microsoft Windows 95 Original Version:   6.5.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 08 Oct 1998 Not a Bug Description Customer's application consists entirely of approximately 90 response windows. The response windows have coordinates and size explicitly set to maximum size. In PB 5.0 he was able to use the debugger with this application. Basically in PB 5.0 the debug window comes up in front of the application window so you can choose to step through, continue...... In PB 6.0_251 through 6.5_444 the debugger window comes up behind the application's response window and as the response window is maximized the application is essentially frozen and the customer cannot step through the debugger. If the response window is not a maximized size you can put focus on the debugg window by clicking the debugger in the background. Although, doing this allowed me access to the debugger's window it still left the response window on top. Other observed wrong behavior is that it allowed me to close the response window by clicking the X in the upper right hand corner which resulted, not surprisingly, in an invalid page fault in module PBVM60.dll at 0137:10c84b0. Tested this with several types of windows with results as follows: Response windows - debugger comes up behind response window Popup window - debugger comes up behind popup window Main window - debugger comes up in front of main window. Workaround: Make sure response window is small enough while in development to 'grab' debugger window behind it. Workaround Description  Open Response window smaller than maximum size and 'grab' focus onto debugger's window in background.

CR:170366

CR Number:   170366 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.2 22 Sep 1998 Fixed Description 6.0.00 Regression. The currentrow parameter of the rowfocuschanged event on a re-retrieval (2nd retrieval) ON A SHARED DATAWINDOW (using Sharedata()) is 0 in 6.0.00 where it was 1 in previous versions specifically when the execution is in the following order: 1. Retrieve (currentrow = 1 after retrieve) 2. Change the current row (click on row 2) 3. Retrieve again (currentrow changes to 0 instead of 1 in 6.0.00 and 6.5.00) Workaround Description  Reinitialize the dataobject after the sharedatoff () and before the retrieve on the datastore will involve a rowfocuschanged event fired wwith currentrow=1

CR:170374

CR Number:   170374 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) 31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product Description Enhancement: CheckBox default value of Check/Uncheck in DataWindow painter like the CheckBox control has a property: Checked.

CR:170506

CR Number:   170506 Product Name:   PB Enterprise Product Component:   DW Display Status:   Closed OS:   HP-UX 10.20 Original Version:   6.0.01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 6.5.00 28 Jan 1999 Presently Not Targeted For Any Future Release Of This Product Description Accessing column information from a child datawindow within a nested report via dot notation causes large amounts of memory to be allocated. On Windows 95 and on NT4.0 the memleak_3.pbl test case is leaking about 4.2M of memory per 10K of test case loop iterations or about 420 bytes per loop on average. On the HPUX machine it is leaking at about the rate of 5.4M per 10K iterations or 540 bytes per loop on avarage. On all three platforms I observed some very interesting behavior: When I first bring up PowerBuilder and start the test case, it starts leaking right away and continues to leak through out the first test run. For example on the HPUX, memory would initially be at 7.3M for PB06.exe and after 10,000 iterations the memory usage would 12.7M. If I then exited the test case execution, returned to the development environment, and then restarted the app, memory usage is still at 12.7M. But now when I run the app it does not leak until around the 10,000th iteration! Then it starts leaking again at the same rate as before. So it appears that in between executions the memory that was 'leaked' or used is reclaimed by PB. It does not return it to the operating system, but keeps it internally and is able to reuse it. But it is not able to reclaim this memory during the execution of a single test session, even when the app is idling. I can suspend the loop iteration and idle, but no memory is reclaimed. Resuming the test loop at this point continues the leak. So knowing this, the best way to always see the leak is to shut down PowerBuilder and restart it, then the test case will leak from the start. Otherwise any given test case run is dependent on the previous highwater mark of memory usage in the same PB session before it will start to leak again. I've simplified the test case and can also see the memory leak with a simple nested report created from the demo db. The test case has a main datawindow with 1 row of data, and a nested report with one row of data. No database connection is needed, the datawindows have data retained on save. The script is a tight loop that simply assigns a string to a column in the nested report using dot notaion. The leak is isloated to the line of script that is dot notating into the nested report and assigning a string to a column in the nested report: . dw_1.object.d_emp[1].object.emp_fname[1] = "ABCabcDEFdef" . If the line assigning the string to the dot notated column is commented out, it does not leak. The leak is related to the fact that the report is nested, if the nested report is put into the main datawindow control, dot notating to the same column no longer leaks. The size of the column does not seem to matter, very large columns and small columns all seem to leak. Also, the size of the string being assigned does not seem to be a factor, even assigning an empty string ("") leaks. . The problem is not related to visual processing, using a datastore leaks, and setting SetRedraw to false with a datawindow still leaks. The advantage of setting SetRedraw to false really speeds up the test case. It gets to the leak quickly and the leak is quite dramatic. There is often a delay for several seconds when starting the test (while the test loop is iterating) before the leak is apparent. I can only assume that PB has an internal memory pool and when the pool is exhausted it requests more free memory from the operating system. Once this initial threshold is reached, the leak is apparent, and rapid as PB keeps requesting memory and never returning any. . I also tested this new test case on both the Windows 95 and NT4.0 platforms. With this test case I'm also seeing a significant leak on both of these platforms as well. It seems to be a smaller leak on these platforms, but it is clearly leaking.

CR:170519

CR Number:   170519 Product Name:   PB Enterprise Product Component:   DW Painter Status:   Closed OS:   MS Windows NT 4.0 Original Version:   6.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 6.5.00 17 Nov 1998 Not reproducible with latest version of the product available as of Resolution Date Description Having 2 stacked (in the y-direction) nested reports - with autosizeheight set ON - in the main header band of a datawindow causes the application to hang if the user tries to scroll using the thumb after playing with the zoom factor of the datawindow. Workaround: Turn off autosizeheight for both the nested reports in the header.

CR:170526

CR Number:   170526 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 Concatenating several calls to the Oracle function NVL() will cause a GPF in PBOR860.DLL when the number of NVL() calls concatenated in one line of a SQL select goes above 4 (in this example, but this number may vary). Address in PBOR860.DLL can vary a little. 0137:02026100 0137:02066100 0137:01ffc6100 The following SQL sentence causes a GPF SELECT nvl("TABLE_NAME"."COL_NAME",0) + nvl("TABLE_NAME"."COL_NAME",0) + nvl("TABLE_NAME"."COL_NAME",0) + nvl("TABLE_NAME"."COL_NAME",0) + nvl("TABLE_NAME"."COL_NAME",0) FROM "TABLE_NAME"

CR:170547

CR Number:   170547 Product Name:   PB Enterprise Product Component:   DW Display Status:   Closed OS:   MS Windows NT 4.0 Original Version:   6.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 6.5.00 459 16 Dec 1998 Fixed Description 6.0.00 Regression. Datawindow scrolling using the thumb on the vertical scrollbar - with print preview OFF - is showing blank spaces (missing rows) for the row that is just beyond the bottom of the datawindow control visual area while scrolling. The blank areas (rows) recur at intervals exactly equal to the height of the datawindow. Most often happens with datawindows with groups in development and runtime but the printout is OK. Nothing seems to get rid of the blank areas during display (setredraw, etc). Development: There is a gap at the end of the page of grouped reports, where the next row does not fit and is pushed to the next page. This gap is still visible as the display is scrolled -- but no rows are missing. However, we did make a change to the group display. If the display is scrolled, a page separator (single line) is drawn between the two pages. This is an attempt to show that the gap is intentional, and the space is supposed to be blank. This line is not printed.

CR:170632

CR Number:   170632 Product Name:   PB Enterprise Product Component:   Jaguar Integration Status:   Closed OS:   MS Windows NT 4.0 Original Version:   6.0.01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 23 Apr 1999 Not a Bug Description Jaguar server crashes when there are multiple client sessions from the same client. Access is via ODBC.

CR:170646

CR Number:   170646 Product Name:   PB Enterprise Product Component:   DPB 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 DPB Deadlock - Server push to busy client can cause deadlock. It happens when the server post's a push to a busy client and the client triggers another server call before the posted push call executes. Workaround: the deadlock can be avoid by the client posting calls to the server. Workaround Description  Workaround: the deadlock can be avoid by the client posting calls to the server.

CR:170685

CR Number:   170685 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) 5.0.04 22 Sep 1998 Fixed Description Regression : DW Date and Datetime EditMask mmm-yy cannot work with year 00 (year 2000), the field displays -00 (null)

CR:170686

CR Number:   170686 Product Name:   PB Enterprise Product Component:   Project Painter 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 Feature Request: Add a feature in the project painter to specify the target location (directory) of PBD's and DLL's, not just the executable.

CR:170748

CR Number:   170748 Product Name:   PB Enterprise Product Component:   Language - Compiler Status:   Closed OS:   Microsoft Windows 95 Original Version:   6.5.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 6.5.00 521 16 Sep 1999 Fixed Description 6.5 Regression: Full Rebuild of PFC / Cornerstone application fails in 6.5

CR:170758

CR Number:   170758 Product Name:   PB Enterprise Product Component:   Pipeline - Runtime Status:   Closed OS:   Microsoft Windows 95 Original Version:   5.0.04 Fixed Version Build Resolution Date Closure Code (If Appropriate) 6.5.00 522 30 Dec 1998 Fixed Description 5.0.04/6.0 Regression: Executing a Pipeline at runtime, correcting any errors and then executing the Repair() function causes a page fault in PBSHR050.DLL@0137:11133A4A or PBVM60.DLL@0157:10B55F7D.

CR:170883

CR Number:   170883 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 Variable of type 'any' that is NULL is not handled in the right way with the SetDynamicParm function. This causes different SQLErrText messages. SQLDA.SetDynamicParm will return a -1 when you try to pass a any varibale with NULL. When you try the same thing with a integer variable with NULL it will work and the function return a 1. Workaround: cast the any varibale into the rigth datatype and it works. ex. SetDynamicParm(1,integer(my_any_variable)) Workaround Description  Workaround: cast the any varibale into the rigth datatype and it works. ex. SetDynamicParm(1,integer(my_any_variable))

CR:170913

CR Number:   170913 Product Name:   PB Enterprise Product Component:   Window - Runtime Status:   Closed OS:   Microsoft Windows 95 Original Version:   6.5.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 07 Dec 1998 Not reproducible with latest version of the product available as of Resolution Date Description Treeview SelectionChanging firing twice when dragdrop enabled

CR:170917

CR Number:   170917 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) 04 Nov 1998 Fixed Description 5.0.04/6.0.00 Regression. Dynamic Protected functions cause a runtime error in 5.0.04, 6.0.00 & 6.5.00. They do compile. This worked in PB5.0.03. Protected means the function of the ancestor should be able to be called in a descendent BOTH directly OR using the keyword DYNAMIC. In 5.0.04, 6.0.00 and 6.5.00, the call in the descendent for the PROTECTED function works when called directly but doesn't when using the keyword DYNAMIC. This is incorrect. For a PROTECTED function called from a descendant, the DYNAMIC keyword seems to cause a runtime error and treats these function calls as if the ancestor function was declared as PRIVATE. This was probably caused by the fix to 163944. R0065 Application terminated. Error: Dynamic function not found. Possible causes include: pass by value/reference mismatch...

CR:170967

CR Number:   170967 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) 6.5.00 16 Dec 1998 Fixed Description When in the control panel the comma is set as decimal separator, PowerBuilder 6.5 crashes on a print preview of any rte datawindow. It crashes also on a print preview of a rich text control when calling rte_1.preview(true). This problem does not exist in PowerBuilder 6.0

CR:171026

CR Number:   171026 Product Name:   PB Enterprise Product Component:   DW Edit Mask Status:   Closed OS:   Microsoft Windows 95 Original Version:   6.5.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 7.0.00 13 Nov 1998 Fixed Description PB 6.5 Editmask doesn't allow the input of negative values (minus sign) when having the numbers highlighted (selected).Edit MAsk is set to #,###,###,##0.00. Result: You'll get a beep and NO minus sign is going to be displayed.

CR:171027

CR Number:   171027 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) 03 Sep 1998 Presently Not Targeted For Any Future Release Of This Product Description SetRow not working when all columns protected and have a non-zero tab order. This will not be fixed: Per Development: This has always been the behavior for PB and would be too risky for Development to attempt a code change at this point. If this was done, it would have the potential to break too many existing applications that depend on the current behavior. Workaround Description  In some cases the following work arounds may help if you are able to do them: 1) Set the all column tab orders to zero. 2) Use ScrollToRow() instead of SetRow()

CR:171033

CR Number:   171033 Product Name:   PB Enterprise Product Component:   DW Display Status:   Open OS:   Microsoft Windows 95 Original Version:   6.5.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description Enhancement req for null value support in EditMask and option to enter NULL

CR:171038

CR Number:   171038 Product Name:   PB Enterprise Product Component:   DW Expression 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 25 Apr 2005 Presently Not Targeted For Any Future Release Of This Product Description 6.5.00 Regression. The real() and Double() functions (both Powerscript and Datawindow) do not convert numbers that have European format separator for decimal (the comma). The string '1,225' passed to each of these functions (with Regional Settings for Number in control panel set for comma decimal separator) return "1" instead of 1,225. Workaround: The decimal() function seems to work OK and might be an acceptable workaround in Powerscript (but not in the dw painter functions)

CR:171051

CR Number:   171051 Product Name:   PB Enterprise Product Component:   DW Painter Status:   Closed OS:   MS Windows NT 4.0 Original Version:   6.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 09 May 2000 Not a Bug Description Enhancement Request: Customer would like to have an additional menu option added to the Edit...Size Objects that makes objects both the same height and the same width just to make it quicker to make a bunch of objects exactly the same size, rather than having to do the height and the width in two separate steps.

CR:171071

CR Number:   171071 Product Name:   PB Enterprise Product Component:   DW - Runtime Status:   Closed OS:   MS Windows NT 4.0 Original Version:   6.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 6.5.00 475 16 Dec 1998 Fixed Description 5.0.04/6.0.00 Regression. Rows/Page for Data tab of Graph object on datawindow causes ObjectatPointer() to fail. Rows/All for Data Tab works and ObjectatPointer() returns correct values. The graph object does not have "size to display" on.

CR:171073

CR Number:   171073 Product Name:   PB Enterprise Product Component:   Source Control 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 ENHANCEMENT REQUEST: It would be nice if PB or PVCS informed the user that an ancestor or a descendant of the object is also checked out.

CR:171096

CR Number:   171096 Product Name:   PB Enterprise Product Component:   DW SaveAs Status:   Closed OS:   Microsoft Windows 95 Original Version:   6.5.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 7.0.00 2226 19 Nov 1998 Fixed Description The properties HtmlTable.CellSpacing=0, CellPading=0, Width=100% are not working. The values are not included in the HTML. When you set Cellspacing and Cellpading to 0 these two settings are not included tin the HTMLTable when you save a dw. The Browser automaticly build a table with Cellspacing and Cellpadding = 1. When you spacify Cellspacing = 0 and Cellpadding = 0 in the HTML code the browser build a table with smal lines. ct like to be able to set the spacing and padding to 0 and this should be placed in the HTML script of a dw. Workaround Description  insert Cellspacing = 0 and Cellpadding = 0 in the html string before you save the html document.

CR:171100

CR Number:   171100 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 DataWindow sort order--- if you have a string with a dash in it, the DataWindow will not sort it correctly. DataWindow seems to be ignoring the dash. Resolution from development: This is sorting as it should ... In Win32 the compare that we're doing internally intentionally ignores hyphens (-) and apostrophes (') (this is called a word sort as opposed to a string sort). To do otherwise would have to be an enhancement . Workaround: To achieve a sort taking the leading "-" or "+" into account add the column you would like to sort that includes the "-" hyphens twice - assume it's called col1. Doubleclick on the first instance of col1 in sort dialogue and modify the expression as follows ( left(col1,1)). Check off sort order and leave the second instance as simply the column name. This will sort on the first character first and then on the entire column resulting in a sort that takes into account the leading "-" or "+".

CR:171105

CR Number:   171105 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) 7.x Catalina 13 Apr 2000 Fixed Description Using an editmask of ###.00, if the column of the datawindow is not large enough at runtime for the mask to fit, the editmask behaves strangely. Warning beeps occur, the cursor does not move consistently, and when you tab away the data will be incorrect. WORKAROUND: Either make the column larger (usually only wider is necessary) or the font smaller, so that all of the data can be easily displayed during data entry.

CR:171151

CR Number:   171151 Product Name:   PB Enterprise Product Component:   Documentation Status:   Closed OS:   MS Windows NT 4.0 Original Version:   6.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 24 Sep 1998 Not a Bug Description InfoMaker User Guide missing from 6.0.00 box. NOTE: For customers wanting a User Guide, please see page x in the InfoMaker Getting Started book. As in 5.0, the User's Guide is not packaged with the product. It can be ordered by calling the number on page viii.

CR:171152

CR Number:   171152 Product Name:   PB Enterprise Product Component:   DW - Runtime Status:   Closed OS:   MS Windows NT 4.0 Original Version:   6.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 6.0.01 18 Aug 1998 Fixed Description 6.0.00 Regression. In the itemchanged event, if you change an attribute of a column - some examples: dw_1.object.dept_id.dddw.required='yes' dw_1.object.dept_id.background.mode='0' dw_1.object.dept_id.background.color=rgb(192,192,192) You get a GPF in MSVCRT.DLL

CR:171177

CR Number:   171177 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 The properties HtmlTable.Width should be able to become a value in % like htmltable.width = 100%

CR:171191

CR Number:   171191 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) 07 Jan 1999 Presently Not Targeted For Any Future Release Of This Product Description 5.0.04/6.0.00 Regression. Syntaxfromsql using JOINs prefixes the column names incorrectly for native drivers and in some cases ODBC if the user is a non-owner of the tables. Prior to 5.0.04, the column name would be prefixed with the table name. Ex: Select emp_id dept_name from employee, department where employee.dept_id = department.dept_id Should product column names of: 'employee_emp_id' and 'department_dept_name' exactly what you'd see if you created a datawindow in the painter and looked at the 'default' assigned column names in design mode. Instead, it produces 'cemp_id' and 'cdept_name'. This was an old behavior with Oracle but now this has migrated to all drivers (in this case SYC). Even with using the correct USERID prefixing, there is no way at runtime or in development to get the correct names. This is definitely related to CR 161648. Workaround: Prefix the tables in the FROM clause with their owner. Ex: Select emp_id, dept_name from employee, department where employee.dept_id = department.dept_id becomes Select emp_id, dept_name from dba.employee, dba.department where employee.dept_id = department.dept_id Per Development: This will not be fixed, you must use the workaround.

CR:171248

CR Number:   171248 Product Name:   PB Enterprise Product Component:   DW Edit Mask Status:   Closed OS:   Microsoft Windows 95 Original Version:   6.5.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 28 Sep 1998 Fixed Description Regression in 6.5.00 When the decimal separator is set to a comma in the control panel, an Edit Mask Control shows value 1,00 in the display when the text value was set to value 1,25 ; i.e. no fractional part when using Real() or Double() PowerScript functions to convert the string 1,25. String (real (sle_real.text)) An editmask on a datawindow column has the same behavior when using the Real() and Double() report functions in the datawindow as computed fields.

CR:171256

CR Number:   171256 Product Name:   PB Enterprise Product Component:   Inheritance Status:   Closed OS:   MS Windows NT 4.0 Original Version:   6.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 6.5.00 491 04 Nov 1998 Not reproducible with latest version of the product available as of Resolution Date Description Incremental rebuild after changing an ancestor slightly - even adding a comment - is broken for 6.0.00. If you use incremental rebuild in the library painter, you get dozens of object not found errors, etc even through just before the change incremental rebuild found no errors. Workaround: Full Rebuild.

CR:171269

CR Number:   171269 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) 5.0.04 02 Feb 1999 Fixed Description On a PowerBuilder SYC connection, connecting takes a long time if the SYSALTERNATES table contains many entries. Workaround Description  Avoid user aliases

CR:171324

CR Number:   171324 Product Name:   PB Enterprise Product Component:   DW - Runtime Status:   Closed OS:   MS Windows NT 4.0 Original Version:   6.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 6.5.00 01 Dec 1998 Fixed Description The Group Sort for a datawindow with groups does not work for any group > 1. It does work for the first group. Workaround: Use a nested report instead of a second group on one report. The parent report would define the first group (you might have to change the SQL statement and use DISTINCT). The nested report would contain the original 2nd group but have this as it's first and only group. An example can be given to all customers by using the PBL for this bug (it's much easier to see than to explain). The problem with this workaround is it creates a nested report which will have the "1 page per detail row" limitation (and this could cause problems with some reports where the nest flows beyond one page) NOTE: This has been fixed in 6.5 and above. Any build after 500 should work. For example 6.5.1 build 620 and above should work.

CR:171334

CR Number:   171334 Product Name:   PB Enterprise Product Component:   DW Display Status:   Closed OS:   MS Windows NT 4.0 Original Version:   6.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 6.5.00 212 16 Dec 1998 Fixed Description A Group datawindow with one or more datawindow groups defined has painting problems when placed in a composite or nested report and the user scrolls down through about 1/3 the pages (almost exactly 1/3) with 2 groups or to the last page of the report with 1 group. This doesn't happen if the same group report (in print preview) is not placed in a composite or nested. The painting problem shows ghosting and an overlap of information. This happens in the datawindow painter print preview or at runtime in an application.

CR:171335

CR Number:   171335 Product Name:   PB Enterprise Product Component:   Language - Runtime Status:   Closed OS:   MS Windows NT 4.0 Original Version:   6.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 6.5.00 09 Dec 1998 Fixed Description 6.0.00 Regression - External function call returning a long and 2 structures passed by reference causes a page fault in: pbvm60.dll@0157:10cf2294 or 0157:10cf2598 or on NT a Dr. Watson occurs 0x0000000b.

CR:171387

CR Number:   171387 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 If you create a crosstab dw (three integer columns who are primary keys) it shows in special cases some values on the wrong place. In the db are three columns of integer and one of type money. The three integer columns are the primary key. Crosstab dw definition: define the first integer = column, and the 2. and 3. integer are rows. Value is the sum of the money . Now in some special cases when the column (first integer) is equal to the 2. integer row the crosstab dw mixed the values of the integer rows. Workaround: Insert a computed column between the two rows and make it invisible Workaround Description  Insert a computed column between the two rows and make it invisible

CR:171392

CR Number:   171392 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) 08 Oct 1998 Not a Bug Description Informix IN7 to ANSI DB with DisableBind=1 gives SQL error -280 : A quoted string exceeds 256 bytes. Workaround Description  use binding (DisableBind=0)

CR:171398

CR Number:   171398 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) 7.x Catalina 1019 08 Nov 2001 Fixed 25 Feb 2004 Fixed Description dw_1.Object.DataWindow.Printer is used to get the name/path of the default printer. This name/path is more than 73 characters long and is cut off in Win95. There are no problems using NT 4.0. Workaround Description  Don't use long sharenames.

CR:171403

CR Number:   171403 Product Name:   PB Enterprise Product Component:   DW - Runtime Status:   Closed OS:   MS Windows NT 4.0 Original Version:   6.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 07 Apr 2000 Fixed Description 6.5.00 Regression. The assignment of a datawindow datetime column to a structure element of type date using dot notation fails in 6.5.00. A datawindow date also fails assigned to a to a corresponding structure element of datetime. Both failed in 5.0.03 and 5.0.04 but was fixed in 6.0.00. The runtime error is R0049 Type Mismatch (development or runtime). Now 6.5.00 has this not working again. Strangely, the assignment of a structure element of type datetime to datawindow column date using dot notation works as does assigning a structure element of type date to a datawindow column of datetime. Workaround: Use exactly matching datatypes.

CR:171413

CR Number:   171413 Product Name:   PB Enterprise Product Component:   DW Painter Status:   Closed OS:   MS Windows NT 4.0 Original Version:   6.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product Description Enhancement to SQL painter: The datawindow painter has a built in functionality (for new users) to automatically create a JOIN between like named columns if two tables are selected whether or not there is an actual primary key/foreign key relationship. This is a nice feature in most cases. But, there is no way for the user to - and this is important - easily see - the difference from JOINs that are REAL and joins that the painter is "assuming". This can cause problems in datawindows that will cause table scans, etc.

CR:171425

CR Number:   171425 Product Name:   PB Enterprise Product Component:   Generators 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 221 31 Oct 2002 Fixed Description The PB COM Generator connot handle a NVO that contains user object functions that take more than 15 arguments. The generator will crash when you attempt to generate COM objects for such classes.

CR:171426

CR Number:   171426 Product Name:   PB Enterprise Product Component:   Menus - Runtime Status:   Closed OS:   MS Windows NT 4.0 Original Version:   6.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 6.5.00 15 Dec 2000 Fixed Description 6.0.00 Regression. The opensheet function using a non-zero position argument causes the sheet list to appear under the FIRST (normally File) top level menu item. In the simple example of File....Edit....Window....Help, if the opensheet call uses position 3 (Window) and the open event of the sheet makes "Edit" invisible, the sheet list should still appear under Window - it now appears under File. This appears to be related to 161211 which was fixed in 6.5.00. The fix for that bug seems to have also fixed this particular offshoot.

CR:171430

CR Number:   171430 Product Name:   PB Enterprise Product Component:   OLE - Active X - OCX Status:   Closed OS:   MS Windows NT 4.0 Original Version:   6.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 6.5.00 461 04 Jan 2001 Fixed Description OCX built in VB, function call causes error: R0033 Invalid parameter type calling external object function. The argument sent to the function TestMethod (ref long i) is correct according to the information in the PowerBuilder browser.

CR:171454

CR Number:   171454 Product Name:   PB Enterprise Product Component:   Script Painter Status:   Closed OS:   MS Windows NT 4.0 Original Version:   7.0.00 Beta 1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 30 Nov 1998 Fixed Description Enhancement request to include the object functions for Windows, Menus, and User Objects into the script painter as a drop down.

CR:171455

CR Number:   171455 Product Name:   PB Enterprise Product Component:   DW Painter Status:   Open OS:   MS Windows NT 4.0 Original Version:   7.0.00 Beta 1 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description Enhancement - include dw button objects into tab sequence in dw painter

CR:171471

CR Number:   171471 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.0.00 22 Oct 1998 Not reproducible with latest version of the product available as of Resolution Date Description Performing GetFullState on a datastore that has a composite/nested datawindow object and then performing SetFullState() to a datawindow that already has an existing datawindow object will cause the following errors: Under Win95: "PB60 caused an invalid page fault in module PBDWE60.DLL at 0157:115e83fa. " Under WinNT: "The instruction at 0x115e83fa referenced memory at 0xd0000005e. The memory could not be written" Only occurs when performing the above with a standalone application - does not occur with a distributed application where the GetFullState() is done on the server and the SetFullState() is performed on the client.

CR:171546

CR Number:   171546 Product Name:   PB Enterprise Product Component:   Documentation Status:   Closed OS:   MS Windows NT 4.0 Original Version:   6.5.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 01 Sep 1998 Duplicate Description The PowerBuilder 6.0 and 6.5 help files does not display an alphabetical list of DataWindow object properties, a blank screen is displayed instead.

CR:171548

CR Number:   171548 Product Name:   PB Enterprise Product Component:   DW Edit Mask Status:   Closed OS:   Microsoft Windows 95 Original Version:   6.5.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 13 Oct 1998 Fixed Description 6.5 Regression When the control panel the decimal separator is set to a comma : When entering data in a Float or Real type datawindow Column, the fractional part is lost when tabbing to the next column. Columns of type Double or Number do not have this behaviour. It happens also in preview in the database painter.

CR:171581

CR Number:   171581 Product Name:   PB Enterprise Product Component:   Preference Painter Status:   Closed OS:   MS Windows NT 4.0 Original Version:   6.5.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 22 Oct 1998 Presently Not Targeted For Any Future Release Of This Product Description 6.5.00. System Options for 6.5 is still writing/reading information to the 6.0 registry entries. It's writing information, (for example, initpath or initialization path) to the following key: HKEY_CURRENT_USER\Software\Powersoft\PowerBuilder\6.0\initpath The PowerBuilder 6.5 environment seems to work OK. The profiler.exe seems to want to read from the '6.5' key: HKEY_CURRENT_USER\Software\Powersoft\PowerBuilder\6.5\initpath Change Request 171575 addresses that.

CR:171641

CR Number:   171641 Product Name:   PB Enterprise Product Component:   Window - Runtime Status:   Closed OS:   Microsoft Windows 95 Original Version:   6.0.01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 6.5.00 478 21 Oct 1998 Fixed Description 6.0.00 Regression. The Yield() fiunction has no effect when executed from the application open event. Workaround Description  Instead of the lopp in the application open event, create an application function and post its execution.

CR:171672

CR Number:   171672 Product Name:   PB Enterprise Product Component:   DW Edit Mask Status:   Closed OS:   Microsoft Windows 95 Original Version:   6.5.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product Description When the SystemError event is triggered by a dw column with an editmask and either the SystemError event script closes the window or does a Halt Close and the application close event has script in it (even a comment), you will get an Invalid Page Fault. With PB 6.5 the Illegal Page Fault was in module PBVM60.dll at 0137:10baef24. If the column that triggers the SystemError does not have an editmask the Illegal Page Fault does not occur.

CR:171705

CR Number:   171705 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 06 Jan 1999 Duplicate Description 6.5 Regression : Crosstab crashes when three columns in "Crosstab Columns" dialog.

CR:171725

CR Number:   171725 Product Name:   PB Enterprise Product Component:   DW Expression Status:   Closed OS:   MS Windows NT 4.0 Original Version:   6.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 7.x Catalina 1019 13 Apr 1999 Fixed Description Enhancement: Page(), Pagecount() and PageAcross() datawindow functions return INT. They should return LONG. This can only be accomplished in a full release (since it requires a migration).

CR:171731

CR Number:   171731 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) 6.5.00 494 10 Nov 1998 Not reproducible with latest version of the product available as of Resolution Date Description 6.5.00 Regression. OLE automation GPFs using a simple example.

CR:171771

CR Number:   171771 Product Name:   PB Enterprise Product Component:   Application Painter Status:   Closed OS:   MS Windows NT 4.0 Original Version:   6.5.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 23 Nov 1998 Presently Not Targeted For Any Future Release Of This Product Description There is a 64k limit to the pb.ini. As you exceed this limit and exit out of PowerBuilder, the next time you go back into PowerBuilder, you will get the typical New/Open/Cancel dialog prompt to create a new application. This happens even though your Pb.ini is correct, your "initpath" points to the correct directory, and the pb.ini 'deflib' key - the key powerbuilder uses to open your "default application" on startup is populated with an application that exists on that exact location on your hard drive. It almost seems like when the 64k limit is reached, Powerbuilder 'acts' as if the pb.ini is readonly, missing entirely, or the PBL that the DefApp key points to has been renamed or moved and puts up the New/Open/Cancel dialog for creating a new application. Workaround: Edit your pb.ini and delete applications from the bottom up Look in the [Application] section. The applications begin with a $. Delete until you're way under 64k and you will find Powerbuilder will automatically open up the correct 'DefApp' application on startup again.

CR:171818

CR Number:   171818 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) 17 Jun 2005 Not reproducible with latest version of the product available as of Resolution Date Description The crash is not reproducible in PB9.0.2 Build 7682++ PB 6.5 REGRESSION : Following script causes a crash in 6.5, either immediately or after exiting the application >>> scriptdefinition scriptlist[] variabledefinition argumentlist[] .. argumentlist = ScriptList[119].ArgumentList <<< This problem is related to CR162727 >>> Crash while accessing the properties of created Meta Information variables (EnumerationDefinition, VariableCardinalityDefinition, ScriptDefinition, VariableDefinition) <<<

CR:171844

CR Number:   171844 Product Name:   PB Enterprise Product Component:   DW Painter Status:   Closed OS:   Microsoft Windows 95 Original Version:   6.5.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 23 Sep 1998 Not a Bug Description PB 6.5 Regression. Minor regression as the icon looks disabled but on all machines tested that exhibited the problem the icon actually worked, but you had to click twice. Seems machine dependent. Tested many machines and on some WIN 95 a and b machines it was a problem but on other WIN 95 machines it wasn't. All NT 4.0 machines tested appeared to be fine. When creating a new DW and hit 'X' to close, click cancel to save and the Preview Icon on toolbar is disabled. Design=>Preview works fine and also hitting SQL icon to get out of SQL mode icon is enabled. Even when disabled on machines clicking Icon once changes it from looking disabled to enabled and it worked properly. WORKAROUND: Hit icon twice or exit by hitting SQL icon rather than "X". Workaround Description  Hit icon twice or exit by hitting the SQL icon.

CR:171846

CR Number:   171846 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) 17 Sep 1998 Not a Bug Description When in Pipeline Painter SQL mode the Preview menu bar icon is displayed but is disabled. In PB 6.0_251 this is enabled and allows the user to preview. This icon is also displayed but disabled in PB 5.0 through 5.0.04.

CR:171850

CR Number:   171850 Product Name:   PB Enterprise Product Component:   Installation Status:   Closed OS:   Microsoft Windows 95 Original Version:   6.5.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 05 Nov 1998 Presently Not Targeted For Any Future Release Of This Product Description The 6.5 maintenance file PB65MNT.EXE, that is downloaded from the web, does not "clean up" after the installation. Launching the .exe, it unpacks all the files in a directory. You can choose what directory it unpacks to or it will default to windows\temp. Once the installation is complete, you exit out of the setup program and the files are left behind. What to do: Just delete the files manually from the directory where you directed the program to unpack them.

CR:171864

CR Number:   171864 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) 16 Dec 1998 Fixed Description Regression: Retrieving/previewing a crosstab datawindow which is defined to have multiple columns selected in the "Column" field of the Crosstab definition dialog causes Powerbuilder to either gpf or hang, depending upon the system. This problem did not occur for 5.0.04 and does not occur using 6.0. Upon migration to 6.5, a retrieve of this type of crosstab causes a gpf or causes Powerbuilder to hang.

CR:171892

CR Number:   171892 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) 6.5.00 476 31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product Description Dot notation on nested column attributes causes loss of 2-n result sets. There was a fix put into 5.0.04 for a GPF dealing with dot notation into a true nested report. An undesirable side effect is that the result sets for the first nest is OK (for example, things change color correctly) but after the dot notation, result sets 2-n are lost for the other nested result sets. Another set of bad side effects - any filter() or retrieve() directive seems to break the change. (reads in the original dataobject definition - this is incorrect) examples of the dot notation: dw_1.object.d_employee[1].object.emp_id.color="0~tif( emp_id < 200, 255,0)" dw_1.object.d_employee[1].object.emp_id.font.weight="400~tif( emp_id < 200, 700,400)"

CR:171895

CR Number:   171895 Product Name:   PB Enterprise Product Component:   DB Sybase System Status:   Closed OS:   Microsoft Windows 95 Original Version:   6.0.01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 7.0.00 Beta 3 510? 01 Dec 1998 Fixed Description A SQL PRINT statement executed in the DB Admin painter does not echo the resulting string in PB 5.0.04 and causes a GPF in PB 6.0.00 and PB 6.0.01, 6.5.00.

CR:171897

CR Number:   171897 Product Name:   PB Enterprise Product Component:   Inheritance Status:   Closed OS:   Microsoft Windows 95 Original Version:   6.5.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 6.5.00 491 04 Nov 1998 Not reproducible with latest version of the product available as of Resolution Date Description Simple incremental rebuild of Qckstart PFC application fails with many errors when even a slight change, a comment, is made to an ancestor. May be a duplicate or related to CR171256 with the key difference being that with the Qckstart.pbl application changing the ancestor was successful at an incremental rebuild in PB 6.0 GA. Fails in PB 6.5 build 444 and 446. Workaround: Use Full Rebuild. Workaround Description  Use Full Rebuild.

CR:171901

CR Number:   171901 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) 7.0.00 Beta 3 13 Nov 1998 Fixed Description A Return 1 in the SQLPreview event not working correctly to stop a Retrieve() or Reselectrow() Workaround Description  Use dwcontrol.SetSQLPreview(sqlsyntax) to change the SQL to something that will error, or not return a result set.

CR:171949

CR Number:   171949 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 MDI context no more available if resizable main window property is dynamicly set. This doesn't happen in SDI context...

CR:171961

CR Number:   171961 Product Name:   PB Enterprise Product Component:   DPB 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 Setting the myconnect.options="MaxRetry=15" will cause the client app to hang on a disconnect; myconnect.DisconnectServer() call. Anything 16 and over works, 15 and below will hang. This is a 6.5 regression, it works fine in 6.0. Workaround: Set myconnect.options = "MaxRetry=16" or anynumber > 16. Workaround Description  Set myconnect.options = "MaxRetry=16" or anynumber > 16.

CR:171974

CR Number:   171974 Product Name:   PB Enterprise Product Component:   Language - Runtime Status:   Closed OS:   Microsoft Windows 95 Original Version:   6.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 6.5.00 496 10 Nov 1998 Fixed Description Using LibraryImport() with syntax generated from SyntaxFromSQL or from a hardcoded string within the script generates an Illegal Page Fault on WIN 95 or an Unhandled Exception on NT when the window did not have a dw control on it. When using LibraryImport() with syntax generated from Describe() this problem did not occur. This window would naturally have a dw control on it. In fact in the Development environment, using LibraryImport() with the syntax from Describe() prevented the page faults with the previous two methods of generating the SQL even when the active pbl was changed. If the PB development environment was exited and re-entered the page faults reappeared. Behavior was consistent with above in an executable version. Workaround: Place a empty invisible DW control on window. Workaround Description  Place a empty invisible DW control on window.

CR:172020

CR Number:   172020 Product Name:   PB Enterprise Product Component:   DB Informix 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 21 May 1999 Fixed Description Informix ANSI DB Create Table dialog pops up when trying to alter existing table

CR:172021

CR Number:   172021 Product Name:   PB Enterprise Product Component:   DW - Runtime Status:   Closed OS:   Microsoft Windows 95 Original Version:   6.0.01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product Description PB 6.5 Regression A crash occurs when both the 'other' event and the 'clicked' event of a datawindow with a button in it, has been coded or contain comments. The crash occurs when clicking the button.

CR:172022

CR Number:   172022 Product Name:   PB Enterprise Product Component:   Project Painter 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 Enhancement. Project painter puts up a dialog when it finds an error or warning rather than continuing on with the compile and presenting the errors at the end. Also, PowerBuilder should be able to log warnings and informational messages to a file instead of promting the user to continue when displaying the error dialog after the Rebuild is finished and just before the actual compilation occurs. There should be some sort of "Silent Compile." This is a case where the user wants to see the warnings or errors (IE they don't want to UNCHECK showing of Information or Obsolete Messages in the Design/Options menu of the Project Painter (7.0)) but they don't want them to be shown - perferably with an option to log to a file - until after the exe is created. (esp if the messages are just warnings) If the project is run as an automated process (through a tool such as sqa robot), there is no way to continue on until a user actually responds to the messagebox which makes it hard to automate overnight builds and running of regression suites afterwards. A batch mode compile would also be nice.

CR:172026

CR Number:   172026 Product Name:   PB Enterprise Product Component:   DW Synchronization Status:   Closed OS:   MS Windows NT 4.0 Original Version:   6.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 7.0.00 Beta 3 08 Jan 2002 Fixed Description Using the same dataobject, if you use the datawindow synchronization functions to synchronize changes and then Update, the SQL statement generated will update all updateable columns of the datawindow rather than just the modified column(s). If you make the same data changes to a standalone datawindow using the same datawindow object and issue an update, only the column that actually changed is updated on the database. This is not critical because the resulting data is the same, but there could be a performance impact. Checking with development to find out whether this difference was implemented by design.

CR:172050

CR Number:   172050 Product Name:   PB Enterprise Product Component:   DB DB2 Status:   Closed OS:   Microsoft Windows 95 Original Version:   6.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 6.5.00 10 Sep 1998 Fixed 6.5.00 554 11 Feb 1999 Fixed 6.5.00 614 26 Apr 1999 Fixed Description Autocommit is not working in pbnet050.dll and pbnet60.dll for System 11x servers. CR164967 originally put in support for long transactions, but had to check to make sure that we were working with release 3.0 or higher of Sybase Net Gateway. We did this by checking the first byte of the version number only.

CR:172064

CR Number:   172064 Product Name:   PB Enterprise Product Component:   DW Printing Status:   Closed OS:   MS Windows NT 4.0 Original Version:   6.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 6.5.00 17 Nov 1998 Third Party Problem Description NT only: If you set the default text color for your system to something other than black and then print a Crosstab datawindow, the data itself does not print. You end up with a printout of gridlines with empty cells. PER DEVELOPMENT: (Nov. 17/98): this issue is dependent on the printer driver and its configuration settings; I printed the sample on a desktop Canon and on a HP 4Si LaserJet (using a PostScript driver); I received gray-scale print on the Canon and black print (on all columns) on the HP; if the printer can handle gray-scale printing then it will turn colors into shades of gray; if the printer does not handle gray, then it will round down the color value to a black, or round it up to a white (which makes it invisible); it could be a problem with PrinterControlLanguage (PCL) drivers vs. PostScript drivers; try altering the Graphics properties of the printer driver to produce darker, finer, vector output -- this should cause more colors to round down to black, instead of white

CR:172107

CR Number:   172107 Product Name:   PB Enterprise Product Component:   DB Informix Status:   Closed OS:   Microsoft Windows 95 Original Version:   5.0.04 Fixed Version Build Resolution Date Closure Code (If Appropriate) 6.5.00 28 Oct 1998 Fixed Description Got "SQL ERROR -766 : String must be null terminated. Has occured" error when declare/open a cursor with an INFORMIX7 ANSI DB (INET 7). This only happens when disablebind is set to 0 and when there's a string host variable in where clause with an informix ansi db. WARNING!!! corrected in some cases (static embedded sql) in pb5.0.05_10 CR 159854 => This still doesn't work with dynamic sql

CR:172152

CR Number:   172152 Product Name:   PB Enterprise Product Component:   DW Synchronization Status:   Closed OS:   Microsoft Windows 95 Original Version:   6.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 7.0.00 RC 03 Jan 2002 Fixed Description After having made a change to a column in a datawindow GetFullState() is executed on the source and then SetFullState() on the target dw or ds. The status flag for the row is DataModified! on both the source and the target. But the column's status flag is DataModified! on the source dw but is NotModified! on the target. According to documentation for GetFullState() the status flags should be included. The problem is that if an update() is done on the target dw or ds the rows that have been modified do not get updated. A better approach is to use GetFullState() and SetFullState() only when initailizing with data retrieved from the database and then use GetChanges() and SetChanges() to reflect any changes. This does result in the correct status flags and updates. Workaround: Use Getchanges() and Setchanges() to retain status flags. Workaround Description  Use Getchanges and Setchanges to retain status flags.

CR:172158

CR Number:   172158 Product Name:   PB Enterprise Product Component:   Language - Runtime Status:   Closed OS:   Microsoft Windows 95 Original Version:   6.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 6.5.00 11 Mar 1999 Fixed Description 6.0 Regression: GPF on Return of dynamic function call with boolean argument passed by readonly. Workaround: Call the function statically if you can, or try changing the pass by readonly to pass by value. Workaround Description  Call the function statically or pass the argument by value.

CR:172186

CR Number:   172186 Product Name:   PB Enterprise Product Component:   DW Edit Mask Status:   Closed OS:   Microsoft Windows 95 Original Version:   5.0.04 Fixed Version Build Resolution Date Closure Code (If Appropriate) 7.0.00 Beta 3 13 Nov 1998 Fixed Description Cursor movement of date datawindow column with edit mask has changed in PB 5.0.04. E.g. with edit mask 'dd/mm/yyyy' cursor could previously be moved from day to month by typing '/' - in PB 5.0.04, 6.0.00 ande 6.5.00 nothing happens. NB: ----- Sample pbl must be run on pb5.0.03, then on pb5.0.04, 6.0.00 and 6.5.00

CR:172191

CR Number:   172191 Product Name:   PB Enterprise Product Component:   DW - Runtime Status:   Closed OS:   MS Windows NT 4.0 Original Version:   6.5.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 7.0.00 Beta 3 31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product Description QueryMode rejects first char if it is an international accented char eg "", "" etc When a datawindow is in QueryMode and the first character entered for a column is an international accented letter the datawindow rejects it with the message "Specified criteria is invalid". A workaround exists. Workaround Description  1. Use quotes around the letter or word or 2. Prefix word with = symbol However this does require the cooperation of the end user

CR:172218

CR Number:   172218 Product Name:   PB Enterprise Product Component:   Structure - Runtime Status:   Closed OS:   Microsoft Windows 95 Original Version:   6.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 25 Dec 2000 Fixed Description If two structures are populated from the Message.PowerObjectparm, a subsequent change to the values in one structure are also reflected in the other structure. Workaround Description  Replace this code: str_1 = Message.PowerObjectParm str_2 = Message.PowerObjectParm With this code: str_1 = Message.PowerObjectParm str_2 = str_1

CR:172221

CR Number:   172221 Product Name:   PB Enterprise Product Component:   DW Painter Status:   Closed OS:   MS Windows NT 4.0 Original Version:   5.0.04 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11 Sep 1998 Not a Bug Description Enhancement request to have external source datawindow column edit limit property default to the length that the column was defined. For example, for a string column of length 20 at definition time, the resulting datawindow column edit limit should default to 20, not zero. If the data source is a database char(20) column, the edit limit would default to 20. For external source, the default edit limit is zero, which is no limit. This results in a validation error when you tab away from the column. WORKAROUND: The edit limit can be explicitly set within the painter. PER DEVELOPMENT: This will not be addressed. The workaround is simple, and other users may prefer the current behavior.

CR:172234

CR Number:   172234 Product Name:   PB Enterprise Product Component:   DB Informix Status:   Closed OS:   Microsoft Windows 95 Original Version:   5.0.04 Fixed Version Build Resolution Date Closure Code (If Appropriate) 6.5.00 16 Nov 1998 Fixed Description Informix - updateable datetime fields are not recognized in the where clause, when the datawindow update properties "Key and Updatable columns" and all columns are selected. No matter how DisableBind is set. Connected to a ANSI compliant DB.

CR:172246

CR Number:   172246 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) 31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product Description Enhancement Request: Customer would like to be able to add or edit retrieve arguments for a crosstab datawindow with a Stored Procedure source. When a Crosstab datawindow has Stored Procedure source, if you select Design...Datasource from the DW painter menu, you get to the crosstab definition dialog. I couldn't find a way to access the selection of the stored procedure or the retrieve arguments for the procedure. If you create a tabular datawindow from stored procedure source, it is possible to modify or add retrieve arguments through the painter. If you create a tabular datawindow from a SQL select statement, it is possible to add or modify retrieve arguments, but it is not possible when the datasource is a stored procedure.

CR:172296

CR Number:   172296 Product Name:   PB Enterprise Product Component:   DB Oracle Status:   Closed OS:   Microsoft Windows 95 Original Version:   6.5.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 6.5.00 464 22 Oct 1998 Fixed Description Execution of a stored procedure inside a pcakacge causes an error when using OR8 driver. If the procedure name is not qualified with the owner, you get Oracle error ORA-04043 Object mp_pkg2.sel_one_stud does not exist . If the procedure name is qualified with the owner, you get error ORA-25123 Too many components specified in the name. Workaround Description  Use the O73 driver.

CR:172299

CR Number:   172299 Product Name:   PB Enterprise Product Component:   DB Informix Status:   Closed OS:   Microsoft Windows 95 Original Version:   5.0.05 Fixed Version Build Resolution Date Closure Code (If Appropriate) 6.5.00 16 Nov 1998 Fixed Description update () and commit do not return an error value when the update is not performed. This is related to CR 172234 datetime is not recognized in the where-clause.

CR:172300

CR Number:   172300 Product Name:   PB Enterprise Product Component:   Menu Painter Status:   Closed OS:   MS Windows NT 4.0 Original Version:   6.5.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product Description Enhancement request: Customer would like to be able to add window controls such as SingleLineEdit, CheckBox, or DropDown ListBox to a Toolbar.

CR:172344

CR Number:   172344 Product Name:   PB Enterprise Product Component:   Help Status:   Closed OS:   Microsoft Windows 95 Original Version:   6.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 7.0.2 10 Aug 2000 Fixed Description Online help for 6.0 & 6.5 incorrect links for certain topics such as: ALLBASE takes you to "Modify PowerScript function" AllowEdit property takes you to "SelectItem PowerScript function: Syntax 2 When you know the item number" Alphabetical list of properties takes you to a page entitled that, but it is blank. Batch Applications takes you to "PostEvent PowerScript function" condensed mode takes you to PrintSend Powerscript Function