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

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

CR:166948

CR Number:   166948 Product Name:   PB Enterprise Product Component:   DB Oracle Status:   Closed OS:   Microsoft Windows 95 Original Version:   6.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 6.5.00 502 13 Nov 1998 Third Party Problem Description Memory is leaking when connected using OR8 and calling a window function that loops executing embedded SQL.

CR:166996

CR Number:   166996 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) 14 Jul 1998 Not reproducible with latest version of the product available as of Resolution Date Description **6.0 Regression: Making external function call: WSASTARTUP() from WINSOCK.DLL (16bit). If running on NT4.0 or NT3.51 or Win3.1 a gpf will occur in PBVM60W.DLL@002b:11c7. This worked fine in 5.0.04 16bit and is not a problem using 32bit on NT making call to WSOCK32.DLL. Nor is it a problem running 16bit PowerBuilder on WIN95 or WFW3.11. Workaround Description  If possible, create 32bit exe when deploying to NT machines and use WSOCK32.DLL.

CR:167003

CR Number:   167003 Product Name:   PB Enterprise Product Component:   Language - Compiler 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 482 23 Oct 1998 Fixed Description In a script, if you use: STRING(2001-02-29,"dddd, dd-mmm-yyyy"), no compiler errors. Result: 'Thursday, 29-feb-2001'.... an invalid date. Direct assignment in script is also an issue but it's already reported. CR 162708.

CR:167010

CR Number:   167010 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) 24 Sep 1998 Not a Bug Description Setitem(row,col, 2001-2-29) works with invalid dates. You can either do this literally or with an invalid date assigned via script like: ld_date = 2001-02-29 <-- This compiler bug is CR162708. setitem(row,col,ld_date) Development: SetItem() does not do any validation. The bug is in the compiler that allows the specification of an invalid date constant bug 162708.

CR:167019

CR Number:   167019 Product Name:   PB Enterprise Product Component:   DW Edit Mask 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 DELETE in date editmask can leave an invalid date. For example: . In a edit-mask with mask "dd/mm/yy" the user types in '31/12/96' and then deletes the '1' of the 12 (month), resulting in '31/02/96'. Then by means of a button the contents is being read and displayed: '31 february 1996'.....? Although this data has not been validated yet, by deleting the '1' in '12', we effectively let the user extract a valid date. Development: Not really a bug. The editmask control cannot prevent all possible conditions and keystrokes. We would have to disable the delete key for this circumstance and that would not be appropriate

CR:167047

CR Number:   167047 Product Name:   PB Enterprise Product Component:   Language - Runtime Status:   Closed OS:   MS Windows 3.1 Original Version:   6.0.01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 6.5.00 09 Dec 1998 Fixed Description Regression -16 bit PB app runs another 16 bit PB app, GPFs on close of 2nd app

CR:167129

CR Number:   167129 Product Name:   PB Enterprise Product Component:   Window - Runtime Status:   Closed OS:   MS Windows 3.1 Original Version:   6.0.01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 13 Aug 1998 Fixed Description Regression: 16 bit app does not open window. 6/10/98 fbashaw: Fixed in 6.0.01 build 442.

CR:167159

CR Number:   167159 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.0.01 13 Aug 1998 Fixed Description 6.0.01 Regression: PFC Examples GPF when populating a listview. This bug is a duplicate of 166615. Fixed in 6.0.01 build 442.

CR:167218

CR Number:   167218 Product Name:   PB Enterprise Product Component:   OLE - Active X - OCX Status:   Closed OS:   MS Windows NT 4.0 Original Version:   6.0.01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product Description If you are using a single PBD/DLL with the OLE generate registration feature, and if the LibraryList using a long filename path is greater than 129 characters on NT 4 or Win 95 the type library will NOT get generated. You will get the following error message in step 5 of 6 of the OLE automation registry generation dialog box "Error Generating Type Library". If you are using three or more PBDs/DLLs with the OLE generate registration feature, and if the total length of the LibraryList using a long filename path is greater than 276 characters then PowerBuilder will produce an access violation (a different address is generated each time) on NT 4 and PowerBuilder will hang indefinitely on Win 95. The problem occurs on the second press of the "Proceed" command button in step 5 of 6 of the OLE automation registry generation dialog box, usually the "Proceed" command button will work first time, but not under these circumstances. Workaround Description  The workaround is to use a shorter path and manually alter the LibraryList in the .REG file which is produced as the result of the OLE generate registration feature.

CR:167223

CR Number:   167223 Product Name:   PB Enterprise Product Component:   Inheritance Status:   Closed OS:   MS Windows NT 4.0 Original Version:   6.0.01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 04 Jan 1999 Not a Bug Description 6.0.01 Beta. There is a severe memory usage and handle leak problem in 6.0.01 434 when opening a window with inheritance. The window takes about 10 seconds to open vs sub-second in 5.0.04 most often mentioned with PFC and INHERITED objects. The handle leak is about 72 handles per open of PFC's pfc_w_master. PowerBuilder returns them all when the application closes. Development: Release note stating customers should rebuild all applications to avoid Application Painter load delays when using 6.5 Powerbuilder with older 6.0.00 applications and even when running the application. We change the internal type definitions slightly in 6.5 and this caused ANYTHING big being opened to take longer with 6.5 - meaning an Incremental or Full Rebuild (best) was required to sync up an old application with the new type definitions. We "recompiled" pfc for 6.5. By taking an older 6.0 application opening it with this version of PFC, then PFC (6.5) is newer than their application and this causes a mini incremental rebuild on startup. If the developer uses the original 6.0 version of PFC then everything is in sync, of course. Any time the ancestor classes are newer than their descendants (as in this case using a 6.0 PFC application with newer 6.5 PFC pbls - as just about everything will be) then the vm must do a psuedo-rebuild of the descendants since the ancestor has changed. This happens when you open the app painter because it encounters one of these situations and then does the rebuild. So think of it like you are doing an incremental rebuild every time you open the app painter (or any painter for that matter). The difference is, this rebuild does not get saved back to disk so until you do a real one incremental rebuild, it will keep happening. Of course, the work around is to do an incremental rebuild and it is then solved. The problem is there is nothing we can do to solve this. This is actually correct behavior and really is a staging issue. The only way around this would be to ship the 6.0 GA version of PFC. But, of course, you can't do that because then you don't get bug fixes. Developers should do a full rebuild any time they upgrade to a newer version of PFC.

CR:167238

