远程Sybase数据库技术支持,联系手机:13811580958,QQ:289965371!

 

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

如有问题,请联系我!

QQ :289965371 点击这里给我发消息
Email:
不仅仅包括BUG的详细描述信息,还包括首次报告BUG的平台、数据库版本以及BUG修复历史过程;有些BUG还提供了Workaround来临时解决该BUG带来问题。

 

CR:216894
CR Number:   216894
Product Name:   PB Enterprise
Product Component:   Language - Compiler
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
25 Feb 2004 EOL'd version. Not to be Fixed.
Description
Real/Double conversion using Dec() - precision displays differently if cast into a Decimal datatype (rather than a Decimal{n} datatype.

decimal test
real r1,r2
r1=922000
r2=923000
Messagebox("",dec(r1))
Messagebox("",dec(r2))

The first one will have 12 decimal places, the second 13.

Workaround: Use Decimal{n} in PowerScript to specify exact precision.



CR:216897
CR Number:   216897
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   5.0.04
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
When you change a computed field created by manipulating NUMERIC columns (na + nb) and one of the column values in the expression is NULL, the computed field becomes "0" after you change it's expression. (to, say "na")

ex:
If na and nb are numeric columns and compute_1 is made up of 'na+nb' and na and nb are null, the computed field will turn from NULL (blank) to zero when the expression is changed to "na". It should remain NULL since one or both of the columns is null.



CR:216901
CR Number:   216901
Product Name:   PB Enterprise
Product Component:   Migration
Status:   Closed
OS:   Microsoft Windows 98
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 dw export file from PB5.x does not migrate nor import correctly to PB7.x if property HSplitScroll is enabled. Repaint problems happen when the VScrollBar DownArrow is pressed.
Workaround Description
 a)Re-create the DW grid in PB7.x instead of migration OR b)Disable HSplitScroll property in PB5.x then import
into PB7.x OR c) Place SetRedraw function in scrollvertical and scrollhorizontal events.



CR:216906
CR Number:   216906
Product Name:   PB Enterprise
Product Component:   DW Edit Mask
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.2 8028 11 May 2000 Fixed
Description
PB 7.0.2 build 8026 regression from PB 6.5.1.

Datawindow with string/character colum with an editmask. Highlight value in column and press the Delete key. When user tries to reenter data the first character input is ignored and does not appear. All subsequent characters are fine.

As an example if a character column has an editmask on it and the string is 'ABCD'. Highlight the entire string and hit the delete key. Try reentering 'EFGH' and you will only see 'FGH'.



CR:216909
CR Number:   216909
Product Name:   PB Enterprise
Product Component:   DB DirectConnect
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. The TableCriteria/TableOwner setting used with PBDIR to DB2/MVS causes a GPF in PBVM70.DLL when either opening the table list in the database painter or anywhere the 'Select Tables' dialog is presented (as in the datawindow painter, SQL Select datawindow creation).

Appears to work fine in 7.0 builds > 8025



CR:216930
CR Number:   216930
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
Filter expression with "column in (<list>)" causes memory leak. This can become severe with a high number of iterations.



CR:217051
CR Number:   217051
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
25 Feb 2004 EOL'd version. Not to be Fixed.
Description
In runtime a Datawindow of style grid is not refreshed sometimes. If dragging (very fast) another window e.g. Explorer over a grid dw it could happen that a black square appears.

Map the pbm_paint in the window and place following script in the event:
dw_1.setredraw(FALSE)
dw_1.visible = FALSE
dw_1.setredraw(TRUE)
dw_1.visible = TRUE
Workaround Description
 Map the pbm_paint in the window and place following script in the event:
dw_1.setredraw(FALSE)
dw_1.visible = FALSE
dw_1.setredraw(TRUE)
dw_1.visible = TRUE



CR:217054
CR Number:   217054
Product Name:   PB Enterprise
Product Component:   Rich Text
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
Large memory leak printing when using the rich text edit control (native). After 10 iterations of a small rich text file (with embedded graphics) using rtf.print(), it leaks 300k with a simple 130k file. Also leaks 11 handles in NT.

Rich Text Datawindows also leak when printing - about 2MB for 10 pages (with metafile)



CR:217066
CR Number:   217066
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   MS Windows 3.1
Original Version:   6.5.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16 Nov 2000 Presently Not Targeted For Any Future Release Of This Product
Description
The CrossTabDialog() function does not work in 16-bit in PB6.5.

The dialog comes up but the selections does not apply after closing the dialog

--> This problem is not going to be fixed due to 16-bit PB6.5 version is nearing end of life.



CR:217089
CR Number:   217089
Product Name:   PB Enterprise
Product Component:   Language - Compiler
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
25 Feb 2004 Not reproducible with latest version of the product available as of Resolution Date
Description
PowerBuilder Wintel client applications GPF when calling remote functions on Jaguar on Solaris. An example would be if you redeploy a PB Component to Jag 3.5 (to fix a bug - no changes in methods). You would think the client application was OK - ie - any proxies (stubs) are OK since the interface didn't change.

If you don't do a Library Painter/Full Rebuild (regenerate) on ALL the client objects - esp the proxy object - before re-running the client application AFTER RE-DEPLOYING COMPONENTS WITH NO INTERFACE CHANGES TO JAGUAR - you will GPF on the CLIENT or HANG at the first remote function call.

After regenerating the client application, the client will immediately begin working again.



CR:217105
CR Number:   217105
Product Name:   PB Enterprise
Product Component:   Window - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
25 Feb 2004 EOL'd version. Not to be Fixed.
Description
Memory usage goes up when an app is running

in development or runtime (p code and machine code), when isnull

is used with the any datatype.



The test case has a do while loop that runs with 10000 iterations

any test_string

do while myint < long(sle_1.text)

isNull(test_string)

myint ++

loop



Memory usage goes up as follows for a pcode exe:

Memory VM Size

1. 4488 2456

2. 4572 2540

3. 4652 2620

4. 4728 2696
Workaround Description
 Change the datatype from any to string.



CR:217134
CR Number:   217134
Product Name:   PB Enterprise
Product Component:   Jaguar Integration
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
21 Sep 2000 Fixed
Description
GetFullState () hangs for dw with large amount of data (e.g. 2000 rows X 31 columns) when integrated with Jaguar 3.5 on SUN Solaris 2.6. However, its work fine with small amount of data (e.g. 100 rows).

On the other hand, it works perfectly for large amount of data when using Jaguar 3.5 on Win NT accessing the same ASE database on SUN Solaris.
Workaround Description
 No



CR:217135
CR Number:   217135
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Open
OS:   MS Windows NT 4.0
Original Version:   7.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
Datawindow Print Orientation isn't working fine if no printer is defined.
Different PB releases have different behaviours.
If no Printer is defined and you create a composite datawindow it's not possible to change the Orientation. it will always displayed in Portait format or in PB 6.0 build 444 the print preview becomes the size of the frame.
Because in PowerBuilder 7 we have the posibility to define the paper size in the dw, we should be able to put the orientation correctly according to the paper size in the preview of the dw. Then if default paper size is used it will take the system parameter ( but when no printer is defined only portrait will be used or something like this).
More over I notice that when no printer is defined, the paper size is ignored.



