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

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

CR:202809

CR Number:   202809 Product Name:   PB Enterprise Product Component:   DW Edit Mask Status:   Closed OS:   MS Windows NT 4.0 Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 13 Apr 2000 Fixed Description BackSpace does not behave correctly with EM such as ##-##-##

CR:202815

CR Number:   202815 Product Name:   PB Enterprise Product Component:   Function Painter Status:   Closed OS:   Microsoft Windows 98 Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 02 Aug 1999 Duplicate Description When a non-visual object is loaded in the 'function painter', the powerbuilder environment will cause an application error and gpf. This sample non-visual object function has 110 arguments and the function object prototype cannot be loaded successfully in the 'function painter'. The sample NVO has 50 object functions. One of the object functions has 110 arguments.

CR:202821

CR Number:   202821 Product Name:   PB Enterprise Product Component:   DW Synchronization Status:   Closed OS:   MS Windows NT 4.0 Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 7.0.00 07 Sep 1999 Fixed Description 7.0 Regression. SetfullState crashes (GPF) when 64 or more rows are deleted or filtered first. Does not work in 7.0.1 build 6012.

CR:202837

CR Number:   202837 Product Name:   PB Enterprise Product Component:   DW - Runtime Status:   Closed OS:   MS Windows NT 4.0 Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 7.0.00 29 Mar 2000 Fixed Description I have a datawindow using the new stored procedure update feature. This DW works fine in every other way, but when I call GetFullState() on this DW I get the message "Row 22, Column 144: Invalid syntax." If I remove the stored procedure update option GetFullState() works as designed.

CR:202844

CR Number:   202844 Product Name:   PB Enterprise Product Component:   DW HTML Status:   Closed OS:   MS Windows NT 4.0 Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 25 Feb 2004 Fixed Description HTML Datawindow - Pictures on buttons or picture objects don't show in HTML Preview. The problem is two-fold: 1. Absolute paths in the painter when translated to HTML show ' e:\program files\common files\holes.gif ' which in a browser will never translate to a picture when you click on Design/HTML Preview. This is just a simple rendering for the datawindow painter. It's part of a more generalized problem in that the HTML generated (dw or ds.HTMLGen) should (suggestion) always be missing the full directory path or the code on the server should substitute into the datawindow where this is being generated (via dot notation) the actual Web Server Virtual directory path to the images stored on the web server - ie something like /images/holes.gif instead of e:\pb7\images\holes.gif) 2. The HTML DW source (dwtemp.html) is copied to the \windows\temp directory but the .gif files are not. The browser doesn't search the path for the .gif file. Since this html file is not returned by a server (with the .gif too), unless we physically check the dw for picture objects and copy the files to \windows\temp, they won't display in the painter. A workaround could be to copy the .gif files manually to \windows\temp, change the location of the .gif from FULL path (e:\pb7\images...) to simple filename "holes.gif" and try Design/HTML Preview again. (if the browser cache doesn't find the new page, you may have to click on the refresh or reload button or Control-Reload to get the new page.

CR:202847

CR Number:   202847 Product Name:   PB Enterprise Product Component:   DW - Runtime Status:   Closed OS:   Solaris 2.5.1 Original Version:   6.5.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product Description Solaris. Default datawindow button action build-in pictures (such as Filter, etc) display as black. Workaround: The user has the ability to use a workaround of using .bmp files on the hard drive for the datawindow button pictures. Workaround Description  This is not great but the user has the ability to use a workaround of using .bmp files on the hard drive for the datawindow button pictures.

CR:202861

CR Number:   202861 Product Name:   PB Enterprise Product Component:   Source Control Status:   Closed OS:   MS Windows NT 4.0 Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 7.0.00 7009 25 Feb 2004 Fixed Description Unable to check-out objects with source control with PB7 and ClearCase

CR:202862

CR Number:   202862 Product Name:   PB Enterprise Product Component:   OLE - Active X - OCX Status:   Closed OS:   Microsoft Windows 95 Original Version:   6.5.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 6.5.00 08 Jan 2001 Fixed Description PowerBuilder causes a GPF when you try to place a an MS Word Document OLE control on a window.

CR:202883

CR Number:   202883 Product Name:   PB Enterprise Product Component:   DB DirectConnect 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 1094 31 Oct 2002 Fixed Description DIR driver SQLErrText should return more information in SQLErrText for login and RSP failures

CR:202903

CR Number:   202903 Product Name:   PB Enterprise Product Component:   ORCA Status:   Closed OS:   MS Windows NT 4.0 Original Version:   6.5.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 6.5.1 1183 31 Oct 2002 Fixed Description Importing an object using CompileEntryImport through ORCA, when the object has a name that includes a foreign character with an accent mark, the import will fail with a -9 return code (Invalid Name) . If the name of the object is changed to not have the accented character, even if there are accented chartacters within the object it, will import correctly. The object will also import correctly from the library painter.

CR:202908

CR Number:   202908 Product Name:   PB Enterprise Product Component:   DPB Status:   Closed OS:   MS Windows NT 4.0 Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15 Jun 2004 EOL'd version. Not to be Fixed. Description 7.0 Regression. CreateInstance of sharedcomponent failing when running more than one client. With Machine code server application ONLY. Works fine with Pcode in all builds of 6.5 and 7.0. Worked fine using machine code server exe in 6.5.1. The second client application might fail with a R0002 Null Object Reference. The server log shows: SMI02 Connection <X> ERROR OCCURRED: The request caused an abnormal termination. The connection has been closed 80042008.It's Another possible message: You might get a createinstance error return value of 55, which is defined as request terminated abnormally. If you run just one client createinstance will succeed. If you create a pcode executable of the server app this will succeed.

CR:202910

CR Number:   202910 Product Name:   PB Enterprise Product Component:   Web.PB Status:   Closed OS:   Solaris 2.6 Original Version:   6.5.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product Description In webpb, when calling a function where it is saving multiple psr reports using the saveas function causes problems in PB. The problem only happens when the app server is compiled to pcode. Works ok in development and machine code. Works ok in distributed pb (client app and server app). Using a webserver and pbcgi60.exe, the error is: The instruction at 0x100034d5 referenced memory at 0x00000000. The memory could not be read. When you click ok, the following error message appears in the browser: CGI Error: The specified cgi application misbehaved by not returning a complete set of HTTP hearders. The headers it did return are: Also ran a test with pbisa60.dll and same problem but the error message was No document header

CR:202911

CR Number:   202911 Product Name:   PB Enterprise Product Component:   DW HTML Status:   Closed OS:   MS Windows NT 4.0 Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 25 Feb 2004 EOL'd version. Not to be Fixed. Description When a service class nvo is used for one web dw and instance pooling is set to true for the Jaguar generator component and then you go to a web dw that does not specify a service class nvo you will receive the error: on component call 'Generate' = 'Exception thrown: org.omg.Corba.Transaction_RolledBack:in method Generate of class DataWindow/_st_HTMLGenerator.'

CR:202912

CR Number:   202912 Product Name:   PB Enterprise Product Component:   DW - Runtime Status:   Closed OS:   MS Windows NT 4.0 Original Version:   6.5.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 6.5.00 1108 28 Mar 2000 Fixed Description 6.5.1/7.0.1 Regression. DDDW (DropDownDatawindow) does not scroll to and highlight associated row when arrow is clicked on the FIRST time. After the dddw column loses focus once, when the user clicks on the column, it then scrolls to and highlights the correct row. Fixed in 6.5 build 1108 and above and 7.0.1 build 7022 (after the MJD 7021 build - Modified Julian Date)

CR:202918

CR Number:   202918 Product Name:   PB Enterprise Product Component:   DW Graph 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 The following examples are from Crystal Reports. (a) All bands should be sub-dividable into multiple bands. (b) The sub-bands should each have their own attributes such as auto-size, 'suppress if empty', and 'suppress if true' based on a formula. A major use of this might be to have a variable heading. For example when printing an invoice you might want to show a lot of information such as the invoice number, customer's name and address, ship-to address, etc. on the first page but only show the customer name and invoice number on subsequent pages. In this case you could create a header-a and a header-b. Header-a would be printed for page 1 and header-b would be printed for all subsequent pages.

CR:202919

CR Number:   202919 Product Name:   PB Enterprise Product Component:   DW Graph 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 Add vertical and horizontal allignment bars. These will allow a group of fields or text to be aligned, locked together, and moved as a group. (as in Crystal Reports) There should also be a 'snap-to-allignment-bar' option. *I let cust know that while there are no allignment bars, there is a snap to grid option - and the granularity of the grid can be adjusted. You can also lasso or select several fields at once and move them as a group.

CR:202921

CR Number:   202921 Product Name:   PB Enterprise Product Component:   DW Graph 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 Enhance req: Graph title - need sub-title field with different font from main Title allows multiple lines, but all must be in the same font. There should be a sub-title field which can be a different font from the main title.

CR:202922

CR Number:   202922 Product Name:   PB Enterprise Product Component:   DW Graph 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: add footer and sub-footer bands to graph datawindows.

CR:202923

CR Number:   202923 Product Name:   PB Enterprise Product Component:   DW Graph 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 Ability to put a data table on the graph and have the legends appear as part of the data table. While it is possible to create a datawindow, I usually would use an n-up presentation style, and create a data table it is a lot of work and does not look as if it is really part of the graph. This is especially true when there are several series and it is necessary to have the series descriptions appear both as legends on the graph and as text on the data table.

CR:202924

CR Number:   202924 Product Name:   PB Enterprise Product Component:   DW Graph 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 Wants New graph type: High/Low/Open/Close/Volume

CR:202934

CR Number:   202934 Product Name:   PB Enterprise Product Component:   Business Graphics 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 3d dw graphs look fine at runtime (on the screen) in the painter but not when printed - they come out reduced in size - sometimes up to 50%. 3D Bar graphs seem to reduce the most..

CR:202976

CR Number:   202976 Product Name:   PB Enterprise Product Component:   OLE - Active X - OCX Status:   Closed OS:   MS Windows NT 4.0 Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 1188 03 Jan 2001 Fixed Description oleobject.IsAlive () leads to GPF

CR:202979

CR Number:   202979 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) 5.0.04 31 Aug 1999 Fixed Description You get error :"Select error: SQL Error -930 Can not connect to database server (ts_informix7), has occurred" when you attempt a retrieve as needed datawindow retrieve using the IN7 driver