CR Number:   167238 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 16 Jun 1998 Fixed Description 5.0.04/6.0.00 Regression. Gettext() on a NULL date column with editmask shows 2000-01-01. It should show nothing. More importantly, validation expressions (or any expression) using this value also could break applications. Isdate(gettext()) returns TRUE on a newly inserted row with no data (since the gettext() is "getting" 2000-01-01 a perfectly valid date.

CR:167242

CR Number:   167242 Product Name:   PB Enterprise Product Component:   DPB 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 IsValid not working on Server Push object references

CR:167247

CR Number:   167247 Product Name:   PB Enterprise Product Component:   Debugger Status:   Closed OS:   Microsoft Windows 95 Original Version:   6.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 6.5.00 04 Jan 1999 Fixed Description Using the DebugBreak() function and "Just In Time Debugging" mode. When the debugger is launched it does not stop at the DebugBreak () function or execute any remaining script in the ItemChanged event of the datawindow if there is any code, even a comment, in the LoseFocus event. If you then proceed through the debugger by clicking the Continue icon, a MessageBox() will display with: "There already is an instance of the debugger". Click OK, when you return to the debugger, all icons are greyed out. When you return to the application, run it again and it "blinks". After another try or two, a page fault will occur in PBVM60.DLL@0137:1120f02d.

CR:167325

CR Number:   167325 Product Name:   PB Enterprise Product Component:   Profile Painter Status:   Closed OS:   MS Windows NT 4.0 Original Version:   6.0.01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 07 Oct 1999 Fixed Description The following is quoted from our documentation: DESCRIPTION: GarbageCollectSetTimeLimit ( newtimeinmilliseconds ) Sets the minimum interval between garbage collection passes. ARGUMENT: newtimeinmilliseconds - A long (in milliseconds) that you want to set as the minimum period between garbage collection cycles If NULL, the existing interval is not changed Specifies the minimum interval between garbage collection passes: garbage collection passes will not happen before this interval has expired. Garbage collection can effectively be disabled by setting the minimum limit to a very large number. If garbage collection is disabled, unused classes will not be flushed out of the class cache. When I pass GarbageCollectSetTimeLimit a value equal too 2147483647 (maximum value for a long) there is no effect. Recreated with 32 bit PowerBuilder 6.0 GA and 6.0.01 build 424.

CR:167327

CR Number:   167327 Product Name:   PB Enterprise Product Component:   DB Oracle 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 Beta 3 3245 11 Feb 1999 Fixed Description Customer is connecting to Oracle 7.3 with native drivers. Customer has created extended attributes in Powerdesigner and wants to use these in Powerbuilder. He has created public synonyms with these extended attributes. The public synonyms are available, including the extended attributes, while in PB in the Database Painter and when creating a Quick Select dw. They are not available in a SQL Select datawindow. He is trying to create datawindows with these public snyonyms and he can see them when he chooses Quick Select, including all the extended attributes, but when he tries to build a SQL Select datawindow he can see a table reference with the same name but it appears without the public qualifier and it does not have any of the extended attributes. He needs to use SQL Select because several tables are usually involved in these datawindows.

CR:167329

CR Number:   167329 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 16 Jun 1998 Fixed Description 6.0.00 Regression. Scrolling with a RetrieveAsNeeded datawindow not in print preview has large white blank spaces when scrolling. This does not appear in 5.0.04 or 6.0.01.

CR:167332

CR Number:   167332 Product Name:   PB Enterprise Product Component:   DB MS SQLServer Status:   Closed OS:   Microsoft Windows 95 Original Version:   5.0.04 Fixed Version Build Resolution Date Closure Code (If Appropriate) 6.5.00 462 15 Dec 1998 Fixed Description If a column is defined as type TIMESTAMP and NULL's are allowed, in the dw painter you cannot select this column. It first comes up with a datatype of binary(8). It should be TIMESTAMP. This behavior can be seen in versions 5.0.04, 6.0.0x. Workaround Description  Don't allow NULL's for column.

CR:167355

CR Number:   167355 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) 6.5.00 463 13 Nov 1998 Fixed Description 6.0.00 Regression. Picturelistbox using a picture of 180x150 pels cuts off the bottom half of the picture. (bad in 6.0.01 beta I, II as well).

CR:167370

CR Number:   167370 Product Name:   PB Enterprise Product Component:   DB Oracle 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 459 12 Nov 1998 Fixed Description When retrieving recordset into a datawindow object created from a Oracle7.3 and 8.0 stored procedure as a datasource, retrieval arguments with single quotes do not return result set.

CR:167407

CR Number:   167407 Product Name:   PB Enterprise Product Component:   OLE - Active X - OCX Status:   Closed OS:   Microsoft Windows 95 Original Version:   6.0.01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 01 Feb 1999 Not reproducible with latest version of the product available as of Resolution Date Description GPF when go back to an html page wich includes a Window ActiveX pbrx60.ocx

CR:167473

CR Number:   167473 Product Name:   PB Enterprise Product Component:   Language - Runtime Status:   Closed OS:   Microsoft Windows 95 Original Version:   6.0.01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 31 Oct 2002 Not a Bug Description 6.0.01 Regression: Day() function problem: Day( Date("2/29/2002")) returns day of one instead of zero. Workaround: Always apply the IsDate() function and only proceed on valid dates. Workaround Description  Workaround: Always apply the IsDate() function and only proceed on valid dates.

CR:167530

CR Number:   167530 Product Name:   PB Enterprise Product Component:   Language - Runtime Status:   Closed OS:   MS Windows 3.1 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 Using PrintDefineFont to set fonts, and PrintText to print strings using the defined fonts. 5.0.x works in all cases 32 and 16 bit, but 6.0.x 16 bit does not work on Windows 3.11, all strings print in a default font.

CR:167550

CR Number:   167550 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) 03 Mar 2004 EOL'd version. Not to be Fixed. Description 6.0.00 Regression. Unable to directly assign an element of an array that is part of a structure that is returned by a function to a variable. You must have an intermediate structure that will take the return from the function and then assign the array element to a variable. This was allowed in 5.0 For example: uf_function() returns a structure of type 'LongStructure' that contains 2 elements: One of type Long, and another of type Unbounded Long Array. i.e. LongStructure long l_long long l_longarray[] long ll_rtnlong ll_rtnlong = uf_function().l_long // this will work in 5.0 and 6.0 ll_rtnlong = uf_function().l_longarray[1] // this will not work in 6.0, but works in 5.0 Both of these cases in the future will generate compiler warnings. Returning a structure as part of a function call in a Powerscript statement can be dangerous since the memory could have been freed. We made several changes in 6.x and beyond to fix several memory leaks that were really these structures left lying around (which is why you could reference them as above in 5.0). Now that we clean these structures up after the function call, it's possible to get memory corruption with these types of constructs. Correct way to code this: long ll_rtnlong LongStructure ll_struct ll_struct= uf_function() ll_rtnlong=ll_struct.l_long ll_rtnlong=ll_structl_longarray[1] Per PB Engineering: The reason this worked in 5.0 was because we were not deleting the temporary struct returned from the function call in the expression myfunc().fieldname. This resulted in a memory leak which has since been fixed. As part of fixing this memory leak, the field elements were also free'd after the expression evaluation. Because the field here is a string, the string value therefore is free'd resulting in the garbage that you see when you run this test case. It is expected that this syntax will work for simple data types at this time, but not for strings, or arrays. Please issue a separate change request for a compiler warning against this, to eventually be a compiler error in the next major release of PB. Due to this, I would strongly recommend to customers that they change all occurrances of this syntax to use a local struct variable, and return the function result into that. This ensures that the data will be correct and avoid any crashes until we fix the compiler to warn against this. (CR 203969 was added to request the compiler warning.) Workaround Description  Create a local structure and assign it the structure that is returned by the function: i.e. LongStructure lstr_rtnstructure long ll_rtnlong lstr_rtnstructure = uf_function() ll_rtnlong = lstr_rtnstructure.l_longarray[1] // this will work