CR:217136
CR Number:   217136
Product Name:   PB Enterprise
Product Component:   Generators
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
20 Sep 2000 Fixed
Description
Has a PB nvo with a method of_pass_string (string as) which just does return as.
When a client calls this method passing a string containing french or german or hebrew characters (above ascii code 127), it receives garbage.



CR:217147
CR Number:   217147
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
This problem only appears to be an issue with Times New Roman font.
In the DW painter if you change the font from Arial to Times New Roman via the toolbar font.family is set to 2, if you try to change the font from Arial to Times New Roman via the column properties, then font.family is set to 1. On some printers the output will be incorrect, a different font will be used instead of Times New Roman.



CR:217152
CR Number:   217152
Product Name:   PB Enterprise
Product Component:   System Runtime Functions
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15 Jun 2004 EOL'd version. Not to be Fixed.
Description
Using PopMenu on a menu item which is not visible will pop-up this menu.

Easy WA:
Just code: (Example)
IF m_genapp_sheet.m_edit.Visible THEN
m_genapp_sheet.m_edit.PopMenu(1024,384)
END IF
Workaround Description
 Just code:
IF m_genapp_sheet.m_edit.Visible THEN
m_genapp_sheet.m_edit.PopMenu(1024,384)
END IF



CR:217155
CR Number:   217155
Product Name:   PB Enterprise
Product Component:   DW Painter
Status:   Open
OS:   MS Windows NT 4.0
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
The client would like to have the ability to set the background color of columns as a default style setting.
Workaround Description
 From the font tab of the DW column you can set the background color, but this will be specific to each DataWindow.



CR:217160
CR Number:   217160
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)
7.0.2 8011 09 Jun 2000 Fixed
Description
7.0 Regression. If you create a crosstab and don't own the table, and you use just ONE table for your SELECT statement, the columns the crosstab wizard creates are fully qualified (employee.emp_id) and this causes the computed fields for the crosstab to be corrupt and show no data (esp Grand Total computed fields in the footer band that show blank)

This has been reproduced in ODBC and SYC which rules out some ODBC interaction with owner in PBODB70.ini.

CR207744 was a GPF building a crosstab. Fixed in 7.0.2 8011 or so.

This fix requires at least PBWIZ70.DLL and PBDWE70.DLL.



CR:217162
CR Number:   217162
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)
16 Mar 2004 EOL'd version. Not to be Fixed.
Description
OLEDB missing profile dialog UI for FormatArgsAsExp. Without this, large integers in retrieval arguments will be converted to exponential notation. The property would be a checkbox on the Syntax tab as "Format Arguments in Scientific Notation"



CR:217164
CR Number:   217164
Product Name:   PB Enterprise
Product Component:   DB Oracle
Status:   Closed
OS:   HP-UX 10.20
Original Version:   6.5.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
On hpux, trying to connect using the or8 driver with
oracle client 8.0.4 will give the following error:

DBMS or8 oracle 8.0 is not support in your current installation.

Works ok when using oracle 8.0.3 client. Works ok using oracle 7.3 and the o73
driver.



CR:217166
CR Number:   217166
Product Name:   PB Enterprise
Product Component:   DW HTML
Status:   Open
OS:   MS Windows NT 4.0
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
PowerBuilder SaveAs() should include the new HTML Datawindow Generator for datawindows and datastores. The new generator created has more features than the currently supported HTMLTable! output and this would be a great tool for both PowerBuilder (and even InfoMaker) users.