CR:202980

CR Number:   202980 Product Name:   PB Enterprise Product Component:   DW Synchronization Status:   Closed OS:   MS Windows NT 4.0 Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 7.0.00 EBF1 07 Sep 1999 Fixed Description Got GPF when using SetChanges and if a date/datetime/time field is modified and its previous value was NULL

CR:203023

CR Number:   203023 Product Name:   PB Enterprise Product Component:   Project Painter Status:   Closed OS:   MS Windows NT 4.0 Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 03 Jan 2001 Fixed Description Executing a COM/MTS project leads to generate an exe file instead of dll file Workaround Description  One or the other . 1- Export the project , change the decimal separator of the GENVERSION banner so that it matches the one in the regionnal settings & reimport the project. 2 -decimal symbol set to "." before starting powerbuilder all will work fine.

CR:203026

CR Number:   203026 Product Name:   PB Enterprise Product Component:   DW - Runtime Status:   Closed OS:   MS Windows NT 4.0 Original Version:   6.5.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 6.5.00 1098 08 Aug 2000 Fixed Description 6.5 Regression. Datawindow with outer joins and 350 columns retrieving over 50000 rows causes "out of memory" message before pagefile is exhausted.

CR:203053

CR Number:   203053 Product Name:   PB Enterprise Product Component:   DB OLE DB Status:   Closed OS:   MS Windows NT 4.0 Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 27 Apr 2001 Fixed Description OLE DB: Executing a stored procedure that has another SQL command before the SELECT that returns the result using SQLOLEDB provider causes access violation in address 0x14f18854 in SQLOLE70.DLL. This is a problem with the Microsoft provider SQLOLEDB - MSDASQL works fine.

CR:203064

CR Number:   203064 Product Name:   PB Enterprise Product Component:   Machine Code Exe Creation Status:   Closed OS:   MS Windows NT 4.0 Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15 Jun 2004 EOL'd version. Not to be Fixed. Description Building a PFC peat application machine code executable aborts (GPFS). The object most often noted is pfc_n_cst_filesrvunicode. This doesn't seem to have the autoinstantiate problem that was fixed in 7.0 GA in PFC. This issue is the same as Change Request 188839. This issue found the problem to be a variable is set to "~142" could not be compiled. pfc_n_cstfilesrvunicode happens to be the first one the compiler hits - all of the pfc_n_cstfilesrv(hpux,win32,aix,sol2) have this coded somewhere.

CR:203088

CR Number:   203088 Product Name:   PB Enterprise Product Component:   Jaguar Integration Status:   Closed OS:   MS Windows NT 4.0 Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 25 Feb 2004 EOL'd version. Not to be Fixed. Description CreateInstance of shared comp fails in Start method of a PB Jag Services comp. Do the createinstance in the Run method, or: Go to the All Properties for the server and set com.sybase.jaguar.server.bindrefresh = start This will cause the nameservice to build its bindings in start() instead of run(). Workaround Description  Do the createinstance in the Run method, or: Go to the All Properties for the server and set com.sybase.jaguar.server.bindrefresh = start This will cause the nameservice to build its bindings in start() instead of run().