CR:167663

CR Number:   167663 Product Name:   PB Enterprise Product Component:   P-Code Deployment Status:   Closed OS:   MS Windows 3.1 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 Resource leak opening multiple sheets with inherited menus with Windows 3.11. If you use up all resources, it de-stabilizes Win 3.11 and when you exit the application, you will get a GPF in PBRTE050.DLL. 0003:f6c3

CR:167715

CR Number:   167715 Product Name:   PB Enterprise Product Component:   DB Informix 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 589 19 Mar 1999 Duplicate Description Informix IN7 driver DW generates Update syntax with "is NULL" in WHERE clause for a column which contains an empty string

CR:167753

CR Number:   167753 Product Name:   PB Enterprise Product Component:   DW HTML Status:   Closed OS:   Microsoft Windows 95 Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 7.0.00 7004 04 Oct 1999 Fixed Description When you call <dw>.SaveAs() to create an HTML file form a free form datawindow, the resulting html file may not contain all of the data from the datawindow. Multiple DB columns on the same line seem to trigger the problem.

CR:167793

CR Number:   167793 Product Name:   PB Enterprise Product Component:   Business Graphics Status:   Closed OS:   Microsoft Windows 95 Original Version:   6.0.01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 6.5.00 543 03 Feb 1999 Fixed Description 6.0.01 Regression - Graph with Value Axis property: AutoScale=off displays 'weird' numbers on the axis - seems like a rounding problem. All show the same 'weird' numbers on the axis like 49.9999999 & 149.9999997 instead of rounding to 50 or 150. Workarounds: 1. Turn autoscale back ON in the Value Axis Tab Page. 2. Format the Value Axis Text by clicking on the Text tab of the graph property sheet. -Click on 'Value Axis Text' item in the Text Object listbox to show all properties for the Value Axis -Notice the Display Format field shows [general] for the format. Click on the Formats... button and change the format to something like 000 or ### and you will no longer see trailing 3's or 9's.

CR:167794

CR Number:   167794 Product Name:   PB Enterprise Product Component:   Window - Runtime Status:   Closed OS:   Microsoft Windows 95 Original Version:   5.0.04 Fixed Version Build Resolution Date Closure Code (If Appropriate) 7.0.00 Beta 2 3255 04 Dec 1998 Not reproducible with latest version of the product available as of Resolution Date Description An accelerator key on a tab page is fired when the tab page is not current. Problem exists in PB 5.0.04. It does not exist in 6.0.01 build 444.

CR:167803

CR Number:   167803 Product Name:   PB Enterprise Product Component:   Library Painter Status:   Closed OS:   Microsoft Windows 95 Original Version:   6.0.01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 6.0.01 01 Jul 1998 Fixed Description Customer reported that when they applied the 419 Beta patch they started experiencing problems trying to do a Full Rebuild on their PFC application. With PB 6.0 GA the application was able to complete a Full Rebuild in either the Library Painter or the Project Painter. The customer is hanging while I receive an illegal page fault, but it is failing consistently on the same objects and otherwise identical. He has plain WIN 95 while I have WIN 95b. Through testing his original full application (44 pbls), and the narrowed down sample app I discovered that the Full Rebuild started failing in Build 404, which is the first available build after a different PFC application Full Rebuild (CR 164588) bug was fixed. This was tested up through build 444 with the same results.

CR:167825

CR Number:   167825 Product Name:   PB Enterprise Product Component:   DW - 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 461 23 Nov 1998 Fixed Description Setitem()/Reset() loop leaking memory with a datastore. Using the same datastore over and over and calling Reset() is the culprit. The original value would be leaked across a call to Reset(). A simple work around would be to delete the datastore every time in the outer loop. The Setitem() call causes an allocation (to hold some data) Workaround Description  Suggestions: 1) When batch processing large amount of data with in the datawindow with multiple rows and columns, brake it down and process in the smaller chunks; 2) Upgrade memory on the machine (server) that is doing the processing

CR:167852

CR Number:   167852 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) 20 Jan 1999 Duplicate Description Declaring global variable (in the Declare Global Variables dialog) of inherited PFC autoinstantiated user objects such as n_cst_color, n_cst_numerical, n_cst_datetime causes error invalid page fault 0137:111fcfbc / access violation in 0x111fcfbc when trying to run the application after a full rebuild or when doing a full rebuild in the library painter to create an executable. This was due to some extra source for some of these objects causing a problem when made global. To permanently correct the source, you need to resave all the inherited objects using the user object painter from pfc_n_base down to the object you're using as a global. Migration, regeneration and import will not solve the problem - the source must be re-written by the painter. In general, we don't recommend using autoinstantiated objects as global variables. Workaround: Code the references to these objects from the application manager NVO inherited from n_cst_appmanager (which of course is not autoinstantiated). This way, there is only one global variable - everything stays encapsulated, and it is not hard to reference in code (just qualify everything with gnv_app.reference)

CR:167853

CR Number:   167853 Product Name:   PB Enterprise Product Component:   DW Synchronization Status:   Closed OS:   Microsoft Windows 95 Original Version:   6.0.01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15 Apr 1999 Fixed Description If you create a user object and place a datawindow control on it without specifying the underlying datawindow object, a subsequent call to SetFullState() will cause the datawindow to shift up within the user object. Workaround Description  Specify the datawindow for datawindow controls that are in user objects if you intend to do a subsequent SetFullState. Or, Reposition the datawindow by changing the x and y coordinates after the SetFullState() call

CR:167855

CR Number:   167855 Product Name:   PB Enterprise Product Component:   Printing Status:   Closed OS:   Microsoft Windows 95 Original Version:   6.0.01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 6.5.00 569 04 Mar 1999 Fixed Description If you change you default printer within PowerBuilder, the setting should only last for the life of the current PowerBuilder session. However, if you close PowerBuilder and start it up again, the printer is not default back to the system default.

CR:167859