CR:217180
CR Number:   217180
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)
14 Jul 2000 Fixed
Description
7.0 Regression. Bad behavior. Regenerating the last object in the library painter (where there is more than one "page" of objects, causes the list to scroll back to page 1 when finished. In 6.5, it stayed with the object you regenerated.



CR:217232
CR Number:   217232
Product Name:   PB Enterprise
Product Component:   UO Painter
Status:   Open
OS:   MS Windows NT 4.0
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
In 7.0, the property sheet for an inherited object will contain the instance variables as part of the "General" tabpage for the properties sheet shown at the RIGHTMOST pane (default layout). We do this for default values like "Enabled", etc, why do we lower case all instance variables that show up in descendant areas.

Also, in the script painter, right -mouse/paste special/instance also shows all instance variables defined in the ancestor object or in the CURRENT descendant object in lower case.



CR:217234
CR Number:   217234
Product Name:   PB Enterprise
Product Component:   Library Painter
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
14 Jul 2000 Fixed
Description
A full rebuild will show inconsistent results on
several attempts. In the library painter when you run the full rebuild,
it may show no errors. Run a full rebuild again and app will show
errors.



CR:217244
CR Number:   217244
Product Name:   PB Enterprise
Product Component:   Window - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.5.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
27 Feb 2001 Not a Bug
Description
OpenWithParm will return control back to the script that called the window before the window is closed.

Developers Comments:
This is not a bug. This doesn't work because of the close in ue_retrieve of w_cancel. The doc indicates that the post messages are written to a different queue from the window's message queue, therefore you don't have control over either message. What is happening is that the return of w_cancel is not occuring until after w_info has been opened. If you had script following the OpenwithParm of w_cancel, you would see that this isn't occuring until after w_info is closed and there is nothing in the message object because the OpenWithParm for w_info cleared the message object.



CR:217270
CR Number:   217270
Product Name:   PB Enterprise
Product Component:   UO Painter
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15 Jun 2004 EOL'd version. Not to be Fixed.
Description
Running nvo in debug causes constructor to fire later in painter when saving nvo.



CR:217276
CR Number:   217276
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.5.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.5.2 05 Sep 2000 Fixed
Description
6.5.1 Regression. Rowfocuschanged not firing on NUP datawindow when the user clicks from NUP row to NUP row.



CR:217286
CR Number:   217286
Product Name:   PB Enterprise
Product Component:   DB ODBC
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.2 31 Oct 2002 Fixed
Description
DB2/MVS Outer Joins not allowed in SQL query

This problem happens for PB SQL painter regarding ODBC connection to DB2 on MVS. The 2 join selections unsupported are :-
= table1.id = table2.id and rows from table1 that have no table2
= table1.id = table2.id and rows from table2 that have no table1

PowerBuilder ODBC to DB2 UDB on NT is OK.
Workaround Description
 Make an export/import of each DW and to add the table name before each column name.



CR:217325
CR Number:   217325
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.2 28 Aug 2000 Fixed
Description
Editing Global Variables while in function object substitutes variables for script. This seems to only happen on GLOBAL FUNCTION objects, not user objects. (Keywords: disappear, gone, missing, swap, corrupt, deletes)

This might be because the script painter is slightly different for global functions. They only have

f_test
(Declare)

in the listbox and (Declare) only has Global Variables and Global External Functions. A user object would have:
uo_test
(Functions)
(Declare)
and (Declare) would have 5 different items, (Global, Instance,Shared variables, Global, Local External Functions)

7.0 GA build 5031 and 7.0.1 build 6012 have this problem. 7.0.2 (build 8003) or higher seems to work fine.



CR:217346
CR Number:   217346
Product Name:   PB Enterprise
Product Component:   SQL Painter
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
03 May 2000 Fixed
Description
7.0.2 EBF Regression. Right Mouse menu to Paste Retrieval Arguments in the datawindow painter "SQL" view has disappeared in 7.0.2 Build 8026. Instead you get the Cut/Copy/Paste/Select All menu.

The WHERE Tab has the columns "Column, Operator, Value". You used to be able to right mouse on the "Value" column in an EDITABLE field and get the popup menu containing:

Columns...
Functions...
Arguments...
Value...
Select...
Clear

In 7.0.2 8033, the menu does appear but only when on the 'Header' part of the tab (when placed over the header label "Value" in the value column.).



CR:217353
CR Number:   217353
Product Name:   PB Enterprise
Product Component:   Structure Painter
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
14 Jul 2000 Fixed
Description
Printing a structure from the painter, pops the save dialog window and does not print the structure.



CR:217356
CR Number:   217356
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.5.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.5.1 1231 01 Feb 2001 Fixed
Description
6.5.1 Regression. Group band background color outside band in preview mode (not print preview). Grid datawindow shows this best where the color is above the grid line by about 5%-10%.



CR:217466
CR Number:   217466
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   5.0.04
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
Typing Control-End on an empty datawindow in print preview mode GPFs in in PBDWE050.DLL, PBDWE60.DLL, etc depending on version of PowerBuilder.

Appears fine in versions 6.5.1 620 and 7.0.1 6012.

Note: This could also happen in InfoMaker in the report painter or in a runtime executable since it's always in print preview mode.



CR:217471
CR Number:   217471
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11 May 2000 Fixed
Description
If you evaluate dwo.name in the dw clicked event when the pointer is over a text field of a dw command button, it evalueates to "datawindow" instead of the name of the text field or button. When you click on a dw command button, the buttonclicking and button clicked events do not fire.
Workaround Description
 <none>



CR:217472
CR Number:   217472
Product Name:   PB Enterprise
Product Component:   DB Profile
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   8.0 Beta 1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0 Beta 3 3032 09 Jan 2001 Fixed
Description
Enhancement. Make 'Format Arguments in Scientific Notation' "NO" the default in ODBC and OLEDB connections and any other connections when you either build a new profile or when running in runtime.

The default behavior causes the where clause to produce a scientific notation for a numeric (integer or long) retrieval argument.

Ex: where id = 1.3e1

which can often cause table scans if the numeric retrieval argument is large. There is no way for the average developer (or InfoMaker end user) to know the effect of this DBPARM default value on their queries.



CR:217486
CR Number:   217486
Product Name:   PB Enterprise
Product Component:   DW Painter
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.3
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16 May 2000 Fixed
Description
7.0 Regression: In dw painter, can't change name of graph or OLE object for a graph or OLE presentation style datawindow.



CR:217494
CR Number:   217494
Product Name:   PB Enterprise
Product Component:   Inheritance
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.2 8042 25 Dec 2000 Fixed
Description
UO Painter. GPF replacing an object whose ancestor has been deleted.
Problem with inherited objects that are user objects or menus. Windows do not appear to have the problem.
Example of problem with user objects is :

I have three objects A, B, C. C is inherited from B and B is inherited from
A. I delete B and create a new object D, inherited directly from A.
A this point, I have object A and object an object C that is no longer
valid - the object it is inherited from, B, no longer exists.
If I try to save the new object D with the same name as object C,
overwriting C, PB GPFs.
In previous versions the new object would be saved without a problem and would overwrite the object with the missing ancestor.



CR:217550
CR Number:   217550
Product Name:   PB Enterprise
Product Component:   DW Expression
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
03 Mar 2004 EOL'd version. Not to be Fixed.
Description
Some values are computed differently when using the Round(0 function in Powerscript and in the Datawindow.
Powerscript value after rounding = 312.8300 However, in the DataWindow, the value is 312.82.

Workaround:
Use Round(Truncate((( sj_b_npric * ssj_sh_qty) + 0.000001),4),2).
Workaround Description
 Use Round(Truncate((( sj_b_npric * ssj_sh_qty) + 0.000001),4),2).
However, Customer would like an explanation for the discrepancy.



CR:217555
CR Number:   217555
Product Name:   PB Enterprise
Product Component:   Script Painter
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   5.0.04
Fixed Version Build Resolution Date Closure Code (If Appropriate)
28 Nov 2000 Not a Bug
Description
Save As... from the menu for a new global function to a second PBL causes the function definition (arguments + return value) and script to disappear. You must have 2 PBLs and do a Save As.. to the second PBL when you FIRST save the function

Happens in NT and Win98 (suspect Win95 too). Also, PowerBuilder 5.0 and 6.x have this behavior but 7.0 does not.



CR:217572
CR Number:   217572
Product Name:   PB Enterprise
Product Component:   Inheritance
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.2 8042 12 Dec 2000 Fixed
Description
When attempting to inherit from a descendent with a missing ancestor as soon as the ancestor is chosen you will receive a PB 70.exe Application Error. The instruction at "0x1131bc97" referenced memory at "0x01820760". the memory cannot be read.

In PB 6.5.1 if you try to choose a descendant ot inherit from that has a missing ancestor you will get the standard Inherit of 'xxxx; failed Possible causes 1- Object does not exist"

Let's say you have a base menu 'm_base' and create a descendant called 'm_level2' and then inherit 'm_level3' from 'm_level2'. Now delete 'm_level2' and try to open 'm_level3'. You will get the standard: Open of menu 'm_level3' failed. Possible causes: 1 - Object does not exist, etc. You will also get this error message if you try to inherit from this menu in PB 6.5.1 but in all versions of PB 7.0 tested when you try to inherit from this menu with a missign ancestor you will crash.



CR:217646
CR Number:   217646
Product Name:   PB Enterprise
Product Component:   Library Painter
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   5.0.04
Fixed Version Build Resolution Date Closure Code (If Appropriate)
14 Sep 2000 Fixed
Description
If the date format used for ShortDate in the control panel Regional Settings includes a SPACE, the library painter, Modification Date, Compilation Date and comments get corrupted.

5.0.04 - 04 25 2000 07:05:21 (1543) 2000 07:05:21
6.5 - 04 25 04 25 2000 07:05:21 (1543) 2000 07:05:21
7.0.2 - 04 25 04 25 (1543) 2000 07:05:21



CR:217649
CR Number:   217649
Product Name:   PB Enterprise
Product Component:   Jaguar Integration
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
25 Feb 2004 EOL'd version. Not to be Fixed.
Description
A memory leak occurs when populating a string array in a PowerBuilder Jaguar component that has instance pooling disabled.



CR:217669
CR Number:   217669
Product Name:   PB Enterprise
Product Component:   DB ODBC
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
SQLSTATE 07006 (Restricted data type attribute violation) using an ODBC driver against MS SQL Server 6.5 or 7.0. This is caused if the statement contains a backend Convert() call in the WHERE clause that contains a retrieval argument.

Ex:
convert(varbinary(1),:ts_1) +
convert(varbinary(1),:ts_2) +
convert(varbinary(1),:ts_3) +
convert(varbinary(1),:ts_4)

Workaround is to use Disablebind=1 in the DBPARM (Profile painter, transaction tab)



CR:217771
CR Number:   217771
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.2 01 Nov 2000 Fixed
Description
dw.reset GPFs when dw is shared with multiple reports in composite dw.



CR:217776
CR Number:   217776
Product Name:   PB Enterprise
Product Component:   DW Edit Mask
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.2 06 Sep 2000 Fixed
Description
When there is an editmask of ###.## on a numeric column and the data value is highlighted and then the Delete key is clicked. At this point the cursor will be to the left of the decimal point. If in PB 6.5.1 the Delete key is again clicked you cannot get to the decimal portion of the number unless you click in the decimal portion. In PB 7.0 GA through build 8030 when the Delete keyis hit a second time you will be to the right of the decimal point and the column will be displayed as .0. The same thing will happen in PB 8.0. In Pb 7 if you then realize that you need to be to the left of the decimal point and click there or hit the 'Home' key and enter 1-2-3 the value will be displayed as 2-3-1. In PB 8.0 the value will be displayed correctly as 123.

If the editmask is ###.00 the behavior is the same in both PB 7.0 and 8.0 in that you can get past the decimal point ( which may be an intended change in behavior in both PB 7 and 8 but I could not find it documented), but the data entered into the column is correct.



CR:217810
CR Number:   217810
Product Name:   PB Enterprise
Product Component:   DW Printing
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15 Jun 2004 EOL'd version. Not to be Fixed.
Description
Tray Selection (Paper.Source) not working for POSTSCRIPT printers.
Workaround:
use non Postscript drivers if possible or setup the tray in the printer setup.
Workaround Description
 use non Postscript drivers if possible or use the tray in the printer setup



CR:217824
CR Number:   217824
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)
26 Dec 2000 Not a Bug
Description
7.0 Regression. For a group style datawindow, the group band property "Reset Page Number on group break" is now called "Reset page count" by mistake.

Development: We made a conscious decision in 7.0 to expose the datawindow syntax as much as possible (consider it a way for the user to learn syntax ) .. and .. ResetPageCount is the syntax (property) for what was once "Reset Page Number on Group Break".



CR:217866
CR Number:   217866
Product Name:   PB Enterprise
Product Component:   DW Edit Mask
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
When an edit mask is used on a real column, there can be a rounding error for certain numbers.
A numeric value like 9.4 stored in a coltype real column can get truncated to the value 9.3 in the
editmask instead of rounded to 9.4.

Work-around is to export the datawindow and change the column type from real to number.



CR:217872
CR Number:   217872
Product Name:   PB Enterprise
Product Component:   System Runtime Functions
Status:   Closed
OS:   Solaris 2.6
Original Version:   6.5.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
02 Oct 2000 Not a Bug
Description
PB crashes with a segmentation fault after
calling a external function.

External function is user defined. Generated in c++ and calling
the java jvm. Using jdk/jre 1.2.1. PB crashes in development and runtime when
calling.



CR:217874
CR Number:   217874
Product Name:   PB Enterprise
Product Component:   Language - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.2 8031 07 Dec 2000 Fixed
Description
When opening the w_examplemain window in the PFC examples the following error occors: PowerBuilder Application Exection Error (R0023) Error: Cannot assign object of type mdi_1 to variable of type pfc_w_frame'mdi_1 at line 6 in create event of object pfc_w_frame. To fix this: Export w_frame from exmmain.pbl and remove these two lines:
"type mdi_1 from mdiclient within w_frame
end type"
and then import w_frame back in.
Workaround Description
 Export w_frame from exmmain.pbl and remove these two lines:

type mdi_1 from mdiclient within w_frame
end type

and then import w_frame back in.



CR:217885
CR Number:   217885
Product Name:   PB Enterprise
Product Component:   PB GUI
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   7.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
25 Feb 2004 EOL'd version. Not to be Fixed.
Description
When a com/mts component is generated on a win95
machine and you then open the project and select objects from the painter
bar, the checkboxes don't appear to work. (see 41065974.zip for screen
print shot)