CR:203119

CR Number:   203119 Product Name:   PB Enterprise Product Component:   DW Painter Status:   Closed OS:   MS Windows NT 4.0 Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 22 Mar 2000 Fixed Description Alignment is not saved in the dw when using in the propertie tab the alignment ddlb. works fine if you use toolbar or if you do it dynamicly. workaround: use toolbar Workaround Description  use toolbar

CR:203130

CR Number:   203130 Product Name:   PB Enterprise Product Component:   DB OLE DB Status:   Closed OS:   MS Windows NT 4.0 Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0 Beta 2 23 Jul 2004 Fixed Description OLEDB. Binding for database/datawindow painter datatypes in the table listing appears not to be working. MS SQL Server 7 via OLEDB with Microsoft SQLOLEDB provider. In the database if the column is varchar, PB7 shows as a char. In the database if the column is datetime, PB7 shows as smalldatetime. In the database if the column is money, PB7 shows as smallmoney. In the database if the column is numeric, PB7 shows as decimal. In the database if the column is nvarchar, PB7 shows as nchar. In the database if the column is varbinary, PB7 shows as binary. The datawindows created from these are generally correct. Varchar and char become char in the datawindow and so on. The worst one is the Money datatype since it becomes Decimal(0) in the datawindow instead of Decimal(4). Powerbuilder uses can export the syntax. Datawindow Builder users (PowerJ) and InfoMaker cannot fix this and the fractional part will be truncated to "0"

CR:203139

CR Number:   203139 Product Name:   PB Enterprise Product Component:   DB OLE DB Status:   Closed OS:   MS Windows NT 4.0 Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0 Beta 1 28 Jun 2001 Fixed Description OLEDB Microsoft SQL Server. Outer Joins not allowed in Join Selection dialog. Also, if you have a datawindow containing an outer join in the where clause and you examine it using the OLEDB interface, you'll see it blows away the where clause to something like: WHERE () or WHERE |||

CR:203142

CR Number:   203142 Product Name:   PB Enterprise Product Component:   DPB Status:   Closed OS:   Solaris 2.6 Original Version:   6.5.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 6.5.00 14 Oct 1999 Fixed Description The customer is unable to connect to their Sybase database and run a shell script in their distributed/web.pb application when it is run as a deployed executable. This scenario works fine in development mode for the customer. I was able to reproduce the problem the customer was experiencing and also reproduce a memory leak issue that I am also working on (CR 201638). I am able to run my sample application a total of 33 times in development, but only managed to get it to run 3 times as a deployed PCode executable. This was tested against build 565 of PowerBuilder 6.5 on Solaris 2.6 also using Stronghold Web Server (Apache)

CR:203154

CR Number:   203154 Product Name:   PB Enterprise Product Component:   Generators Status:   Closed OS:   MS Windows NT 4.0 Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 25 Feb 2004 EOL'd version. Not to be Fixed. Description This could possibly be the same issue as CR 188549 although that was determined to be a 6.5 issue only. This exhibits similar symptoms of memory loss when the component simply creates and destoys a datastore on a component on Microsoft Transaction Server. The memory does not appear to be released until PB itself is shut down. My results of memory usage when running the sample under NT 4.0 are as follows: Initial 77068K Start PB 81972K Start App 82144K 1st run 83340K 2nd run 83480K 3rd run 83524K Close App 83440K Close PB 77068K

CR:203168

CR Number:   203168 Product Name:   PB Enterprise Product Component:   DW HTML Status:   Closed OS:   MS Windows NT 4.0 Original Version:   7.x Catalina Fixed Version Build Resolution Date Closure Code (If Appropriate) 16 Mar 2004 EOL'd version. Not to be Fixed. Description To reproduce: change the raise % from 5 % to 10 % and then changed it back to 5 % the error item does not pass validation appears. The solution is to change the static value .05 to .06 as shown below SELECT "DBA"."employee"."emp_fname", "DBA"."employee"."emp_lname", "DBA"."employee"."birth_date", "DBA"."employee"."salary", "DBA"."employee"."ss_number", "DBA"."employee"."emp_id", "DBA"."employee"."dept_id", "DBA"."department"."dept_name",.06 FROM "DBA"."employee", "DBA"."department" WHERE ( "DBA"."employee"."dept_id" = "DBA"."department"."dept_id" ) and ( ( "DBA"."department"."dept_id" = :deptid ) ) And then to change the data values from .06, .1, .15, .20 etc to 0.06, 0.10, 0.20 etc.

CR:203174

CR Number:   203174 Product Name:   PB Enterprise Product Component:   Window Painter Status:   Closed OS:   MS Windows NT 4.0 Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 08 Aug 2000 Not reproducible with latest version of the product available as of Resolution Date Description Placing a large number of tabpages onto a tabcontrol gpf's on saving in PB 7.0 on NT 4.0 only. PB 6.5 and Catalina do not appear to exhibit the problem.

CR:203178

CR Number:   203178 Product Name:   PB Enterprise Product Component:   DW HTML Status:   Closed OS:   MS Windows NT 4.0 Original Version:   7.x Catalina Fixed Version Build Resolution Date Closure Code (If Appropriate) 16 Mar 2004 EOL'd version. Not to be Fixed. Description This button shoulud be removed or the DataWindow made updateable.

CR:203180

CR Number:   203180 Product Name:   PB Enterprise Product Component:   Installation Status:   Closed OS:   MS Windows NT 4.0 Original Version:   7.x Catalina Fixed Version Build Resolution Date Closure Code (If Appropriate) 16 Mar 2004 EOL'd version. Not to be Fixed. Description It is only added to the HKEY_LOCAL_MACHINE\Software\Sybase\Sybase Central\Profiles registry key. It should also appear under HKEY_CURRENT_USER. I assume this is the fault of the install program When creating a profile using Sybase Central it places information in both trees. It is a problem because the profile does not show up when selecting Tools, Connection Profiles.

CR:203181

CR Number:   203181 Product Name:   PB Enterprise Product Component:   DW HTML Status:   Closed OS:   MS Windows NT 4.0 Original Version:   7.x Catalina Fixed Version Build Resolution Date Closure Code (If Appropriate) 16 Mar 2004 EOL'd version. Not to be Fixed. Description To Reproduce: Open the HTML DW sample provided with EA Studio Click on Scott to open manager details Notice that the phone field contains a client side formatting of (617) 555-3246 click on the phone number Notice that it changes to 6175553246 Click it again Notice that it changes to (617) 555-3246 Now make a change to it and tab off the field Notice that the phone number is now messed up and if the update button is pressed it fails.

CR:203209