CR Number:   167859 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) 09 Sep 1998 Presently Not Targeted For Any Future Release Of This Product Description Regression from PB 5.0 for all builds of 6.0/6.01 tested GA through build 444. Customer reported as P1. The dll's being left in memory is happening on all platforms tested, WIN95, NT 4.0 and WIN 3.11 platforms. Extensive testing was done with WIN95 as this is the platform that this customer is using. When the customer runs a 16 bit exe with datawindows or userobjects with datawindows on them PB is leaving 11 - 16 bit dll's in memory. When the customer then tries to run a 32 bit application he is receiving an illegal page fault. Also trying to rerun the 16 bit application or returning to the 32 development environment causes gpf. After testing this issue out I found the problem to exhibit itself in different ways depending on what I tried to do next after closing out normally from a simple 16 bit executable. I also tried this with both machine code and pcode with the same results. The PB 6.0 exe leaves the following 11 dlls in memory: ole2.dll,ole2disp.dll, ole2nls.dll, pbbgr60w.dll, pbdwe60w.dll, pboui60w.dll, pbvbx60x.dll, pbvm60w.dll, storage.dll, typelib.dll, unidrv.dll. Furthermore, when I tried to unload the dlls if I unload pbdwe60w.dll all of the other 10 dll's also get unloaded but if I try to unload pbvm60w.dll then pbbgr60w.dll and pbdwe60w.dll were still left in memory. Workaround: Declare as external functions: SUBROUTINE FreeLibrary(uint libhandle) LIBRARY "Krnl386.exe" FUNCTION int GetModuleHandle(string modname) Library "Krnl386.exe" Script in Close Event of Application: uint l_handle l_handle = GetModuleHandle("pbdwe60w.dll") // This can be any dll or library that is loaded into memory. FreeLibrary(l_handle)

CR:167936

CR Number:   167936 Product Name:   PB Enterprise Product Component:   DW Printing Status:   Closed OS:   Microsoft Windows 95 Original Version:   6.0.01 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 It is impossible to print a clear 3D graph datawindow. They always print out very small, illegible and in the centre of the page. No change of graph properties helps. Fails with following 3D graph types : 3D Column 3D Bar 3D Area 3D Line 2D graph datawindows print fine and MS Graph prints correctly with a 3D graph. Workaround Description  There is no real acceptable workaround other than use 3rd party product to do what PB should do. W/A suggested but rejected by ct... - Visual component OCX in PB OLE datawindow or use - Microsoft Graph in PB OLE datawindow.

CR:167949

CR Number:   167949 Product Name:   PB Enterprise Product Component:   DW Display Status:   Closed OS:   Microsoft Windows 95 Original Version:   6.0.01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 6.0.01 02 Jul 1998 Fixed Description 6.0.01 Regression starting with build 424. Composite datawindow using Page() + PageCount() in header or footer band. In preview mode or print output, the page numbers display ie 1 of 3, 1 of 3, 1 of 3 (if there were only 3 pages in the report).

CR:168031

CR Number:   168031 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) 31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product Description Can not insert a tab character into an mle on a tab page or in an MDI app. Workaround Description  Subclass a standard visual user object from multilineedit; u_mle. (or use PFC u_mle) On u_mle map a user event; ue_keydown to pbm_keydown. Script: If KeyDown(KeyEscape!) and KeyDown(KeyT!) then this.post undo() this.post ReplaceText end if

CR:168037

CR Number:   168037 Product Name:   PB Enterprise Product Component:   DW Edit Mask Status:   Closed OS:   Microsoft Windows 95 Original Version:   6.0.01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 7.x Catalina 13 Apr 2000 Fixed Description Tested and reproduced with Pb 5.0.04/PB 6.0 GA and 6.0.01 build 444. Trying to delete or re-enter a new date on a highlighted editmask column with either Center or Right alignment that is only partially visible because the column is too narrow results in an illegal page fault or a seemingly infinite loop. Left (default) and justify alignment appear to not exhibit the problem. With the infinite loop when I hit Ctrl=>Alt=>Delete I got a messagebox with "The system is dangerously low in resources. Would you like to terminate the following application? accompanied by the title of the window. " Illegal page faults I received on my machine : PB 6.0 GA build 251 @ 0137:1113c9cd PB 6.0.01 Build 444 @ 0137:1111ef1b Workaround Description  Use Left(default) or Justify and the problem does not occur.

CR:168054

CR Number:   168054 Product Name:   PB Enterprise Product Component:   Window - Runtime Status:   Closed OS:   Microsoft Windows 95 Original Version:   6.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 6.5.00 08 Feb 1999 Fixed Description 6.0.00 Regression. Setting the tabstop property MLE mle_1.tabstop[<position>] = <size of the tab> for a multilineedit control doesn't work

CR:168067

CR Number:   168067 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) 6.5.00 28 Oct 1998 Fixed Description 6.0.01 REGRESSION - Can't select a value in a dropdowndatawindow if the display value contains a comma (European format) 5,2. Get "Item does not pass the validation test"

CR:168070

CR Number:   168070 Product Name:   PB Enterprise Product Component:   Library Painter 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 16 Jun 2004 Not reproducible with latest version of the product available as of Resolution Date Description Incremental rebuilds fail with PFC applications. Must do a full rebuild for any small changes in descendant objects. (there were many examples of this. The best thing to do is try the release it is fixed in)

CR:168071

CR Number:   168071 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) 10 Aug 2000 Fixed Description Documentation enhancement added to the User's Guide and On-line help: Nested and composite datawindow's require a printer driver be installed on the user's machine. When the datawindow does not display properly (it's blank), it is probably because there is no printer driver installed on the machine they are using.

CR:168111

CR Number:   168111 Product Name:   PB Enterprise Product Component:   DW - Runtime Status:   Closed OS:   Microsoft Windows 95 Original Version:   5.0.05 Fixed Version Build Resolution Date Closure Code (If Appropriate) 7.0.00 Beta 3 15 Dec 1998 Not reproducible with latest version of the product available as of Resolution Date Description Using a datetime column type for a graph "value" expression (graph style datawindow or graph object on a datawindow) causes the application to hang during preview (really while painting the data) after the retrieve or setitem() to the datetime field. This is a bug from Powerbuilder 5.0 on. Workaround: You can use a date() by instead substituting "DATE(datetime_column)" for VALUE on the graph.

CR:168121

CR Number:   168121 Product Name:   PB Enterprise Product Component:   DB DB2 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 next build 26 Jan 1999 Fixed Description Using datetime retrieval argument for datawindow causes error -181. Cause is use of too many digits in microseconds prtion of timestamp. Workaround Description  None. Datawindow cannot be saved; converting to syntax does not help as the problem is the dummy value inserted for the argument to get the statement prepared.

CR:168131

CR Number:   168131 Product Name:   PB Enterprise Product Component:   P-Code Deployment Status:   Closed OS:   Microsoft Windows 95 Original Version:   6.0.01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 09 Mar 1999 Fixed Description Converting a string to double with the DOUBLE function and with german country settings for numbers (decimal seperator = "," and number group = ".") causes wrong convertions.

CR:168138

CR Number:   168138 Product Name:   PB Enterprise Product Component:   DW Painter Status:   Closed OS:   Microsoft Windows 95 Original Version:   6.0.01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 6.0.01 28 Jan 1999 Fixed Description DW painter generates incorrect SQL for union of outer joins using SQL Anywhere. Workaround Description  On both outer joins; Change: FROM {oj customer LEFT OUTER JOIN sales_order ON customer.id = sales_order.cust_id}, To: FROM customer KEY LEFT OUTER JOIN sales_order ON customer.id = sales_order.cust_id,

CR:168141