Problem only happens on win95. Ran a test on win95a,win95b and problem
happens on both. Also installed dcom95 and checked the security and problem
still happens. It appears to be environmental because on one win95 machine,
problem doesn't happen. Both machines are running dcom95 and pb 7.0.2
8026. Also ran msinfo32 and both machines are using the same system dll's.

Need to know what conditions pb is checking for a com/mts project/select objects.



CR:217914
CR Number:   217914
Product Name:   PB Enterprise
Product Component:   DW Display
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
14 Jul 2000 Fixed
Description
PB 7.X regression. When adding a computed field to a datawindow that displays wingding fonts the default font is used. If a PB 6.5.1 datawindow is migrated to PB 7.0.2 the correct wingding font is displayed.



CR:218041
CR Number:   218041
Product Name:   PB Enterprise
Product Component:   DB MS SQLServer
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.5.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
In DB Painter, open a table having a primary-foreign key relationship with another table.
Rightmousebuttonclick on primary key - open dependent tables - fails
In PB 6.5.1 + built 1180 you'll get a GPF in pb60.exe
The instruction at 0x109f7e01 referenced memory at 0x00000000.
Workaround Description
 Use PBmss60.dll from original built if possible.



CR:218042
CR Number:   218042
Product Name:   PB Enterprise
Product Component:   Jaguar Integration
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
25 Feb 2004 Fixed
Description
Concurrent clients hang PB7 component in EAServer3.5 (Solaris) at GetFullState()
Workaround Description
 no



CR:218045
CR Number:   218045
Product Name:   PB Enterprise
Product Component:   Jaguar Integration
Status:   Closed
OS:   Solaris 2.6
Original Version:   7.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.2 06 Apr 2001 Fixed
Description
A pb component fails in Jaguar on solaris when a dw
used in that component has a updatable datawindow. The component
creates a datastore and assigns the dataobject.

The dw is using a sp and is set to updateable from rows/stored
procedure update. When you call that component from a pb client,
the component fails on the settransobject only on jaguar on solaris.
Works ok on nt. If the sp update is reset from rows/stored procedure update
so that it isn't updatable, than the data is retrieved back to the client. No problems.

Happens for an ASE stored procedure and Oracle. Doesn't appear to be
db specific.



CR:218057
CR Number:   218057
Product Name:   PB Enterprise
Product Component:   DW Graph
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   7.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.2 8033 17 May 2000 Fixed
Description
7.0.2 ebf Regression. Graph datawindow with query datasource is not displaying graph after retrieving.

Works up through 7.0.2 8003.



CR:218111
CR Number:   218111
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.x Catalina
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0 Beta 3 30 Jun 2004 EOL'd version. Not to be Fixed.
Description
Nested reports within composite datawindows are renamed after migration to PB 7.

In Powerbuilder 7, empty names for nested reports within a composite DW are not allowed anymore.
Then, during migration, any nested report is renamed with the syntax dw_{x} (based on the Design/Options/Prefixes setting for a nested report) if it was created without a name in a prior version.

If you happen to use a name similar to the dw_{x}, you could get into trouble.