CR Number:   203209 Product Name:   PB Enterprise Product Component:   DB OLE DB Status:   Closed OS:   MS Windows NT 4.0 Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 7.x Catalina 8015 27 Mar 2000 Fixed Description Timestamps cannot be used in OLE DB to MS SQLServer. When trying to create a DataWindow from a table with a timestamp column or selecting timestamp in an ISQL session: Error: This column's data type (timestamp) requires the use of an embedded SQL statement. occurs

CR:203221

CR Number:   203221 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 have a datawindow based on a stored procedure with retrieval arguments enter retrieval arguments through the argument prompt put up by PowerBuilder, when you enter "NULL" for a numeric argument, 0 is passed as the argument. When you enter "NULL" as a data arguemnt, a format error occurs. Workaround Description  Do not rely on PowerBuidler to prompt for the retrieval arguments. Instead promt for them using script and incude them when the <dw>.Retrieve() is executed.

CR:203224

CR Number:   203224 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 1110 28 Mar 2000 Fixed Description Page numbering on datawindow printed reports may be incorrect. The problem is the Page() datawindow function. The grey box that echos the current page in print preview seems to show the correct page but the Page() computed field in the header shows 3 pages for 1 real page. IE Page 1 of 40, 1 of 40, 1 of 40 for pages 1-3 then page 4,5,6 is page 2 of 40 - I guess it may depend on the datawindow size at the time. This happens most often when the data for a particular row is beyond the 1 page limit of the datawindow for a single detail row.

CR:203226

CR Number:   203226 Product Name:   PB Enterprise Product Component:   DW HTML Status:   Closed OS:   MS Windows NT 4.0 Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 25 Feb 2004 EOL'd version. Not to be Fixed. Description There is a property on the HTML Table tab of a datawindow where you can assign a style sheet to the datawindow. Anything you enter there is ignored, though. The style sheet does not end up being included in the HTML that is generated. Workaround: Assign the style sheet from within Powersite instead of PowerBuilder.

CR:203243

CR Number:   203243 Product Name:   PB Enterprise Product Component:   PB GUI Status:   Closed OS:   MS Windows NT 4.0 Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 18 Jul 2000 Duplicate Description Closing the Find Dialog by click the X close box will cause PowerBuilder 7 to hang or GPF. to reproduce 1. open a window which contains a command button with a script 2. right click on command button and chose script 3. place cursor at beginning of clicked script 4. right click and chose find from pop-up 5. put a short string which is included in the script as the string to find and click find next 6. after the first th is found click the x button in the top right corner of the find dialog. PowerBuilder will gpf, hang or shutdown

CR:203244

CR Number:   203244 Product Name:   PB Enterprise Product Component:   DW - Runtime Status:   Closed OS:   MS Windows NT 4.0 Original Version:   6.5.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 6.5.00 1096 29 Mar 2000 Fixed Description Accessing the dwo.type attribute in the clicked, rbuttondown and other events in a CROSSTAB datawindow causes a R0039 Application Execution error. " Error accessing external object property TYPE at line xxx in clicked event..." Other simple datawindow types (grid, tabular) work fine.

CR:203246

CR Number:   203246 Product Name:   PB Enterprise Product Component:   DW Painter Status:   Closed OS:   MS Windows NT 4.0 Original Version:   5.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 Customer wants to eliminate {oj .... } requirement that populates the ddlb of table names in "update Properties"

CR:203254

CR Number:   203254 Product Name:   PB Enterprise Product Component:   DW Printing Status:   Closed OS:   MS Windows NT 4.0 Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 25 Feb 2004 EOL'd version. Not to be Fixed. Description Enhancement. Powerbuilder size ID for paper size should be transparent to the printer for the most common sizes of print jobs. Powerbuilder saves the Size attribute as a numeric specific to the printer used when creating the datawindow. When printers are switched, the ID might represent a different SIZE PAPER for the new printer causing problems.

CR:203288

CR Number:   203288 Product Name:   PB Enterprise Product Component:   DW - Runtime Status:   Closed OS:   MS Windows NT 4.0 Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 7.x Catalina 02 Sep 1999 Fixed Description when you select a new item in a dddw and press a tab key fast enought aftes the selection you get a gpf 0x7800fa15. This happen in preview and in runtime.

CR:203294

CR Number:   203294 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) 31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product Description Machine code executable only problem : The call::super statement crashes in machine code when the event is a user event that returns a string parameter, it does not crash with a long return value. The same crash oocurs when the ancestor script of the user event is not overridden and both ancestor and descendant have script in the event. Workarounds : - Override the ancestor script - Do not write any code in the descendant event but e.g. use an ancestor instance variable - Override ancestor script and call the ancestor using the new syntax (without the Call keyword), for example : string s s = super:: event get_string()

CR:203309

CR Number:   203309 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) 31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product Description Customer would like to have the ability to reference more than one database within a single connection. Requested specifically for Informix, but many back ends allow this by fully qualifying table names with the database name.

CR:203341

CR Number:   203341 Product Name:   PB Enterprise Product Component:   Documentation Status:   Closed OS:   MS Windows NT 4.0 Original Version:   7.x Catalina Fixed Version Build Resolution Date Closure Code (If Appropriate) 19 Sep 2000 Not a Bug Description DOCUMENTATION. Missing PBDWDynamic, PBBlobDynamic for pbodb70.ini. These control whether we piggyback a connection with retrieveasneeded (using PBDWDynamic) and Blob columns contained in datawindows (PBBlobDynamic). These settings work in ODBC but only with SOME drivers.

CR:203353

CR Number:   203353 Product Name:   PB Enterprise Product Component:   DW HTML Status:   Closed OS:   MS Windows NT 4.0 Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 25 Feb 2004 EOL'd version. Not to be Fixed. Description Create a datawindow with a dropdown datawindow column. Deploy it as a Web datawindow. (Include an Insert button, and if required, Next and Prior buttons. Click the Insert button. Tab to the new row, then tab to the dddw column. Click the down arrow. It does nothing, and no value displays in the column. Click the up arrow instead. You'll see the last item in the list display, and you can arrow up through them.

CR:203401

CR Number:   203401 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) 28 Mar 2000 Fixed Description If Object.DataWindow.Retrieve.AsNeeded property is set to 'yes' then it is not possible to see all the rows in the datawindow. This defect appeared from build 645 to 655 of Powerbuilder 6.5 and can be reproduced in PB 7.0.01. The workaround is made of the last 2 lines integer li_row dw_1.settransobject(sqlca) dw_1.Object.DataWindow.Retrieve.AsNeeded='yes' dw_1.retrieve() li_row = dw_1.insertrow(1) dw_1.deleterow(li_row) Workaround Description  The workaround is made of the last 2 lines integer li_row dw_1.settransobject(sqlca) dw_1.Object.DataWindow.Retrieve.AsNeeded='yes' dw_1.retrieve() li_row = dw_1.insertrow(1) dw_1.deleterow(li_row)