CR Number:   168141 Product Name:   PB Enterprise Product Component:   Library Painter Status:   Closed OS:   Microsoft Windows 95 Original Version:   6.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 7.0.00 RC0 5010 01 Feb 1999 Fixed Description In the library painter, if you move the mouse pointer over one of the toolbar items and have the tooltip appear; [starting from the Export toolbar item and all others to the right of it (Import, Regen, Search...)], then doubleclick and open an application object, when the toolbar repaints, the item the mouse was on stays.

CR:168177

CR Number:   168177 Product Name:   PB Enterprise Product Component:   Language - 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 function for truncate or round time on seconds, minutes, hours .. function for truncate or make a round time "TruncateTime( time value, integer mode ) " truncate on hours minutes and so on - by mode selection

CR:168178

CR Number:   168178 Product Name:   PB Enterprise Product Component:   DW - 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 5.0.04/6.0.00 Regression. Setting the rowstatus with SetItemStatus to DataModified when the Key Modification is set to "Use Delete then Insert" generates a DELETE and INSERT statement on Update() and re-inserts the same row. This only happens if you code the Update() function with the datawindow in this state. This was caused by a fix to 157312 in 5.0.04. Workaround Description  set the columnstatus for each column to be updated instead of rowstatus

CR:168181

CR Number:   168181 Product Name:   PB Enterprise Product Component:   Menus - Runtime Status:   Closed OS:   Microsoft Windows 95 Original Version:   6.0.01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 6.5.00 467 07 Dec 1998 Fixed Description Regression 6.0.01 beginning with build 381 and reproducible through build 444. Customer has simple genapp application in which he is initially changes the visible attribute to false for several menuitems: visible. He then changes this same properties to 'true' in script and the application halts with an illegal page fault in USER.exe @ 0011:00000971. Placing a messagebox, a yield() or running through the debugger eliminates the illegal page fault. Workaround Description  Using Yield() in loop eliminated illegal page fault.

CR:168233

CR Number:   168233 Product Name:   PB Enterprise Product Component:   Window Painter Status:   Closed OS:   Microsoft Windows 95 Original Version:   6.0.01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 3255 02 Dec 1998 Not reproducible with latest version of the product available as of Resolution Date Description Inherit a window from an ancestor window which has any visual userobject placed on it. Close it immediately after without saving. Try to open the ancestor window and get the error: "Object or one of its ancestors or descendants is already open in another window painter...etc" Must exit PB and start again to open the window. Same happens if use a custom visual uo instead of a window in example above Works OK in 5.0.04 but not in 6.0 GA nor 6.0.01 build 444

CR:168244

CR Number:   168244 Product Name:   PB Enterprise Product Component:   Inheritance 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 If you change the name of a tab control (eg tab_1 -> tab_10) on a custom visual uo which has been inherited from, that change passes down correctly to the descendant when it's saved. But. Change the name of the tab control in the ancestor object again and at the same time add a couple of comments to a tabpage in the tab control and this is the error which appaers in the descendant when trying to open and save for a second time... Object: u_descendant tabpage_1 Class Declaration (0001): Error C0001: Illegal data type: tab_1 The only way to get this change into the descendant is export, edit and import the descendant object. This can be reproduced with any control embedded in the tab control - reproduced with tabpages, datawindow controls, command button. The important combination is Change name of parent control (tab_1) once, allow changes to be saved in descendant Change parent control name again AND add some script to an embedded control (or tabpage). Workaround Description  Export the descendant object Edit the source file manually to force the name change Import again.

CR:168277

CR Number:   168277 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) 24 Sep 1998 Not a Bug Description Originally bug 41584. If an EditMask on a DataWindow column contains one # to the left of the decimal point (#.## or ##.##), no data can be entered into the column. Using the same EditMask on an EditMask control, the behavior is wrong, as well. If you highlight all the data by doubleclicking and click on the DELETE button and tab off, you get "item does not pass validation test" Development: Not a bug. It works this way because a single decimal point is not a valid number. When first painted we will paint a single "." but once data is entered or the contents of the editmask control the data window engine will insist on a valid number being there. One workaround would be to define the edit mask as #.00, and define a format display of #.##, define the column to "Use Format". Then, when the column has focus, the column will display .00 but, when it does not have focus it will display "."

CR:168289

CR Number:   168289 Product Name:   PB Enterprise Product Component:   DW - Runtime Status:   Closed OS:   MS Windows NT 4.0 Original Version:   6.0.01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 6.0.01 444 21 Sep 1998 Fixed Description Setfullstate() gpfs in 6.0.01 . Works fine in build 424. This is a simple example with a freeform datawindow using the department table (5 records). Same thing with Grid - datawindow type didn't matter.

CR:168415

CR Number:   168415 Product Name:   PB Enterprise Product Component:   DB Oracle 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 464 20 Oct 1998 Fixed Description You cannot create or preview a datawindow based on a stored procedure if you are using Oracle 8.0.04 client software. If you are using the OR8 connection to an Oracle 8 dtabase, you will get error ORA-01001. In all other cases you will get a GPF.

CR:168417

CR Number:   168417 Product Name:   PB Enterprise Product Component:   DW Display 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 When a datawindow is set to QuerySort and that datawindow contains a DropDownDataWindow the column with the dddw shows the data column instead of the display column after selecting an item from the dddw and clicking out of the row/column. Setting QueryMode on without QuerySort is OK in the same conditions. Workaround Description  Click option 'Always show arrow' for dddw edit style and the display column is maintained for 1 QuerySort session.

CR:168421

CR Number:   168421 Product Name:   PB Enterprise Product Component:   Language - Runtime Status:   Closed OS:   Microsoft Windows 95 Original Version:   7.0.00 Beta 1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 30 Nov 1998 Presently Not Targeted For Any Future Release Of This Product Description PowerBuilder hangs or GPF's when the user resources are down to the minimum. A new feature is needed to handle the fact that PB cannot allocate new memory anymore and fail silently or give the user an error message.

CR:168452

CR Number:   168452 Product Name:   PB Enterprise Product Component:   Browser 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 As you drill down into objects in the window tab of the browser, the icons become incorrect and the contents incorrect.

CR:168506

CR Number:   168506 Product Name:   PB Enterprise Product Component:   DW - Runtime Status:   Closed OS:   Solaris 2.5.1 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 If you try and enter a date using the European date format dd/mm/yy, in preview or runtime mode, PowerBuilder will give you the following DataWindow error message "item '29/03/98' does not pass validation test." If you typed in 03/29/98, then there is no problem. If you place a command button on a window which contained the following script: MessageBox("Today's Date",string(today())), when this is executed the messagebox will display today's date e.g. 06/22/98 If you edit the .WindU file and scroll to the [intl] section, you can see the date format which is used. Here are the initial settings: SShortDate=M/d/yy SLongDate=dddd, MMMM dd, yyyy If you now change the above to European date format i.e. SShortDate=d/m/yy SLongDate=dddd, MMM, yyyy Now if you execute MessageBox("Today's Date",string(today())), this will return e.g. 22/06/98. Which is what you would expect. If you now retrieve some information from your database via your datawindow, which contains a datetime column, the dates would be displayed in European format. Which is what you would expect. If you try and enter a date using the European date format dd/mm/yy, in preview or runtime mode, PowerBuilder will give you the following DataWindow error message "item '29/03/98' does not pass validation test." If you typed in 03/29/98, then there is no problem, UNTIL you tabbed off the column. The date gets converted into European format i.e. 29/03/98. Workaround Description  Place an edit mask of DD/MM/YY on the datetime column, then Powerbuilder will accept the European dateformat. The only problem is that PowerBuilder will display 00/00/00 by default when a new column is inserted.