For example, if a composite datawindow had 4 nested reports (in PB 6.x) named :
dw_1 / <empty name> / my_nested_1 / dw_2

After the migration (from PB 5 to 7 or PB 6 to 7), the names are automatically changed to :
dw_1 / dw_2 / my_nested_1 / dw_3

So any script reference to the nested report dw_2 now refers the second nested report while it refered the fourth one before the migration. (You'll get strange behavior with GetChild(), perhaps with dot notation, etc).

Workaround:
The collision is caused by the naming conflict. The user might go in ahead of time and change the default 'datawindow' naming prefix from 'dw_' to 'dwn_' before migration.



CR:218115
CR Number:   218115
Product Name:   PB Enterprise
Product Component:   UO Painter
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
03 Oct 2000 Fixed
Description
"A prototype is needed for this script" error in function painter when adding a parameter and saving object.
When adding a new argument to an object function you get the error above IF:
- The object has more than one function
- The function does not have a return value.
- You use the mouse to choose the datatype of the new argument from the DDLB.



CR:218145
CR Number:   218145
Product Name:   PB Enterprise
Product Component:   Debugger
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
27 Nov 2000 Fixed
Description
Debug crashes when stepping into Create of object with deep inheritance.
Verified fixed in 7.0.2 build 8046 (EBF C3)



CR:218165
CR Number:   218165
Product Name:   PB Enterprise
Product Component:   Edit Mask
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.5.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
06 Jul 2000 Fixed
Description
Edit masks ending in #.00 allow more than 2 decimal digits to be entered.
Verified fixed in 6.5 build 1199.



CR:218188
CR Number:   218188
Product Name:   PB Enterprise
Product Component:   UO Painter
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11 Oct 2000 Fixed
Description
If you create a uo with a simple function and save then the object PB causes a gpf.
The object is saved but PB crashed.



CR:218192
CR Number:   218192
Product Name:   PB Enterprise
Product Component:   DW Display
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.x Catalina
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.2 8046_C3 18 Aug 2000 Fixed
Description
Depending on the DW Control size (height property) and on the detail band size (height property) of the datawondow object, the last row of the DW control is hidden.
Workaround Description
 1) Modify the DW control height. In my repro, change it from 992 to 994 solved the problem.
2) Check the "AutoSize height" property of the DW object
3) Modify the size of the detail band. In my repro, change it from 72 to 74 solved the problem



CR:218193
CR Number:   218193
Product Name:   PB Enterprise
Product Component:   DB ODBC
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
27 Oct 2000 Third Party Problem
Description
The Intersolv ODBC drivers supplied with PB are version 3.11.
The latest version on the Merant (Intersolv) site is 3.6
We can download an evaluation copy of these drivers from the web or we can buy them but can we get official upgrades of these drivers licensed for PB?



CR:218217
CR Number:   218217
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.5.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.2 9002 04 Aug 2000 Duplicate
Description
6.5 EBF Regression. Rowfocuschanged not firing after Reset() on a datawindow that contains rows.
(somewhere between March 31, 2000 and April 7th, 2000 builds)



CR:218219
CR Number:   218219
Product Name:   PB Enterprise
Product Component:   Window - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12 Jul 2000 Fixed
Description
7.0 Regression: A response window with SetFocus(this) in the open event GPFs.



CR:218224
CR Number:   218224
Product Name:   PB Enterprise
Product Component:   Language - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.x Catalina
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.5.1 1203 31 Aug 2000 Fixed
Description
Using dot notation to assign a null value to a CHAR variable will crash a PB app if compiled with machine code
Datawindow can be in a datastore or datawindow control. Insert a row in dw but do not add any data...

With 7.0 build 8026 the crash is.
"Instruction at 0x1133d5d4 ref'd memory at 0x00000000...could not be READ."

char charvar
charvar = lds_tmp.Object.a[1] // Crashes
Workaround Description
 Workaround 1 - check if the field is Null with IsNull first
Workaround 2 - use a string var instead of a char var



CR:218265
CR Number:   218265
Product Name:   PB Enterprise
Product Component:   Language - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.5.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
An array of powerobjects is treating nvo elements as if they were structures by copying them on assignment into the powerobject array.
Workaround Description
 After using the powerobject array for structures, initialize it back to a vanilla powerobject array by assigning to it an empty powerobject array.



CR:218272
CR Number:   218272
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   Microsoft Windows 98
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
If an expression is defined for the Graph Value axis using the standard functions :
SUM() or COUNT()
and
Series sort: Unsorted
Category sort: Unsorted,
then in preview the datawindow will force the category to display columns in an ascending character order.
Graph style(s) e.g. Column, Line, Area, Bar, 3D Area, 3D Bar, 3D Column and other
linear styles are affected...

Only PB6.5.1 does not exhibit this problem. From this analysis, I believe PB6.5.1 produces the correct result and the other builds have regressed with respect to the functions SUM() and COUNT() ;



CR:218285
CR Number:   218285
Product Name:   PB Enterprise
Product Component:   DB Profile
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.00 EBF1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0 Beta 2 15 Nov 2000 Fixed
Description
The PowerBuilder IDE crashes in PBVM70.DLL when the database profile has no database specified and you're using PBDIR, PBMSS or PBSYC drivers. The "Test Connection" button on the database profile, "Preview page" when there is no 'database' specified on the "Connection" tabpage in the Profile Painter can cause this.

PowerBuilder goes down faster than the NASDAQ on a bad day.. (SYC, MSS) are affected. All other drivers seem to be OK.

There are several other ways to get this GPF, all related to the profile NOT having a database specified. In these cases, if the "Change Database" dialog comes up and you choose to Cancel out of the dialog without selecting a database, PowerBuilder will GPF. Here are some scenarios (anywhere there is a connection tried):
1. Last connection is one without a database specified in the database profile. Go into PB and open a datawindow but cancel out of the "Change Database" dialog. You will soon GPF (DW Painter)
2. Script painter with embedded SQL. When you save script and are not connected to a database, the IDE will attempt to connect - "Change Database" dialog comes up - cancel out - GPF.
3. Compiling a script manually (Control-L) and cancelling out of the dialog "Change Database".
4. Opening the database painter (same scenario)
5. Creating a new datawindow.
6. Data Pipeline



CR:218293
CR Number:   218293
Product Name:   PB Enterprise
Product Component:   DW Display
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.2 9000 14 Jul 2000 Fixed
Description
Pagedown key positions vertical scroll thumbnail all the way down before it should.
Verified fixed in 7.0.2 build 8046 (EBF C3)



CR:218308
CR Number:   218308
Product Name:   PB Enterprise
Product Component:   Jaguar Integration
Status:   Closed
OS:   Solaris 2.6
Original Version:   7.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
22 May 2000 Not reproducible with latest version of the product available as of Resolution Date
7.0.2 24 May 2000 Fixed
Description
datawindow (HTMLDW) or datastore retrieve return -1 using winfree_interim.tar
Workaround Description
 No Workaround



CR:218315
CR Number:   218315
Product Name:   PB Enterprise
Product Component:   DW Printing
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
25 Feb 2004 EOL'd version. Not to be Fixed.
Description
In a crosstab dw some columns are printed to to wide if using Units="1/1000 Centimeter"