CR:203424

CR Number:   203424 Product Name:   PB Enterprise Product Component:   DW HTML Status:   Closed OS:   MS Windows NT 4.0 Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 7.0.2 9027 05 Dec 2000 Fixed Description HTML datawindow generated output missing data if you place a column from the SELECT statement in the FOOTER or SUMMARY band. It appears to be OK in all the other bands. including GROUP HEADER, DETAIL and GROUP TRAILER

CR:203438

CR Number:   203438 Product Name:   PB Enterprise Product Component:   DW - Runtime Status:   Closed OS:   Microsoft Windows 95 Original Version:   7.0.00 RC1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12 Aug 1999 Not a Bug Description With Control panel regional settings set to Swedish, datawindow.find("col_id=10,10") fails. dw.find("col_id=10.10") still works. Per development, this is not a bug. In DW expressions, '.' must be used as the decimal place. Workaround Description  dw.find("col_id=10.10") still works.

CR:203467

CR Number:   203467 Product Name:   PB Enterprise Product Component:   DW Painter Status:   Closed OS:   MS Windows NT 4.0 Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16 Oct 2000 Not a Bug Description Can't type the letter 'p' in the datawindow painter to change a text box or any property or computed field. The View/Preview menu pick has a shortcut of 'p' causing this problem. The user might have a few shortcuts defined - one with 'P'. The default datawindow layout setting restored ON STARTUP of the datawindow painter IF THE REGISTRY KEY HKEY_CURRENT_USER\Software\Sybase\Powerbuilder\7.0\Layout\Default\Datawindow is missing has the View/Preview [p] using a shortcut of 'p' - it should have no shortcut. When the datawindow is fully previewed, the View menu is disabled and the user is unable to type a "P" anywhere in the datawindow painter at this point. NOTE: If the user goes to Design/Options/Layout 'tab' and clicks on the "Default" button to restore the default layout in the datawindow painter, it DOES NOT make View/Preview with a 'p' shortcut. There seems to be some leftover beta initialization code that puts the View/Preview[p] on startup if it doesn't find the 'datawindow' layout key. When the user actually uses the product to set the default in the painter, no shortcut is created and the painter works OK.

CR:203522

CR Number:   203522 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 1111 28 Mar 2000 Fixed Description Using Pb6.5.1 and running an application that retrieves datas in a tabular datawindow that holds a VScrollBar and a HScrollBar, the VScrollbar overlaps last column, if application was previously created with pb6.5.

CR:203545

CR Number:   203545 Product Name:   PB Enterprise Product Component:   Script Painter Status:   Open OS:   MS Windows NT 4.0 Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description Enhancement. Increase size of script (64k limit) /embedded SQL (32k string) limits.

CR:203575

CR Number:   203575 Product Name:   PB Enterprise Product Component:   DW Display Status:   Closed OS:   MS Windows NT 4.0 Original Version:   6.5.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product Description When moving columns (3D Raised Border) between each other in a Grid datawindow, the border between the header of the coloumns are not correctly repainted.

CR:203595

CR Number:   203595 Product Name:   PB Enterprise Product Component:   DW - Runtime Status:   Closed OS:   MS Windows NT 4.0 Original Version:   6.5.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 6.5.00 07 Sep 1999 Fixed Description SetFilter/Filter and update on a DW with 'use delete then insert' generate a GPF

CR:203604

CR Number:   203604 Product Name:   PB Enterprise Product Component:   DW - Runtime Status:   Closed OS:   MS Windows NT 4.0 Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 27 Apr 2001 Fixed Description dw.clipboard function does not work as documented. The documentation states the following, but this does not work: Calling Clipboard in a DataWIndow control or DataStore object To retrieve or replace the contents of the system clipboard with text from a DataWindow column, you must call Clipboard using the pronoun Super:: as follows: Super::Clipboard("Employee Data") The Super pronoun points to the system function version of the Clipboard function instead of using the DataWindow version. The DataWindow version of Clipboard, documented in Syntax 2, is only applicable to graphs. WORKAROUND 1: use the Copy() function instead. I believe this is a documentation error, and the clipboard function would not be expected to work as documented, but development will make final determination. WORKAROUND 2: Define a new function eg. wf_clipboard (string a_clipdata) and in the function just call the clipboard(a_clipdata) function. In the datawindow event call wf_clipboard("string to paste to clipboard").

CR:203635

CR Number:   203635 Product Name:   PB Enterprise Product Component:   DW Display 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 This request is an enhancement for rotated text within the datawindow. Currently the background is rotating with the text , but not the border. In particular with a font escapement of 900 (vertical text) the enhancement is to have the border positioned properly around the text.

CR:203636

CR Number:   203636 Product Name:   PB Enterprise Product Component:   Edit Mask Status:   Closed OS:   MS Windows NT 4.0 Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 7.0.2 06 Jul 2000 Fixed Description PB 7: EditMask control with Mask : xxxxxx and MaskDataType : StringMask! or datawindow editmask with (uppercase) mask like '!!!!!!!' Typing in some characters (the number of characters must be smaller than the length of the mask in either the window control or the datawindow string column) causes pb 7 to add spaces to fill out the column when the user TABs off the datawindow column or editmask control.. . In PB 6.5 no spaces are added. Possible Workaround: Use the trim() function to remove leading and trailing spaces from a string. Fixed in 7.0.2 ebf codeline (build 8014)

CR:203663

CR Number:   203663 Product Name:   PB Enterprise Product Component:   Window Painter Status:   Closed OS:   MS Windows NT 4.0 Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 7.0.00 7013/1130 01 Jan 2001 Fixed Description Window migrated from 5.0 to 7.0 cannot be modified in 7.0. Any attempt to change the code, even by adding a comment, causes PowerBuilder to crash. This is an extremely large window with many datawindows and tab controls. The root cause of the problem has not yet been isolated. No other similar cases have been reported to date.

CR:203668

CR Number:   203668 Product Name:   PB Enterprise Product Component:   DW Rich Text Status:   Closed OS:   MS Windows NT 4.0 Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 27 Apr 2000 Fixed Description 6.0 and 7.0 Regression. RTF datawindow Print Specifications setting papersize and paper source no longer works in 6.0. These worked fine in 5.0.04. Orientation seems to be OK (see note below) NOTE: In 5.0.04, 6.0, 6.5+ and 7.0, orientation 'sort of' works in that it lists Default, Portrait and Landscape but there is also a blank row at the end of the list so even Orientation is messed up.

CR:203673