CR:168547

CR Number:   168547 Product Name:   PB Enterprise Product Component:   DW DDDW 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 Customer is toggling the 'UseAsBorder' DDDW property programmatically from a command button and if the user click on whitespace or a text field the data disappears from the ddddw colum that currently has focus. It happens whether you change the property with dot notation or with a modify statement. This is not a regression. When the user clicks on an actual column this does not happen. There also does not appear to be problem with the analogous "alway show arrow" property checked or unchecked.

CR:168592

CR Number:   168592 Product Name:   PB Enterprise Product Component:   DW Synchronization Status:   Closed OS:   Microsoft Windows 95 Original Version:   6.0.01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 6.5.00 31 Oct 2002 Not reproducible with latest version of the product available as of Resolution Date Description SetFullState GPFs when the blob size is around 1 Meg. Could not reproduce in 7.0

CR:168596

CR Number:   168596 Product Name:   PB Enterprise Product Component:   Rich Text Status:   Closed OS:   Microsoft Windows 95 Original Version:   6.0.01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 7.0.00 RC0 4000 21 Jan 1999 Fixed Description If you sepcify a non-default pointer to an RTE control on a window, the window runtime ignores this and continues to use the arrow poinbter.

CR:168610

CR Number:   168610 Product Name:   PB Enterprise Product Component:   DW DDDW 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 Feb 1999 Fixed Description In code similar to the PFC DataWindow DropDownSearch service, It gpfs when the dropdowndatawindow "UseAsBorder" attribute is NO and it is being changed to "YES" by Modify() and the dddw Always Show Arrow is 'NO', it will GPF when modifying the dddw display column at runtime.

CR:168611

CR Number:   168611 Product Name:   PB Enterprise Product Component:   DB MS SQLServer Status:   Closed OS:   Microsoft Windows 95 Original Version:   6.0.01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 6.5.00 542 18 Jan 1999 Fixed Description Mss driver doesn't allow more than 25 connections. Customer would like the MaxConnect DB parm to be available for the Microsoft SQL Server (MSS) driver. Error message when exceeding maximum was an ambiguous "A SQL Server request resulted in a bad return code or status but no error message was returned".

CR:168683

CR Number:   168683 Product Name:   PB Enterprise Product Component:   Language - Compiler 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 When using dot notation to assign data from a datastore or datawindow to a bound char array the array's length 'stretches' to fit length of the data in the dw/ds field char char5[5] char5 = "1234567890" // will give -> 12345 Correct, expected behaviour char5 = dw_1.object.col1[1] // will give 1234567890 (assuming the col has that value) A workaround is to pass the same code through String() Workaround Description  Use String to convert... char5 = string(dw_1.object.col1[1]) // Gives 12345

CR:168715

CR Number:   168715 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) 31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product Description 6.0.00 Deficiency. There is a problem expanding hierarchies in the Object Browser causing GPFs on heavily inherited tab or user objects. Development: The problem is with the browser/window painter in that it builds a list of objects has an architectural limitation.

CR:168723

CR Number:   168723 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) 6.5.00 460 13 Oct 1998 Fixed Description Calling a remote Oracle stored procedure fails with a describe error in PB 5 and PB 6. This worked in PB 4.

CR:168757

CR Number:   168757 Product Name:   PB Enterprise Product Component:   DB Oracle 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 514 31 Dec 1998 Fixed Description Repeated executions of an Oracle stored procedure cause about 8 K of memory to be used per call. Occurs with OR8 driver and Oracle 8.0.03 and 8.0.04. Memory is returned when the application disconnects from Oracle. Development: Verified that leak is caused by Oracle client not giving up memory associated with the stored procedure calls until the environment handle is is freed by a call to OCIHandleFree.(). Developer needs to contact Oracle to open a case with them. Workaround Description  The Oracle 7.3 drivers can be used to connect to Oracle 8. The customer will have little impact unless new Oracle 8 features are used in application.

CR:168806

CR Number:   168806 Product Name:   PB Enterprise Product Component:   DW - 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 460 21 Sep 1998 Fixed Description 6.5.00 Regression. The Page() computed field in a footer of a datawindow with a group is broken when the report has "Reset Page on Group Break" set and the report is in print preview mode. The settings that fail: New Page on Group Break (ON) Reset Page Number on Group Break (ON) <----- This is what is broken. This allows things like Page 1 of 2 - Page 1 for value 100 Page 2 of 2 - Page 2 for value 100 Page 1 of 3 - Page 1 for value 200 Page 2 of 3 - Page 2 for value 200 Page 3 of 3 - Page 3 for value 200 What happens now: Page 1 of 2 - Page 1 for value 100 Page 2 of 2 - Page 2 for value 100 Page 3 of 3 - Page 1 for value 200 Page 4 of 3 - Page 2 for value 200 Page 5 of 3 - Page 3 for value 200 Workaround: Placing the datawindow in a composite will show the Page() correctly as the groups break and continue from page to page.

CR:168856

CR Number:   168856 Product Name:   PB Enterprise Product Component:   DB Painter 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 If a change is made in the database painter (in the table painter) to a column's extended attribute such as 'Justification' the column's extended attribute for 'Case' is changed even though this was not requested nor available for change in the table painter. Put on a trace and you see that the table pbcatcol is being changed for this table/column for the column when you only change the justification attribute... pbc_case from the value 27 (upper) to the value 0 (lower) Would like this value not to be touched in PBCATCOL if it hasn't been changed in the painter Workaround Description  Right mouse button on the column on the graphic representation of the table in database painter Click 'Display' tab and change column properties there.

CR:168888

CR Number:   168888 Product Name:   PB Enterprise Product Component:   Language - 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 String(lparam, "address") not properly de-referencing string address in 32 bit. Not a PB bug. In 32 bit passing an address by value between two separate apps will not work as they are running in separate memory spaces, and cannot access each other's memory.

CR:168937

CR Number:   168937 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 205 29 Sep 1998 Fixed Description A pipeline with two or more outer joins. When pipeline executes and Extended Attributes is checked, a page fault occurs: r "pb050 caused an invalid page fault in module pbshr050.dll at 014f:11132175" or PB60 caused an invalid page fault in module pbvm60.dll at 0157:1111F2A1. If Extended Attributes is NOT checked, this does happen and the pipeline executes successfully.

CR:168945