Workaround:
use PowerBuilder Units
Workaround Description
 don't use Units="1/1000 Centimeter"



CR:218316
CR Number:   218316
Product Name:   PB Enterprise
Product Component:   DB ODBC
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 09 May 2001 Fixed
Description
Need support for the retrieval of Procedure text for Oracle ODBC drivers in several areas of the product where PowerBuilder can query this (Script painter, datawindow painter, etc). You'll always see "The database does not currently support retrieval of procedure text."

The actual SQL in the PBODB70.ini that the native driver uses is below (where &objectname is something like 'PROC1' and &ObjectOwner would usually be 'SYS'

[Oracle 7] or [Oracle 8] section of PBODB70.ini
PBSelectProcSyntax='SELECT TEXT FROM SYS.ALL_SOURCE WHERE NAME =

''&ObjectName'' and OWNER = ''&ObjectOwner'' ORDER BY

SYS.ALL_SOURCE.LINE'

When placed in the PBODB70.ini, it doesn't seem to work.



CR:218335
CR Number:   218335
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   Microsoft Windows 98
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.3 29 Sep 2002 Fixed
8.0.3 25 Feb 2004 Fixed
Description
This is a possible regression or intended change in behaviour from PB6.x ; The change in behaviour hinders fast deployment and upgrades for applications.

This problem occurs for "user" object functions. When a library pbl is incrementally
rebuilt as machine or pcode, the minor changes in the source code of
"user" object functions causes an incorrect runtime display ;

I tested this with small changes to function scripts e.g. comment lines, code lines etc. and
NOT argument interference like datatype(s) which are factors necessitating a full rebuild'.

I verified that "window" and "menu" object functions are not affected by this behaviour.

Analysis:-
====================
a)Why has PB made differences in the export order syntax ?

b)Can this influence be removed so as to revert to PB6 behaviour ?
If "No" then PB documentation needs to be changed from "Building individual dynamic library"
to "Necessary for full application recompile".
See PB7 'Application Techniques' Manual.
Page 724: Building individual dynamic libraries.

There are 4 workarounds which will help to deploy "individual" pbds.
Workaround Description
 There are 4 workarounds - see resolution section and refer to case 20234730 for verification tests 4,5,6 ;



CR:218342
CR Number:   218342
Product Name:   PB Enterprise
Product Component:   Edit Mask
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.2 16 Aug 2000 Fixed
Description
Typing backspace on selected data in an editmask deletes the selected data but also inserts a character represented by a square. Verified fixed in 7.0.2 build 8046 (EBF C3)



CR:218364
CR Number:   218364
Product Name:   PB Enterprise
Product Component:   DW Painter
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
25 Feb 2004 EOL'd version. Not to be Fixed.
Description
If a bitmap on a Rich Text Datawindow is changed to anything but the original size, then it is shrunk every time the dw is opened.
Workaround Description
 Use a datawindow other than of RichText type.



CR:218366
CR Number:   218366
Product Name:   PB Enterprise
Product Component:   PB GUI
Status:   Open
OS:   MS Windows NT 4.0
Original Version:   7.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
Enhancement:
In PB 5 when they went to powerbar => rightclick=> select show text =>
You could still see the horizontal separtion lines between the icons. In PB 6.5 and 7.02
they no longer see it.



CR:218378
CR Number:   218378
Product Name:   PB Enterprise
Product Component:   Language - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.2 8042 29 Aug 2000 Fixed
Description
PowerBuilder 7.x :
In the EndLabelEdit event of a treeView control, the RETURN 1 does not prevent the new text from becoming the item's label.



CR:218386
CR Number:   218386
Product Name:   PB Enterprise
Product Component:   Installation
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12 Jun 2000 Presently Not Targeted For Any Future Release Of This Product
Description
7.0.2 Consolidated maintenance upgrade CD (contains all upgrades, InfoMaker, Desktop, Professional, Enterprise) doesn't upgrade PB Desktop 7.0 to 7.0.2. When running setup, you receive the error:

"You do not have the required version of 7.0 or 7.0.1 Enterprise installed on your machine. Please install those products and then run PowerBuilder 7 maintenance setup again."

Resolution:
The artwork on the CDs is wrong. PB Professional and Desktop customers and InfoMaker customers can download the "PowerBuilder 7.0.2 EBF#2" from "MySybase". These customers must already be using PB 7.0x in order to apply this EBF (PB 6.x customers need to upgrade to version 7).



CR:218438
CR Number:   218438
Product Name:   PB Enterprise
Product Component:   DB Oracle
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.5.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Fixed
Description
"Select rowid from table" leads to display a column having 5 characters length instead of 18.
Doing the same with sqlplus leads to show a 18 characters column size.



CR:218442
CR Number:   218442
Product Name:   PB Enterprise
Product Component:   DW Wizards
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.x Catalina
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16 Oct 2000 Fixed
Description
The stored procedure list brought back from the datawindow wizard (any datawindow type) takes 2-3 times longer than it did in 6.5 - more noticeable when there are a lot of procedures.

Seems to be a similar problem to the composite wizard slowdown CR214970. It appears to hang.



CR:218455
CR Number:   218455
Product Name:   PB Enterprise
Product Component:   OLE - Active X - OCX
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15 Jun 2004 EOL'd version. Not to be Fixed.
Description
Using a VC++ MFC window with PB window ActiveX (V6 and V7) leads to debug assertion failed message
when closing the VC++ MFC window



CR:218480
CR Number:   218480
Product Name:   PB Enterprise
Product Component:   DW Painter
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
19 May 2000 Duplicate
Description
In the datawindow painter, if you enter an expression for the Y2 property of a line, the expression gets saved as the expression for the X1 property.
Workaround Description
 None.



CR:218608
CR Number:   218608
Product Name:   PB Enterprise
Product Component:   DB SQLAnywhere
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.x Catalina
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.2 9026 15 Nov 2000 Fixed
Description
Database : Adaptive Server Anywhere
DW based on a JOIN sql statement (JOIN t2 ON t2.col1 = t1.col1) cannot be modified in PB 6 or 7, but it worked fine in PB 5
The error message is : "Database Error."
Workaround Description
 Use the following syntax instead :
SELECT "department"."dept_name" ,
"employee"."emp_id" ,
"employee"."emp_lname"
FROM "department" ,
"employee"
WHERE ( "department"."dept_id" = "employee"."dept_id" )



CR:218620
CR Number:   218620
Product Name:   PB Enterprise
Product Component:   Documentation
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.3
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0 Beta 3 02 Mar 2004 Fixed
Description
Starting with PB7, users cannot redeploy only "some" pbds in an application. Prior to PB7, this may have been possible - but should always have been cautioned. In PB7, the object manager will change the order of object functions whenever the function is editted (for any reason). This affects the v-tables.



CR:218624
CR Number:   218624
Product Name:   PB Enterprise
Product Component:   Jaguar Integration
Status:   Closed
OS:   Solaris 2.6
Original Version:   7.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15 Feb 2001 Not a Bug
Description
Using powerdynamo with netscape 3.61 on solaris
and the html dw on solaris will result in the following error in a web browser:
unable to initialize the vm (check that the path and classpath environmental
variables are set correctly)