CR Number:   203673 Product Name:   PB Enterprise Product Component:   MTS Integration Status:   Closed OS:   MS Windows NT 4.0 Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 7.0.3 10065 25 Feb 2004 Fixed Description Can't return a resultset from a component deployed to MTS as a by ref argument Workaround Description  Return the resultset as a _return_ value rather than a byref arg.

CR:203730

CR Number:   203730 Product Name:   PB Enterprise Product Component:   WT - Object Model Status:   Closed OS:   MS Windows NT 4.0 Original Version:   7.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16 Mar 2004 EOL'd version. Not to be Fixed. Description To reproduce <HTML> <!--SCRIPT PSOBJMOD=TRUE import( site.GetRootDocument().location + "/ObjMod.ssc" ); session.active = true; InitObjects(session); --> <!--SCRIPT myString = new String "Hello world, hello"; sampleString=myString.substring(5,11); document.WriteLn("sampleString="+sampleString); --> </HTML> Produces Warning: undefined variable myString.substring[substring] This is because in the objmod.ssc there is a function String(x) { return (x) } Workaround Description  Instead of using myString = new String "Hello world, hello"; use myString = "hello world, hello";

CR:203735

CR Number:   203735 Product Name:   PB Enterprise Product Component:   System Runtime Functions 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 PB6 and PB7 probblem : When in a script an Autoinstiated UserObject is assigned to an any instance variable for the second time, the class of the ANY variable errornously changes to type "string". This does not happen in an identical situation when the ANY variable is a local variable. Workarounds : - use a PowerObject instead of an ANY variable - set the ANY variable to NULL before the assignment

CR:203763

CR Number:   203763 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) 31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product Description Memory associated with a large string array is returned to OS when string goes out of scope.

CR:203803

CR Number:   203803 Product Name:   PB Enterprise Product Component:   DB Oracle Status:   Closed OS:   MS Windows NT 4.0 Original Version:   5.0.04 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15 May 2002 Fixed 11 Jul 2002 Fixed Description OR8/O84 GPF when sql statement contains '->' characters Workaround: Connect with O73 driver

CR:203805

CR Number:   203805 Product Name:   PB Enterprise Product Component:   Menu Painter Status:   Closed OS:   MS Windows NT 4.0 Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 1136 16 Jun 2000 Fixed Description In the menu painter, the shortcut 'Ins' is displayed as 'Del'

CR:203824

CR Number:   203824 Product Name:   PB Enterprise Product Component:   Edit Mask Status:   Closed OS:   MS Windows NT 4.0 Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 06 Jul 2000 Fixed Description String edit mask control doesn't allow further input after the first space character Workaround: append spaces at the end of the edit maskand type another character, e.g. dash; examplefor Mask: "aaa ##########" Woraround: "aaa ########## -"

CR:203826

CR Number:   203826 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) 20 Oct 1999 Not a Bug Description Customer has a freeform datawindow with a large number of fields. It worked in 5.0.04, but when they migrated to 6.5 and 7.0, they can no longer scroll to the bottom of the datawindow. Using the scrollbar causes the datawindow to scroll to the next record rather than to scroll down to the bottom of the datawindow so you can see the remaining fields in the current record. The problem occurs in both the painter in preview and at runtime. NOT A BUG: Per development: Error in the design of the user's DataWindow -- when InfoMaker constructs a Form, it creates a DataWindow with a fixed-height Detail Band, with a height larger than the page. The DataWindow looks for this configuration to identify an IM Form. In 6.5+ we had to formalize the Form definition as being Fixed-Height. In 5.0 it did not matter but, with the LiveScrolling enhancements of 6.5+, we needed the additional condition. Somehow the DW in the test suite has been given an erroneous AutoSizeHeight property on its Detail Band -- probably through manipulations in PB. Turn this flag off and the DW once again behaves like an IM Form. NOTE: this will be the case for any datawindow, whether created in Infomaker or PowerBuilder. If the detail band is larger than the "page" (which in the case of display on a window means the datawindow control itself) then you must turn AutosizeHeight off in order to have the scrolling work the way the customer wants.

CR:203870

CR Number:   203870 Product Name:   PB Enterprise Product Component:   Window - Runtime Status:   Closed OS:   Microsoft Windows 95 Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 7.0.00 19 Dec 2000 Fixed Description *** 7.0 REGRESSION *** StaticText control with DragAuto property checked (=TRUE), cannot drag control @runtime. This can be a StaticText control placed directly on a window or a user object of type StaticText. This appears to be the only control that is having this problem.

CR:203893

CR Number:   203893 Product Name:   PB Enterprise Product Component:   DW - Runtime Status:   Closed OS:   Microsoft Windows 95 Original Version:   7.0.00 RC1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 7.0.00 7013 23 Sep 1999 Not reproducible with latest version of the product available as of Resolution Date Description PB 7.0.1 regression: datawindow update when many rows are filtered GPFs. Verified fixed in build 7013.

CR:203928

CR Number:   203928 Product Name:   PB Enterprise Product Component:   Documentation Status:   Closed OS:   MS Windows NT 4.0 Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16 Oct 2000 Added to user documentation Description Current limitation of the datawindow is that a single detail row (with all it's nested reports if any) requirement must fit on a page. Common problems seen: 1. The last DETAIL line on the page will repeat as the FIRST line on the next page (after whatever header or group header) in the printed output. There are exceptions but often this happens when using Long text fields (multiline 'memo' like fields that go beyond a page). 2. The datawindow can cause another behavior called "clipping" which could be severe in print preview. Whole lines might be partially clipped. Generally these print better than they display. Playing with print preview Zoom factors often help in some cases but not all. THIS IS NOT EXACTLY RELATED to the '1 page for a detail row' limit but is often reported as the same. You can reproduce this with 3 lines of a long text column that is much less than 1 page. This second problem is due to the text box on the screen which we translate from a printer box on the printer. The inaccuracy of translating printer lines to screen lines (due to resolution differences 600dpi to pixels on screen, rounding of font sizes used) causes this problem.

CR:203954

CR Number:   203954 Product Name:   PB Enterprise Product Component:   DW Painter Status:   Closed OS:   Microsoft Windows 98 Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16 Mar 2000 Fixed Description The problem is that PB7 does not save the Border property value if other than 0(zero). PB defaults to value No Border(0) on a computed field in a datatwindow design mode when asked to save a different value e.g.border="5" Lowered Workaround Description  Workarounds: 1) In design mode: Set an expression for the computed field e.g. 5 ; This will display the computed column with Lowered border style. 2) In the PB script, change the border value dynamically before displaying the datawindow

CR:203969

CR Number:   203969 Product Name:   PB Enterprise Product Component:   Language - Compiler Status:   Closed OS:   MS Windows NT 4.0 Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16 Mar 2004 EOL'd version. Not to be Fixed. Description Please add compiler warning that func().struct_member should not be used. See CR 199826 for more details.