CR Number:   168945 Product Name:   PB Enterprise Product Component:   DB ODBC Status:   Closed OS:   Microsoft Windows 95 Original Version:   6.0.01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 29 Sep 1998 Not a Bug Description When using the SqlCache parameter with an ODBC connection, the SqlReturnData is not being populated with the cache statistics as described in the help text for SqlCache.

CR:168977

CR Number:   168977 Product Name:   PB Enterprise Product Component:   PB GUI Status:   Closed OS:   MS Windows 3.1 Original Version:   6.0.01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 09 Sep 1998 Presently Not Targeted For Any Future Release Of This Product Description 16 bit memory leak in OpenUserObject & CloseUserObject in Win3.11

CR:169016

CR Number:   169016 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) 31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product Description You cannot call the ChildWindowFromPoint Windows API function from PowerBuilder. You get error "specified argument differs from required argument at runtime in DLL function ChildWindowFromPoint. Invalid stack pointer on return from function call."

CR:169041

CR Number:   169041 Product Name:   PB Enterprise Product Component:   DW - Runtime Status:   Closed OS:   MS Windows NT 4.0 Original Version:   6.0.01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 7.0.2 8034 18 Apr 2001 Fixed Description The Identity Column values that are retrieved in a datawindow after an update may give incorrect results if many users are inserting rows into the database at the same time.

CR:169062

CR Number:   169062 Product Name:   PB Enterprise Product Component:   PB GUI Status:   Closed OS:   Microsoft Windows 95 Original Version:   5.0.04 Fixed Version Build Resolution Date Closure Code (If Appropriate) 09 Sep 1998 Presently Not Targeted For Any Future Release Of This Product Description In Windows 3.1 or in Windows 19 (16 bit only) you cannor enter a filespec argument for the DirList function that uses the computer name instead of the drive designation. For example "q:\junk" works while "\\hawg\common\junk" does not.

CR:169080

CR Number:   169080 Product Name:   PB Enterprise Product Component:   Plug-ins 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 465 02 Sep 1999 Fixed Description Regression. Window Plugin generated w/PB 6.5 build 444 doesn't show up in browser.

CR:169128

CR Number:   169128 Product Name:   PB Enterprise Product Component:   Script Painter Status:   Closed OS:   Microsoft Windows 95 Original Version:   6.0.01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 6.5.00 01 Dec 1998 Fixed Description Default behaviour changed between PB 5.0 and PB 6.0. Cannot find documented reference to this change anywhere. Add code to a descendant event which has no code in the same event in the ancestor. Go back and add code to this ancestor event. When we return to the descendant event the new code in the ancestor has been OVERRIDDEN by default. In PB 5.0 this was EXTENDED by default.

CR:169132

CR Number:   169132 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) 7.x Catalina 1043 26 Apr 1999 Fixed Description In an N-Up datawindow, while trying to highlight a computed field via SelectRow in script, the text color changes to white and the columns are not highlighted. So if the datawindow background is white, they "disappear". True even when using [0], [1], etc to ensure that it is clear which row of data the computed field should be associated with. Possible workaround: perform calculations on the back end if possible, and return as part of the result set. Then the calculated data will be treated as regular columns by the nup datawindow, and SelectRow will work properly. Workaround Description  If possible, perform any necessary calculations on the back end and return them as part of the datawindow result set. They are then just part of the data, and SelectRow works fine on regular columns for Nup datawindows.

CR:169222

CR Number:   169222 Product Name:   PB Enterprise Product Component:   Library Painter Status:   Closed OS:   MS Windows NT 4.0 Original Version:   7.0.00 Beta 3 Fixed Version Build Resolution Date Closure Code (If Appropriate) 7.0.00 RC 4006 15 Dec 1998 Fixed Description Browsing in several areas of development (Library painter, File Editor) causes a working directory change that often causes applications not to run correctly afterwards since it no longer can find supporting ".ini" or other files. This has been an annoyance since 3.0 and is reported as a frustration by many customers. GetFileOpenName() and GetFileSaveName() have the same results at runtime. Once the working directory has changed, finding .ini files with ProfileString() calls often fail. Workaround: Reset the working directory by opening (expanding) a PBL in the directory that you want to be your working directory.

CR:169280

CR Number:   169280 Product Name:   PB Enterprise Product Component:   Language - Runtime Status:   Closed OS:   Microsoft Windows 95 Original Version:   6.0.01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 6.5.00 30 Oct 1998 Fixed Description calling a window-function with two call-by-value-parameters (windowobject and string) causes R0051 "bad argument list" in PB 5 and in PB6.0 a crash. Workaround Description  If the user donn't use the PFC of_register of pfc_n_cst_resize: change the order of the argument or use the any datatype

CR:169293

CR Number:   169293 Product Name:   PB Enterprise Product Component:   Plug-ins Status:   Closed OS:   MS Windows 3.1 Original Version:   6.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 09 Sep 1998 Presently Not Targeted For Any Future Release Of This Product Description Using 6.0 Plug-ins on win 3.11 browsers IExplorer / NNavigator results in different GPF's depending on the browser being used.

CR:169310

CR Number:   169310 Product Name:   PB Enterprise Product Component:   Language - Compiler Status:   Closed OS:   Microsoft Windows 95 Original Version:   6.0.01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 6.5.00 482 23 Oct 1998 Fixed Description When placing a non valid 2/29/XXXX value into a Date datatype it is accepted as a valid date value, This can result in wrong behavior when using DaysAfter() and displaying of value in SLE's, etc. . Other invalid dates (2/30/XXXX) are caught by the window initial compile. Simple workaround is to use the IsDate() on all dates entered in SLE's to insure that they are valid. Workaround Description  Use IsDate() on all dates entered in SLE to insure that they are valid.

CR:169338

CR Number:   169338 Product Name:   PB Enterprise Product Component:   DW Painter Status:   Closed OS:   MS Windows NT 4.0 Original Version:   6.0.01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 19 Apr 2001 Fixed Description Unable to create datawindows of source Stored Procedure with Informix if the Stored Procedure argument list has spaces or tabs Workaround Description  See Description

CR:169371

CR Number:   169371 Product Name:   PB Enterprise Product Component:   DB Sybase System Status:   Closed OS:   Microsoft Windows 95 Original Version:   6.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 6.5.00 575 12 Apr 1999 Fixed Description When intercepting the SQL order of a datawindow and replacing it with an EXECUTE of sp. using Setsqlpreview(). leads to an error message: " Row changed between Retrieve and Update." This happens with PB 5.0.04 and PB 6.0

CR:169396

CR Number:   169396 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) 6.5.00 21 Sep 1998 Fixed Description Application is using the Prompt for Criteria option, with a dddw with a data value that is an int and a display value that is a string, entering incorrect information results in an infinite loop. If instead of picking a choice from the dddw the user types a non-valid entry they initially receive the proper PB generated Messagebox - DataWindow Error Specified criteria is invalid! They can hit OK but at this point they will be trapped in an infinite loop that they can only get out of by shutting down the application using CTRL=>ALT=>DELETE. Initially it will let them hit cancel but trying to proceed to make a correct choice will put the user into the infinite loop. In PB 5.0.04 after the initial PB Messagebox for the DataWindow error the application allowed the user to enter a correct value or drop down the DDDW and pick from the list.