When the classpath and ld_library_path point to jdk 1.22 the error occurs.
If the classpath and ld_library_path point to jdk 1.1 then no error.
Workaround Description
 Point to jdk 1.1 instead of 1.2 in the start file of netscape.



CR:218640
CR Number:   218640
Product Name:   PB Enterprise
Product Component:   DW HTML
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
25 Feb 2004 EOL'd version. Not to be Fixed.
Description
The HTML Generator changed from 7.0.1 to 7.0.2 to enhance the rendering of tabular data more accurately and consistently in IE 5.0 and Netscape 4.x. The table width in 7.0.2 is now fully defined in the form header and will include fields that contain only spaces (4 spaces) as table elements. In PB 6.5 and up through 7.0.1, you could add these space elements and they would not get their own HTML table entries.

In 7.0.2, the output of some of these migrated datawindows are displaying the wrong width (too wide) causing bad rendering of tabular data in Internet Explorer vs Netscape.

(Generally, the behavior causes data that fit in the page width to now widen beyond the page)

Discussion: With the recent fixes to the HTML generator to help Netscape positioning, it's possible old workarounds useful in PowerBuilder 6.5 using "SaveAs(HTMLTable!)" don't work. One trick was the addition of fields containing just spaces to help 'space out' tabular data. These are so-called placeholder fields helped to better position and size the real columns but in 6.5 and 7.0.1 they did not get rendered as actual HTML table elements. In 7.0.2, these placeholder columns now become table elements and cause the HTML to "Space out" the data causing the output to look wrong. Users using this method should review their tabular datawindows and take out the placeholder columns.

Here is an example:

[column] [ placeholder ] [ column] [placeholder] [column]

The 'placeholder' fields would just contain 5 or 10 spaces. In 7.0.2, these become table elements so instead of having 3 columns of tabular data, you have 5 columns of data.



CR:218662
CR Number:   218662
Product Name:   PB Enterprise
Product Component:   DW Edit Mask
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.5.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
dw column of datatype NUMBER or REAL with DISPLAY FORMAT e.g. 0.0000. Rounding problem happend
e.g. 1.58465 become 1.5846 expect 1.5847
3.23465 become 3.2346 expect 3.2347

Workaround :
Problem can be workaround by export dw object and change relatedt NUMBER or REAL datatype to DECIMAL(5) and reimport into the dw object.
Workaround Description
 Problem can be workaround by export dw object and change relatedt NUMBER or REAL datatype to DECIMAL(5) and reimport by to dw object.



CR:218676
CR Number:   218676
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)
15 Nov 2000 Fixed
Description
6.5 EBF Regression. Sort() invoked on primary datawindow of a sharedata pair is not displayed on secondary datawindow.

This was broken around 6.5 1189 and 7.0.2 8030.



CR:218682
CR Number:   218682
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.x Catalina
Fixed Version Build Resolution Date Closure Code (If Appropriate)
30 Jun 2004 EOL'd version. Not to be Fixed.
Description
Regression Pb 6 (>build 1176) and 7 (>build 5031)
RowFocusChanged and RowFocusChanging events are not triggered when a retrieve returns no rows,
even though the current row has changed to 0.



CR:218685
CR Number:   218685
Product Name:   PB Enterprise
Product Component:   Window - Runtime
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
09 Oct 2000 Presently Not Targeted For Any Future Release Of This Product
Description
When the NT 4.0 desktop Appearance is changed to Windows Standard ( extra large) the data value in an editmask spin control is truncated when filling the spin control. This did not happen in PB 5.0 or 6.5.1.



CR:218745
CR Number:   218745
Product Name:   PB Enterprise
Product Component:   Jaguar Integration
Status:   Closed
OS:   Solaris 2.6
Original Version:   7.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
02 Jan 2001 Not a Bug
Description
Retrieving on htmldw where ea server 3.5 is
running on solaris,the following error appears ea server console:

SmartHeap error handler recursively reentered
Abort, Retry

The following error appears in the srv.log file:
May 17 08:40:48 2000: HTMLDW: Entering SetSelfLink('testjdsbonnoamt.htm','')
May 17 08:40:48 2000: HTMLDW: Entering SetWeight()
May 17 08:41:00 2000: SIGABRT 6* abort (generated by abort(3) routine)
May 17 08:41:00 2000: si_signo [6]: SIGABRT 6* abort (generated by abort(3) routine)
May 17 08:41:00 2000: si_errno [0]: Error 0
May 17 08:41:00 2000: si_code [-1]: SI_LWP [pid: 14648, uid: 1001]



CR:218752
CR Number:   218752
Product Name:   PB Enterprise
Product Component:   Jaguar Integration
Status:   Closed
OS:   Solaris 2.6
Original Version:   7.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
02 Jan 2001 Not a Bug
Description
When retrieving a htmldw running on ea server on solaris,
the following error appears in the console:

mem_bad_mem pool error
abort, retry

The following errors appear in the srv.log:
May 17 09:53:03 2000: HTMLDW: Entering Generate()
May 17 09:53:21 2000: SIGABRT 6* abort (generated by abort(3) routine)
May 17 09:53:21 2000: si_signo [6]: SIGABRT 6* abort (generated by abort(3) routine)
May 17 09:53:21 2000: si_errno [0]: Error 0
May 17 09:53:21 2000: si_code [-1]: SI_LWP [pid: 15309, uid: 1001]
May 17 09:53:21 2000: stackbase=0, stackpointer=CCA11B4C

Per Development:
Made the following change to testhtml.htm and problem went away:
I found that the following line in the .htm file maybe the cause that hangs the server:
dwMine = new PSDataWindowClass("htmlDW", true, jagConn, dwCource, dbConn);
You should change this to the following and have a try:
dwMine = new PSDataWindowClass("htmlDW", false, jagConn, dwCource, dbConn);
With the second parameter set to "false", a SetComplete() will happen after the Generate() method (of the HTML Generator) is called. This allows the HTML generator to be deactivated and pooled.



CR:218756
CR Number:   218756
Product Name:   PB Enterprise
Product Component:   Window Painter
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.2 9002 15 May 2003 Fixed
Description
graph control hangs PB when altering axis values and use scale type log10! or loge!
For example if you type in for example 10E-10 in the MinimumValue and tab to MaximumValue in the Axis propertie tab then PB hangs up.