CR:204004

CR Number:   204004 Product Name:   PB Enterprise Product Component:   Edit Mask Status:   Closed OS:   MS Windows NT 4.0 Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 19 Apr 2000 Fixed Description The edit mask date with a spin control is not initialized to the current date Workaround Description  Initialiaze the edit mask by script.

CR:204005

CR Number:   204005 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) 07 Sep 1999 Duplicate Description Memory leak when setFullState is called on a datastore

CR:204020

CR Number:   204020 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 Filtering a decimal column in Print Preview mode of the Datawindow painter causes a GPF.

CR:204041

CR Number:   204041 Product Name:   PB Enterprise Product Component:   DW Edit Mask Status:   Closed OS:   MS Windows NT 4.0 Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 25 Feb 2004 Fixed Description Spin Max = 0 is equivalent to having no max at all. This has been reproduce since Powerbuilder 5.0.04. As a workaround, use a max value for the spin control greater than 0 and lower than the spin increment . Workaround Description  Indicate Max=0.1 as an example for the spin control

CR:204046

CR Number:   204046 Product Name:   PB Enterprise Product Component:   P-Code Deployment Status:   Closed OS:   Microsoft Windows 98 Original Version:   6.5.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 25 Oct 1999 Third Party Problem Description Fatal Disk Error when using NetTech radio frequency transmission software

CR:204146

CR Number:   204146 Product Name:   PB Enterprise Product Component:   DW - Runtime Status:   Closed OS:   MS Windows NT 4.0 Original Version:   6.5.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 6.5.00 1108 27 Mar 2000 Fixed Description DataWindow access violation with statement in visible property

CR:204147

CR Number:   204147 Product Name:   PB Enterprise Product Component:   Script Painter Status:   Closed OS:   Microsoft Windows 95 Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 30 Nov 2000 Duplicate Description In any PB script painter, if you close the Find window using the control menu, PB dies and leaves the PB window on the desk top.

CR:204215

CR Number:   204215 Product Name:   PB Enterprise Product Component:   Script Painter Status:   Closed OS:   MS Windows NT 4.0 Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 7.0.00 18 Jul 2000 Fixed Description 7.0 Regression. The Find dialog used in the script painter is now modal. The user used to be able to type behind the find dialog to fix errors (like Word or any other find dialog in windows.) 5.0 and 6.0 allowed the user to edit behind the find dialog. Additionally, closing the find dialog via the X in the upper right corner closes the window, but doesn't give focus back to PowerBuilder rendering PowerBuilder development environment inaccessible. The Powerbuilder development environment is in a weird state where it doesn't even show up on the taskbar and you can't do work or get out of PB without killing it from the task manager.

CR:204227

CR Number:   204227 Product Name:   PB Enterprise Product Component:   Window - Runtime Status:   Closed OS:   MS Windows NT 4.0 Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15 Jun 2004 EOL'd version. Not to be Fixed. Description Listview setcolumn() function does not handle the alignment in the right way. If you use setcolumn on a listview the alignment is not diplayed right. The rows are not aligned after the function call. If you click on rows the alignment will change to the alignment you set with setcolumn().

CR:204228

CR Number:   204228 Product Name:   PB Enterprise Product Component:   DW Printing Status:   Closed OS:   MS Windows NT 4.0 Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 25 Feb 2004 EOL'd version. Not to be Fixed. Description The current settings for paper source and paper size in the datawindow are numeric. They are based on RELATIVE position of the pick in the print specifications dialog - specifically the Paper Size and Paper Source settings have the most problems. If a user creates a custom FORM style and calls it "My Form" and associates it in the "Paper Size" attribute, it will get a relative position. Default Letter 8 1/2 x 11 in Letter small 8 1/2 x 11 in Legal 8 1/2 x 14 in Executive 7 1/4 x 10 1/2 in A4 210 x 297 mm My Form This is at position 7. But on another machine, there may be multiple other user-defined forms so "My Form" might be number 11 in the form and this causes a problem. Saving a setting as for example 8.5 x 11 in one printer driver (relative position 1) might translate to 11 x 19 inches in another driver (relative position 1). Workaround: Get the current form list from the HKEY_LOCAL_MACHINE registry setting: // This example creates the list of Forms in the numeric order. How the user can manipulate this with // Modify() on each desktop can be tricky but is doable. string ls_valuearray[] long ubound,i RegistryValues("HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Print\Forms",& ls_valuearray) ubound = upperbound(ls_valuearray) FOR i=1 TO ubound lb_1.additem(ls_valuearray[i]) NEXT Also reference Microsoft Articles: Q157172 - How to Create Custom Forms in Windows NT 4.0 Q183693 - Cannot Choose Custom Forms on HP III and HP 4 Family Printers

CR:204242

CR Number:   204242 Product Name:   PB Enterprise Product Component:   Menus - Runtime Status:   Closed OS:   MS Windows NT 4.0 Original Version:   6.5.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product Description Using cascading menus, if you disable the menu item which the cascaded menu "hangs off of", although the cascaded menu items are disabled when accessed from the menu, (you cannot get to them) if you use a shortcut key defined for the menu, the shortcut key still works.

CR:204286

CR Number:   204286 Product Name:   PB Enterprise Product Component:   Machine Code Deployment Status:   Closed OS:   MS Windows NT 4.0 Original Version:   6.5.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product Description The same OLE object call to the IsError() function in Excel gives different results depending on the deployment form. In machine code the error is : Application terminated / Illegal any data type in expression : void Workaround: Use Pcode

CR:204287

CR Number:   204287 Product Name:   PB Enterprise Product Component:   DW - Runtime Status:   Closed OS:   Microsoft Windows 98 Original Version:   6.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product Description 1)Create an OLE control object on a window of type Microsoft Word document 2)Run application and doubleclick on OLE control - Microsoft Word application is opened. 3)Type text 'line 1' in the document 4)Click on MSWord's File menu, Save option. 5)Type text 'line 2' in the document 6)Click on MSWord's File menu, Save option. 7)Exit Microsoft Word application 8)DoubleClick the control to reactivate the OLE control - the changes 'line 2' are no longer there 9)Close the application and change the DisplayType property of the control to Icon! and perform steps 1 to 8 again. Notice the changes remain when the control is reactivated. OLE Control with the DisplayType of Icon, loses previous updates when activated again. Action: OLE control activates object MSWord97. Type some text into the Word doc, Save in Word (first update). Do this twice more. Exit Word Application. Doubleclick on OLE control to activate the same doc. Notice that only the first update is displayed and the others lost: OS: Win98, NT4 PB6.0 Result Broken PB6.5 Result Broken PB6.5.1 Result Broken PB6.5.1 Build 1067 Result Broken Error: OLE Control with the DisplayType of Icon, retains only first update and loses all others when activated again. PB7.0 Result OK Workaround Description  Possible workaround PB65: If suitable for the ct, choose DisplayType=Contents instead of DisplayType=Icon PB7: is not a problem.