CR:169426

CR Number:   169426 Product Name:   PB Enterprise Product Component:   Web.PB Status:   Closed OS:   HP-UX 10.20 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 PROBLEM: Used build 444 & 522 on solaris and hpux. App server crashes when retrieving a nested or composite datawindow in webpb or retrieving using get/setfullstate. Works ok outside of webpb. Works ok on windows (build 444) in webpb. Works ok if I don't use a nested report. App server retrieves data ok. Problem happens using using distributed pb and calling remote method that's retrieving a nested report. Getting the following error on hpux: The error of Floating exception pb60 (core dumped) will appear on the unix command line. On solaris, the error is: signal fault in critical section signal number: 11, signal code 1, fault address: 0x0, pc: oxecfa35co, sp: 0xeb0058f8 ABORT: core dump Testing: Used apache web server on solaris and build 444 of pbcgi60.exe. App server was on hp and solaris. Also tried using website on nt 4.0 and app server running on hp and solaris. Same problem with pbcgi60.exe on windows.

CR:169430

CR Number:   169430 Product Name:   PB Enterprise Product Component:   Window - Runtime Status:   Closed OS:   HP-UX 10.20 Original Version:   6.0.01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 31 Oct 2002 Fixed Description When an app is running in cron and uses the run function to fire off a shell script, cpu usage will jump up to 98%. Doesn't happen in Solaris.

CR:169453

CR Number:   169453 Product Name:   PB Enterprise Product Component:   DW Printing 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 The problem has been reported in the past (PTs 465170, 333235, 460101, 314405, 269665). When a field within a datawindow is too wide or extends too far to the right for the size of paper to be printed on, the datawindow displays a second empty page regardless of the content of this field at runtime. Microhelp at bottom of datawindow in preview mode says "Horiz page 1 of 2" Instead of taking the runtime width and calculating when a second page is needed the datawindow seems to base its calculation of the static width of the field as defined in the datawindow painter so it shows an empty page when this is not necessary. For example a string field has a max width of 50 chars, when there is a string longer than 25 the field will not fit on 1 page so it prints on 2. But when this same field only has 1 char it still shows a second page even though it is blank. Customer would like the datawindow not to show this page when it's not needed by checking the runtime width of the column/field and not width as drawn in the datawindow painter (which is always the same, in this case 50) Workaround Description  Move column to the left or reduce its width either in the painter or dynamically.

CR:169558

CR Number:   169558 Product Name:   PB Enterprise Product Component:   Library Painter 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 Ct like to have a tool in the libvrary painter where he can remove automaticly the PVCS informations stored in PowerBuilder objects.

CR:169561

CR Number:   169561 Product Name:   PB Enterprise Product Component:   DW DDDW 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 * Dropdowndw jumps from left to right when it is larger than the dw control

CR:169599

CR Number:   169599 Product Name:   PB Enterprise Product Component:   DB Oracle Status:   Closed OS:   Microsoft Windows 95 Original Version:   6.0.01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 6.5.00 502 13 Nov 1998 Duplicate Description Oracle 8.0.3. Using a bind variable in the where clause does not bring back a result set.

CR:169724

CR Number:   169724 Product Name:   PB Enterprise Product Component:   MAPI Status:   Closed OS:   MS Windows NT 4.0 Original Version:   6.0.01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product Description PB 6.0 on NT4.0 / WIN95 using the function MAPI - MailReadMessage() didn't resolve the filename of the attachments. mailMessage / mailFileDescription structures are not filled with the right attachment file data.

CR:169752

CR Number:   169752 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) 04 Aug 1998 Duplicate Description A set of stacked reports in a composite datawindow does not paginate correctly. The second report on the stack always starts on the second page. In 5.0, if you had: Composite Parent Header report Composite Report #2 The "Composite Report #2" would start immediately after the Header Report on the FIRST page. (assuming the header report was less than 1 page). Now, in 6.5.00, when previewing or printing the report, if the entire "composite report #2" does not fit onto the remainder of the FIRST page, it is started on the SECOND page. Workaround: Place the Parent composite report above into another composite report and by adding one level, it previews and prints as expected. Workaround Description  Place entire report into another layer of composite report and it previewed and printed as expected.

CR:169822

CR Number:   169822 Product Name:   PB Enterprise Product Component:   DW Painter Status:   Closed OS:   HP-UX 10.20 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 Using build 444 on hpux, cpu usage goes up to 98% when dragging columns in the dw painter.

CR:169842

CR Number:   169842 Product Name:   PB Enterprise Product Component:   System Runtime Functions Status:   Closed OS:   HP-UX 10.20 Original Version:   6.0.01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 21 Jan 2000 Not a Bug Description The date() function returns inaccurate results. Under windows, you can modify the shortdate in the control panel/regional settings. Changed the sShortDate in the Intl section. Same problem. Workaround Description  duquette - 12/7/99 From Carlos Bokor: Change the iDate in the .Windu from iDate=0 to iDate=1. That worked for AIX,HP and solaris

CR:169864

CR Number:   169864 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) 7.0.3 04 Jul 2002 Fixed Description When the RightToLeft property of an editable control (sle, mle ..) is set at True, you can't change it to False inside a script. The opposite works. Workaround Description  Use the Api function LoadKeyboardLayoutA() (See attached pbl)

CR:169868

CR Number:   169868 Product Name:   PB Enterprise Product Component:   DW Painter Status:   Closed OS:   HP-UX 10.20 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 Regression - When selecting more than 22 columns for the rich text presentation style on Unix, pb will core dump. Ran a test using pb 5.0.04 on Solaris, no problem. I was able to select all 26 columns--no problem. Under pb 6.0.01 (build 444), pb will core dump on solaris. Ran another test on solaris (build 444) and selected only 20 columns. I then went back into the dw painter and selected the additional 6 columns 1 by 1 and added them to the dw. No problem. I then hit design/preview and the following error message appeared on the unix command line: MEM_BAD_MEM_POOL Abort, Ignore? (I then hit Ignore and the following message appeared) Premission denied All of this works under pb 5.0.04 on Solaris.

CR:169935

CR Number:   169935 Product Name:   PB Enterprise Product Component:   Edit Mask 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 In an editmask control defined as mm/dd/yyyy, enter 12/31/1999 and tab away. Click back on the editmask control and place the cursor between the digits of the year so that it is between the 1 and the 2. Hit the backspace key and the 12 will change to 02. You can now tab off of the control and the date that remains will be 02/31/1999. This may be correct behavior since at this point it is pretty difficult to anticipate what the user's next move will be, much like the situation where a spin control allows invalid dates, but user would like development determination. PER DEVELOPMENT: This works as designed. The editmask control does not check valididity when it loses focus. The DataWindow engine does check valididity when tabbing from one column to another which is why it fails there. Users should check themselves in the LoseFocus event. Workaround Description  Use a datawindow editmask control, and/or add date validation code to the control.