CR:218765
CR Number:   218765
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)
7.0.2 31 Jul 2000 Fixed
Description
7.0.2ebf Regression. A string editmask (such as for a phone number) now returns trimmed values for Gettext() or dwo.data if the underlying data does NOT fill the editmask. In the past (3.0 to 7.0.2 8024), when a char(10) field had 3 characters in it, and an editmask of (###) ###-####, (10 total mask characters), the Gettext() would always return '123<7 padded spaces>'. And as such Len(Gettext()) in script would also show 10.

This was caused by the to CR208886 in 7.0.2 8025, after this, several behaviors are noticed:
1. A partial value "123" in a 10 character phone editmask now shows "(123" without the closing paren ")"
2. Gettext() and/or dwo.data for the char(10) field with 3 characters (not completely filled field) returns only 3 characters.

Also, in the past, if you entered "123" in char(10) field, The datawindow would put "123<7 padded spaces> in the buffer so with Update() and subsequent retrievals, the mask was always "Filled" to 10 characters.

In other words, in the past, no matter how many characters were in the char(10) column buffer, Gettext() ALWAYS padded the data in the past.



CR:218812
CR Number:   218812
Product Name:   PB Enterprise
Product Component:   DB ODBC
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
When using the ODBC driver for Microsoft SQL Server 7.0 "SQLSRV32.DLL", version 3.70 against a SQL Server 6.5 database with NO SQL Server service packs installed, datetime fields will retrieve into datawindows or in the database painter with question marks (01/??/01 00:00:00). This only seems to happen in ODBC and with PowerBuilder 7.0 (all versions) and SQL Server 6.5 with no service packs.

This is not a PowerBuilder bug but is being noted since a lot of customers will hit this upgrading from prior versions of PB (4.0-6.5) to PB 7.0 and using the SQL Server 7.0 ODBC driver "SQLSRV32.DLL" version 3.70.06.23 against SQL Server 6.5 databases and ODBC version 3.51. This is not a problem in prior versions of PowerBuilder.

To tell what service packs (if any) are installed in SQL Server 6.5:
Issue the following in the ISQL_W tool for SQL Server or in the database painter, ISQL view

Select @@version

You should get back a version string... Here's the decoding:
6.50.201 - Original SQL Server release.
6.50.258 - Service Pack 3

An ODBC trace might reveal:
DIAG [01000] [Microsoft][ODBC SQL Server Driver][SQL Server]The ODBC catalog stored procedures installed on server <XYZ> are version 6.50.193; version 07.00.0523 or later is required to ensure proper operation. Please contact your system administrator. (0)


We also made updates to the pbodbxx.ini files for the newer driver:
(an ODBC trace will identify this driver as "Microsoft SQL Server" - which will be used to look up a section in the pbodb70.ini.

Original pbodb70.ini
=================
[Microsoft SQL Server]
PBDateTime='DEFAULT_DATETIME'

[DEFAULT_DATETIME]
PBDateFmt=''{d '\'yyyy-mm-dd\'' }''
PBTimeFmt=''{t '\'hh:mm:ss\''}''
PBDateTimeFmt=''{ts '\'yyyy-mm-dd hh:mm:ss.ffffff\''}''

New pbodb70.ini
==============
[Microsoft SQL Server]
PBDateTime='MSSQLSERVER_DATETIME'

[MSSQLSERVER_DATETIME]
PBDateFmt='\'yyyy-mm-dd\''
PBTimeFmt='\'hh:mm:ss\''
PBDateTimeFmt='\'yyyy-mm-dd hh:mm:ss.fff\''

Solution: Upgrade you SQL Server 6.5 to at least service pack 3 and check your PBODB70.ini for compatibility.



CR:218830
CR Number:   218830
Product Name:   PB Enterprise
Product Component:   Jaguar Integration
Status:   Closed
OS:   Solaris 2.6
Original Version:   7.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
25 Feb 2004 Fixed
Description
Getting a mem_bad_pointer error when a
intercomponent call is made to a component when an argument is
passed by reference. The component being called is in a separate
package and returning an integer. The component also has a
argument passed by value.

May 18 12:16:20 2000: DEBUG: ravitest/n_pbsolarisbug1 (constructor)
May 18 12:16:20 2000: DEBUG: ravitest/n_pbsolarisbug1/$Activate (bind)
May 18 12:16:20 2000: DEBUG: ravitest/n_pbsolarisbug1/solarisbug__N
May 18 12:16:20 2000: DEBUG: ravitest/n_pbsolarisbug1/$Deactivate (unbind)
May 18 12:16:20 2000: DEBUG: ravitest/n_pbsolarisbug1 (remove container 686)
May 18 12:16:20 2000: DEBUG: ravitest/n_pbsolarisbug1/$CanBePooled (poolable)
May 18 12:16:20 2000: DEBUG: ravitest/n_pbsolarisbug1 (destructor)
May 18 12:16:26 2000: SIGABRT 6* abort (generated by abort(3) routine)
May 18 12:16:26 2000: si_signo [6]: SIGABRT 6* abort (generated by abort(3) routine)
May 18 12:16:26 2000: si_errno [0]: Error 0
May 18 12:16:26 2000: si_code [-1]: SI_LWP [pid: 19008, uid: 1001]
May 18 12:16:26 2000: stackbase=0, stackpointer=ECD21F0C
May 18 12:16:26 2000:



CR:218845
CR Number:   218845
Product Name:   PB Enterprise
Product Component:   MTS Integration
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   8.0 Beta 1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
14 Jun 2000 Not a Bug
Description
Migrated test case from pb 7.02 to 8.0 while recreating
com/mts object, fails to build in project painter. Fails on component server build.

The following are the results of the build in pb:

---------- Deploy: Deploy of p_testcrash6
Performing Incremental Rebuild of Objects
Parsing User Object uo_testcrash6...
Beginning generation...
Generating IDL file...
Generating IDL file...
Generating Type Library...
Generating the PB COM Server
Generating GUID source file...
Generating Interfaces header...
Generating Classes header...
Generating Server Data source file...
Generating Classes source...
Generating server resource file...
Compiling GUID Source File ..
Compiling PB COM Object Source File ..

Compiling PB COM Server Source File ..

Linking PBCOM Server object files

Generation Results:
OBJECT INSPECTION RESULTS:
uo_testcrash6
Instance variables:
Instance Variables: PASSED

Functions:
Functions: PASSED
BUILD RESULTS:
IDL File Generation: succeeded
Component Server Build: failed
---------- Finished Deploy of p_testcrash6



CR:218865
CR Number:   218865
Product Name:   PB Enterprise
Product Component:   DPB
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.0 16 Oct 2000 Fixed
Description
Documentation. Timeout property of transport object should be documented as being in milliseconds, not seconds.



CR:218869
CR Number:   218869
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)
06 Feb 2001 Fixed
Description
Whenever a User is not specifying the query starting in row 1 the Querymode where clause is not correctly moved into the table select statement and additionally without proper error handling the message "Specified criteria Invalid " appears.

Possible Workaround:
Start specifiying the query in row 1 of the dw.
Workaround Description
 Start specifiying the query in row 1 of the dw.
(But: This is Not always wanted from users)





--------------------------------------华丽的分割线-------------------------------------------------------------------------
之前就已经研发成功了能够从Sybase SQL Anywhere的DB文件中恢复数据的工具:ReadASADB。
此工具支持ASA v5.0,v6.0,v7.0,v8.0,v9.0,v10.0,v11.0,v12.0等版本。
恢复Sybase SQL Anywhere的工具在国内应该算首创。

ReadASADB功能
能够从损坏的SQL Anywhere数据文件(.db)和UltraLite数据文件(.udb)上提取数据的非常规恢复工具

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

ReadASADB适用场景

各种误操作:

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

本工具的应用场景:

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