CR:204302

CR Number:   204302 Product Name:   PB Enterprise Product Component:   Edit Mask Status:   Closed OS:   Microsoft Windows 95 Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 13 Apr 2000 Fixed Description *** 7.0.01 Regression*** Edit mask ###-###-#### on CHAR or VCHAR column. Run/Preview datawindow and delete data in column using backspace/delete key will also delete the dashes. Then try to type in some new data and you can only get type the first three char's, it will not allow you to type anymore char's. If you tab off the column, the dashes do 're-appear', the editmask will refresh and then you can type in the rest of the data. This happens in the datawindow painter and runtime.

CR:204323

CR Number:   204323 Product Name:   PB Enterprise Product Component:   DW Edit Mask Status:   Closed OS:   MS Windows NT 4.0 Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11 May 2000 Fixed Description It is not possible to specify, using Powerbuilder 7.0, negative values for the DW edit mask spin control MIN and/or MAX attributes. If you try and do so the entered value will revert to 0 while validating whatever negative value has been entered. Entering negative values for the MIN and/or MAX values of a spin edit mask control (on a Window) works fine. Workaround: Dynamically modify the SpinRange at execution time ie dw_1.object.COLUMNNAME.Editmask.SpinRange="-10~~~~-1" Workaround Description  1. Export the datawindow object, modify the SRD and reimport or 2. Dynamically modify the SpinRange at execution time ie dw_1.object.COLUMNNAME.Editmask.SpinRange="-10~~~~-1"

CR:204390

CR Number:   204390 Product Name:   PB Enterprise Product Component:   GenApp Status:   Open OS:   Microsoft Windows 98 Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description Enhancement request from ct: Ct would like to access the CURRENT value of a variable from the VariableDefinition object. At this time, this feature is not present in the VariableDefinition object. OS:Any PB6.x, 7.x : Feature does not exist For example: The VariableDefinition object has information about: -The variable's name and type -Whether the variable is a scalar or an array and information about the array -The variable's initial value, whether the value overrides an ancestor's value, and whether the variable is a constant -The read and write access levels for the variable -The scope of the variable (global, shared, instance, local, argument), including whether the variable is an argument and how the argument is passed

CR:204404

CR Number:   204404 Product Name:   PB Enterprise Product Component:   DB Informix Status:   Closed OS:   MS Windows NT 4.0 Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 6.5.00 1089 01 Jan 2002 Fixed Description SQL error -1803 Connection does not exist" when using Distributed Powerbuilder and the Informix native driver after the second client connects to the database. Using SetTransPool. The Informix client software must be thread safe. Using ODBC to SQL Anywhere works fine. The connection is using SQLCA and the code is doing an explicit disconnect after retrieval in script. Workaround: Commenting out the "Disconnect using SQLCA" in script gets rid of the error but also does not use the transpool correct as it continues to create connections up to the maximum limit of the transpool. At this point, the user gets an error "Transpool limit exceeded". There is no "reuse" of connections and the connections stay open. 9/17/99 Fixed by Development: Also, in order for the fix to work, you have to set dbparm ThreadSafe=1

CR:204408

CR Number:   204408 Product Name:   PB Enterprise Product Component:   WT - Web DataWindow DTC Status:   Closed OS:   MS Windows NT 4.0 Original Version:   7.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0 GA 5027 06 Apr 2001 Not a Bug Description The HTML DataWindow DTC can not be used successfully anymore once Service Pack 5 is installed. At the end of stepping through the wizard, a GPF occurs, then PowerSite shuts down. However, if you run PowerSite again, you will see that the file was actually created. To workaround to crash, use one of the File wizards to create an HTML page, then edit the page and insert a Web DW, by choosing Insert->ActiveX->Design Time->Sybase HTML DataWindow DTC Workaround Description  Instead of using the HTML DataWindow DTCproject wizard, use one of the File wizards to create an HTML page, then edit the page and insert a Web DW, by choosing Insert->ActiveX->Design Time->Sybase HTML DataWindow DTC

CR:204439

CR Number:   204439 Product Name:   PB Enterprise Product Component:   Menu Painter Status:   Closed OS:   Microsoft Windows 95 Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 1136 16 Jun 2000 Fixed Description Window type: MDI Description: Problem with Toolbar property when selection made in menu painter. OS:Win98,NT4 a) Action: With Menu object: Define a Submenu Item: Assign a bmp file which has a path and filename length longer than 63 chars to property ToolbarItemName. Result: PB 7.x will GPF. Workaround Description  Assign the property value for ToolbarItemName in the PB7 script e.g. window Open event. Result: PB7 will not GPF. e.g. m_staff.m_expenses.toolbaritemname = ls_long_str

CR:204460

CR Number:   204460 Product Name:   PB Enterprise Product Component:   DB OLE DB Status:   Closed OS:   MS Windows NT 4.0 Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0 Beta 2 2048 24 Oct 2000 Fixed Description OLE DB driver does not read extended attributes (catalog tables) when you create a datawindow. With 'Use Extended Attributes' ON in the database painter and 'dbo' as the PBCatalogOwner, using the native MSS driver to Microsoft SQL Server 7.0 the user can both SEE and EDIT the extended attributes and they are included when you create a datawindow. Connecting through OLE DB to Microsoft SQL Server 7.0, you can see and edit the extended attributes (for columns, etc) but when you create a datawindow the painter doesn't use them. Workaround: Use the native MSS driver to create datawindows.

CR:204475

CR Number:   204475 Product Name:   PB Enterprise Product Component:   Library Painter Status:   Closed OS:   MS Windows NT 4.0 Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8004 28 Jan 2000 Fixed Description Using the uploaded test case, search for a string which does exist in the script of a menu object. The string searched for is in a quoted string within the script. The same thing works okay in a window object.

CR:204497

CR Number:   204497 Product Name:   PB Enterprise Product Component:   DW SaveAs Status:   Closed OS:   MS Windows NT 4.0 Original Version:   6.5.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product Description the documented syntax for Saveas() does not work when saving a datawindow of type Graph in WMF format. Empty Graphs are saved in a WMF file or infalid files are created. SaveAs ( { filename, } { graphcontrol, saveastype, colheading } ) two possible workarounds: 1. insert the graph dw into a comosite dw. - then saveas() and saveas('d:\d_gr.wmf',WMF!,FALSE) syntax work fine. 2. use the following script: ret = dw_1.saveas('d_gr',WMF!,FALSE) ret = dw_1.saveas() - then you can save the graph with the saveas dialog as WMF