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

 

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

如有问题,请联系我!

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

 

CR:214575
CR Number:   214575
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 8046 07 Sep 2000 Fixed
Description
When a freeform dw returns only 1 row and autosize
height is turned on, the scrollbar will bounce back to the top when dragged.
Also if you click in the grey area of the scrollbar, it won't scroll.
Happens when the dw control is slightly smaller than the freeform dw.

Works ok when more than 1 row is retrieved and when autosize height
is turned off. Also when the dw control is adjusted so that the all the data
from the freeform shows in the dw control.
Workaround Description
 Readjust the size of the dw control or turn off autosize height.



CR:214587
CR Number:   214587
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)
30 Nov 2011 Deferred
Description
Getfullstate/Setfullstate doesn't store images in blob. This is really a Distributed Powerbuilder, Jaguar with Powerbuilder issue. If you use a Powerbuilder client and use Getfullstate() on the server to serve down a datawindow to a client, it doesn't send down the images that might be either in

1. Picture objects on the datawindow.

2. Picture objects in computed fields referenced in a Bitmap(s) type of call.



The problem with this (and there might not be a good solution) is that you must deploy all the bitmaps the user could use on each PowerBuilder client. This causes problems since if these are catalog pictures, they would probably always be out-of-date.



Suggestion: If you're trying to build some kind of shopping cart application with a PowerBuilder Client talking to Jaguar you need to find a better way to present the data. One way is to have a static hyperlink on the window next to the datawindow on the PowerBuilder client instead of the actual picture in the datawindow computed field or picture object (which requires the .bmp, .gif on the path somewhere just to render the picture).



When a person clicks on the row in the datawindow "catalog", set the static hyperlink on the window to "http://mycompany.com/catalog/item326897.gif or a page containing a link to the .gif(s). Let the click on the hyperlink in the datawindow bring up a browser window that displays the bitmap - perhaps on a simple page served up off a web server.



This solution requires a web server but web servers are better at serving up images anyway, plus the browsers are set up to check "stale" files like bitmaps, .gifs or images - something the server application would have trouble doing.



CR:214589
CR Number:   214589
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)
10 Dec 2000 Fixed
Description
OO problem with custom visual user objects.
Fixed in 7.0.2 build 8030 and after.



CR:214628
CR Number:   214628
Product Name:   PB Enterprise
Product Component:   Function Painter
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15 Nov 2000 Duplicate
Description
Adding arguments in the function painter of a uo, nvo, menu,application
or window caused pb to crash.



CR:214631
CR Number:   214631
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)
19 Oct 2000 Duplicate
Description
7.0 Behavior. The new Find window for 7.0 (found anywhere in the script painter where you can use Control-F) does not automatically begin searching after you enter a string and hit the enter key. The reason is PowerBuilder 6.0 had a FIND window where the input was an SLE, the new 7.0 FIND window has an input field that is a dropdownlistbox which contains the last 10 searches. Due to this change in the interface, the default button "FIND NEXT" no longer works in this dialog.



CR:214635
CR Number:   214635
Product Name:   PB Enterprise
Product Component:   Debugger
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.5.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15 Nov 2000 Fixed
Description
PB crashes in the debugger when selecting a function
with numerous arguments.
Workaround Description
 Limit the number of arguments or shorten the names of the args



CR:214677
CR Number:   214677
Product Name:   PB Enterprise
Product Component:   DB Sybase System
Status:   Open
OS:   MS Windows NT 4.0
Original Version:   7.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
Customer wants to have ability to fetch values from a Sybase ASE database text field that are bigger than 32 k into a string variable directly, both via a Select statement and via a stored procedure.



CR:214703
CR Number:   214703
Product Name:   PB Enterprise
Product Component:   PB GUI
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
04 Apr 2000 Fixed
Description
A function with numerous arguments gets truncated
in the function list view. This is happening in the uo, window, menu, and application
painters when you select view/function list. Scroll to the right and argument
list is truncated.



CR:214707
CR Number:   214707
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)
8.0 Beta 2 16 Oct 2000 Fixed
Description
Clarification of Display Format Masks and EditMask Masks.

Legal Display Formats (Focus OFF or Print Preview)
=========================================
Dates
[ShortDate] and [LongDate]. This uses the Registry ShortDate and Long Date formats. This is not documented.

Currency
[Currency] is documented but a user could also use $#,##0.00 The meaning of this is $ (an anchor symbol) should always replace whatever is in the Control Panel "currency" symbol setting. If your setting is Euro () in the Control Panel Regional Settings, you should still enter "$" in the mask if you want the symbol to appear and the runtime engine will substitute <EURO>3,343.34 for example. Do not use the Localized Symbol in the Display Format Mask
Ex: <Euro>#,##0.00 is not a legal display format mask. <Euro> represents the actual Euro Symbol..

Legal Edit Mask Formats (Focus ON)
=============================
Dates
[Date] and [Time] are legal arguments as are combinations already documented with mm dd yy , etc.
[ShortDate] and [LongDate] are NOT valid (they are Display Format Masks)

Currency
[Currency(n)] - ex [Currency(7)] - is a legal format. [Currency] is not a legal Edit Mask. It will not be editable when focus is on the column.

New Property on Edit Style EditMask "Use Format"
=======================================
A new property of the Edit Mask was added in PB/IM6.0 called "Use Format" (it's on the edit tab of a column when you choose edit mask as an edit style). This allows you to have a different display format (focus off) than edit mask (focus on). Prior versions of PB/IM caused an edit style of Editmask to always carry over and override any Display Format Mask (focus off or print preview)



CR:214708
CR Number:   214708
Product Name:   PB Enterprise
Product Component:   DB Oracle
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 8024 30 Mar 2000 Fixed
Description
Creating a datawindow in the painter or by using SyntaxFromSql() takes a long time if the database contains many synonyms.



CR:214741
CR Number:   214741
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)
8.0 Beta 1 1270 12 Apr 2000 Fixed
Description
Font charset isn't saved in the syntax . When syntax is exported, modified so that it matches the desired charset value and reimported, the dw painter does not select the charset but show ansi! instead.



CR:214747
CR Number:   214747
Product Name:   PB Enterprise
Product Component:   UO Painter
Status:   Closed
OS:   Microsoft Windows 98
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
02 Mar 2004 Not a Bug
Description
This is a regression 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 a PB execution error "R0021 - Bad runtime reference" ;

Per Development, this is not a bug:
Issue with the order of functions in exported source code is NOT the cause of the problem. This is normal behavior with how the painter writes out function prototypes and has nothing to do with the compiled object. The problem is occuring because you are not allowed to build specific PBDs and deploy to older versions ESPECIALLY when the changed object's ancestor is in a different PBD.
Workaround Description
 a) Generate a new application executable and library OR b) Save the export file of the "user" object before and after changes to the functions. Then re-order the contruction statements and import. (see main desc section)



CR:214754
CR Number:   214754
Product Name:   PB Enterprise
Product Component:   Application Painter
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
18 Sep 2000 Fixed
Description
'Recent Applications' list is case sensitive causing duplicates in rare cases. For example:
H:\SomeDir\test.pbl
and
H:\somedir\test.pbl

are seen as different entries and will show up separately in the Recent Applications list off on File Menu.



CR:214759
CR Number:   214759
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)
09 Mar 2000 Fixed
Description
Documentation. In Version 7.0 Datawindow Programmer's Guide page 168 bullet 7, the "PowerBuilder Application" property of the DataWindow/HTMLGenerator component should be "remote_datawindow_appl".



CR:214768
CR Number:   214768
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)
25 Feb 2004 EOL'd version. Not to be Fixed.
Description
SmallInt/SmallMoney/SmallDatetime datatypes not seen by DW Stored Procedure Update Screen using ODBC drivers. Other parts of the datawindow painter handle them well enough to create a datawindow. (The native Driver SYC does not have this problem).

If you get a "301" illegal outer join request using the ODBC driver, this is caused by a call to the stored procedure sp_tables. You will need to update to a newer version of this stored procedure.

Workarounds:
1. Define the arguments to the stored procedure temporarily as "INT" instead of "SMALLINT" when you build the stored procedures used in the Stored Procedure Update dialog if using ODBC. Later, Drop and Recreate the procedure(s) with the correct Smallint arguments.
2. Use the native driver (SYC - CTLIB).



CR:214769
CR Number:   214769
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)
19 Oct 2000 Duplicate
Description
This problem occurs when a customer leaves a script to go to another pane, such as attributes and the comes back to the script by clicking the tab at the bottom of the script editor. The cursor does not return to the script. You must click the left mouse button in the script to bring the cursor back.
Workaround Description
 Position the mouse pointer in the scipt and click the left mouse button.



CR:214816
CR Number:   214816
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)
16 Mar 2004 EOL'd version. Not to be Fixed.
Description
Sybase SQL Server 11.x (Adaptive Server Enterprise) will throw an error if you issue an Update() call from a datawindow into a character column and it contains certain symbols like the Euro symbol.

This happens using the PBSYC driver (CTLIB) and with the Intersolv 3.11 ODBC driver and doesn't happen with the PBSYT (DBLIB) driver (NT). The update also works fine using the native Microsoft driver PBMSS against Microsoft SQL Server.

The error is: Error converting client characters into server's character set. Some character(s) could not be converted. No changes made to database.
INSERT INTO dept ( dept_id, dept_name ) VALUES ( 400, '<euro symbol>something' )

The ODBC error would contain "SQLSTATE S1000 [INTERSOLV][ODBC SQL Server driver][SQL Server]"



CR:214817
CR Number:   214817
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 8047 26 Jun 2000 Fixed
Description
7.0.2 Regression. The Horizontal Scrollbar appears to now be obscuring the footer band in the datawindow painter "preview" mode (not print preview). It appears the datawindow calculations for display is putting in one more detail line and this extra detail line obscures the footer band field(s) that should be displaying there.

There seem to be runtime problems associated with this bug too when either the resizable or horizontal split scrollbar is used separately - again with the painting of the footer... Painting problems (specks) are observed when you manipulate the horizontal scrollbar with horizontal split scroll on.



CR:214822
CR Number:   214822
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 Jun 2004 EOL'd version. Not to be Fixed.
Description
7.0 Regression. A crosstab with a numeric retrieval argument will GPF on the second retrieve if you enter a value that is out of range (16 digits). The error in SQL Anywhere would be: SQLSTATE 22003 [Sybase][ODBC Driver][Adaptive Server Anywhere]Numeric value out of range: Value 1234567890123456 out of range for destination.

The second time you submit a query (even if it's within the numeric range), the retrieval will GPF.



CR:214827
CR Number:   214827
Product Name:   PB Enterprise
Product Component:   Structure - 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
SImple application with two identical structures. Identical character data is entered and then a test of equality is applied to members. Testing equality of structure variables works in development, pcode, but fails in machine code.



CR:214842
CR Number:   214842
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)
25 Feb 2004 Fixed
Description
Unable to make an Intercomponent call from a PowerBuilder object on EA Server for Solaris if the function passes a variable by reference.
Workaround Description
 Pass variable by value will not produce the error.



CR:214858
CR Number:   214858
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)
25 Feb 2004 EOL'd version. Not to be Fixed.
Description
Last row in dropdown isn't visible. But it can be selected by clicking on the space. If height of detail band is changed from 64 to 60 PBU the last row becomes visible.
Workaround Description
 Change height of detail band from 64 to 60 PBU then the last row becomes visible.



CR:214901
CR Number:   214901
Product Name:   PB Enterprise
Product Component:   DW Printing
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.5.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
01 Aug 2000 Fixed
Description
Setting the tray selection for PCL printers such as the HP 4si using datawindow.paper.source does not work. It always selects the upper tray.

This works for postscript printers.

4/28/2000 Update:
If you are printing LETTER for upper and lower trays, you should make sure their lower cartridge is for LETTER (not just loaded with letter but an actual LETTER cartridge). If the LOWER cartridge is truly a LEGAL or A4 size cartridge, the only way the printer will print there is if you set the Paper Size to LEGAL or A4 and the tray to LOWER.

Also, the documentation is incorrect for Paper.Source. It states the Paper.Source=2 means "Lower Tray" when this is really only for HP III, IV printers. The value for (ex) Lower Tray can be determined by using API calls but it's generally different for each printer. Utilities exist to query this value: www.powerwhizz.com is one.

dw_1.Object.DataWindow.Print.Paper.Source = 257

might be a perfectly legal use of setting Paper.Source to "Lower Tray" on a specific printer.



CR:214903
CR Number:   214903
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
HTML DW DDDW width does not display as in PowerBuilder when you have a width other than 100% for the dropdown. This is because the HTML datawindow renders the DDDW as a list and there is no way in HTML to control this width except by the width of the largest item in the listbox.



CR:214904
CR Number:   214904
Product Name:   PB Enterprise
Product Component:   Debugger
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.5.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Oct 2000 Duplicate
Description
Unable to debug functions that contain long argument names in the arugment list.



CR:214920
CR Number:   214920
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
HTMLDW layout may be wrong in specific circumstances.The HTML generated will span a column "N" over 2 columns and the "N+1" column goes down.
Workaround Description
 Modify the width property or the X position of the preceding column that goes down until getting a correct layout .



CR:214924
CR Number:   214924
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)
10 Mar 2000 Duplicate
Description
The 7.0 documentation (on-line) has an error for the return codes for SetFullState(). I shows return values of 1,2 and NULL. The 7.0 code still returns 3 in the condition described below but the doc says "NULL".

Return value condition that is incorrect:
Null - No DataWindow object associated with DataWindow control or DataStore; new one assigned from DataWindow blob

The correct return code value is "3".



CR:214925
CR Number:   214925
Product Name:   PB Enterprise
Product Component:   Script Painter
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.x Catalina
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15 Nov 2000 Fixed
Description
PB Version and Build: Docs PB 6.x and PB 7.x
Doc: Powerscript reference Vol1, Chap 4, Page 79

Comments:
In the section concerning 'Data type promotion when evaluating numeric expressions' the manual gives rules for data type promotion with operators / and ^

It states: The minimum precision for division and exponentiation is double. All types are promoted to double before doing the calculation, and the expression's resulting data type is double.

Not so, if all the types in the calculation are decimals or lower, then the data type is not promoted to double for the calculation, it remains decimal. This behaviour is as described in 'Data types of operands' rule on the previous page. The documentation states that all data types always be promoted to double whereas they are only promoted to the data type of higher preference.



CR:214926
CR Number:   214926
Product Name:   PB Enterprise
Product Component:   Function 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 8027 01 Aug 2000 Fixed
Description
7.0. RPCs (Remote Procedure Calls) functions normally used in Local External Function declarations (to call stored procedures with Powerscript coding that looks like a normal function call) are now showing up in function list for an object such as a user object, menu or window (they should not).

This is dangerous since you can pick the function from the (Function) list in the Script view or through View/Function List from the menu pick. You can actually place code in the script painter (for the RPC) and save it and the behavior might be to create a new "overloaded" function call (an object function call) with the same prototype as the Local External Function call that might get called instead.



CR:214932
CR Number:   214932
Product Name:   PB Enterprise
Product Component:   Script Painter
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
When regional setting are set to decimal separator comma (e.g. German Standard) and the PBScript is compiled with that setting then exponential literal scale is lost.
Workaround: Switch to English regional settings to save exponential literals in PBScript - afterwards application runs fine with all settings



CR:214970
CR Number:   214970
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.3 8023 14 Mar 2000 Fixed
Description
7.0 Regression. The composite datawindow wizard is very slow if the number of datawindows in the application is large (hundreds). It can take 5 minutes on a very large application to build the list of datawindows to pick from.

Fixed in builds after March 10th, 2000.



CR:214996
CR Number:   214996
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)
16 Mar 2004 EOL'd version. Not to be Fixed.
Description
There appears to be a regression or requirement in Internet Explorer (IE) 5.0 that upsets the display of a background color for the detail band in the HTML datawindow when the developer chooses the "Generate CSS" checkbox . ( checking this checkbox creates style sheets in the HTML datawindow generated output which IE uses to render a background color to, in most cases, the tabular rows)

Some users will report the background color works in IE 4.0 but disappears in IE 5.0.



CR:214999
CR Number:   214999
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)
19 Oct 2000 Not a Bug
Description
Structure Painter is in overstrike mode when editing element names.



CR:215001
CR Number:   215001
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)
6.5.2 27 Jun 2000 Fixed
Description
DataWindow EditMask in PB6, when the column datatype is NUMBER, mask has dashes in it (ie. ###-##-###), when you highlight the contents and enter a value, can only enter 1 digit.



CR:215003
CR Number:   215003
Product Name:   PB Enterprise
Product Component:   DW Wizards
Status:   Closed
OS:   Microsoft Windows 98
Original Version:   7.x Catalina
Fixed Version Build Resolution Date Closure Code (If Appropriate)
03 May 2000 Fixed
Description
During creation of NEW dw of Crosstab, Graph OR Group presentation style with Data Source - Query with retrieval arguments. PB gives the following error at the end of the dw wizard :
'Arguments for select are invalid or incorrect' .



CR:215043
CR Number:   215043
Product Name:   PB Enterprise
Product Component:   Window - Runtime
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   7.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.2 8024 27 Dec 2000 Fixed
Description
Open/close sheet with menu leaks GDI and Systems resources in Win 95.
Verified fixed in 7.0.2 Build 8024



CR:215118
CR Number:   215118
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)
14 Mar 2000 Not a Bug
Description
Pfccom32.dll regression: Unable to change default printer in registry after pfccom32.dll is loaded.



CR:215142
CR Number:   215142
Product Name:   PB Enterprise
Product Component:   Jaguar Integration
Status:   Closed
OS:   Solaris 2.6
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
19 Dec 2000 Fixed
Description
PowerBuilder 7.0 component on Jaguar 3.0.1 and 3.5 on Solaris 2.6. SetFullState against a datastore is failing and causing the component to immediately - as in mid-method call - deactivate (when stateless) or immediately return with no error in srv.log. (immediate deactivate is the result of a VM crash)



CR:215148
CR Number:   215148
Product Name:   PB Enterprise
Product Component:   DW - Runtime
Status:   Closed
OS:   Microsoft Windows 98
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
The problem is that in the dw ItemError event, the edit control of the CURRENT row-column STORES the item value of the PREVIOUS row-column which had received focus (irrespective of the current column datatype).

In this scenario, the customer is calling the AcceptText() method in the RowFocusChanged event.

The value which should be in the ItemError "data" argument is empty string "" because the user has pressed the TAB key to exit the column and triggers the warning :
"Datawindow error" default msg "Value required for this item" ;

Within PB DEBUG mode, the erroneous value is displayed in the edit control AND is erased at the end of RowFocusChanged event.



CR:215164
CR Number:   215164
Product Name:   PB Enterprise
Product Component:   Source Control
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.5.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
05 Jul 2000 Third Party Problem
Description
Unable to check-out objects when PVCS is installed on a network machine. Check-out will work for most objects, however there may be a few that cannot be checked out.



CR:215257
CR Number:   215257
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
Objects in a dw summary band are displayed incorrectly at runtime of dw PRINT PREVIEW mode.
The 2 problems are:-
-Summary band information overlaps the last imported row (test 1)
-Repaint is incorrect for vertical scrollbar(test 2)

This is not a problem for
-DW (with or without) summary band displayed at runtime.
-DW WITHOUT summary band displayed at runtime in PRINT PREVIEW mode.



CR:215259
CR Number:   215259
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.2 08 Aug 2000 Fixed
Description
Getting ''This database does not support the retrieval of procedure text.'' trying to see procedure syntax in several areas of the product (datawindow painter, etc) connected to Adaptive Server IQ (ASIQ).

The Adaptive Server IQ 12 driver is really the same as SQL Anywhere but because there is no section in the pbodb60.ini, pbodb70.ini and pbodb80.ini for Adaptive Server IQ, certain things default and, for instance, you can't see procedure text in the datawindow painter when painting a datawindow with stored procedure source.

A NEW section needs to be added section to the pbodb60.ini pbodb70.ini pbodb80.ini called

[Adaptive Server IQ]

The contents of this section should be the ENTIRE contents of the [Adaptive Server Anywhere] section in the pbodbxx.ini file. The ASIQ driver identifies itself as "Adaptive Server IQ" - this is why the name of the section must be exactly this.

NOTE: This fix and it works correctly after adding the section to the PBODB70.ini file. For the stored procedure text problem, what fixes it for ASIQ is the [Adaptive Server IQ] PBSyntax='WATCOM50_SYNTAX' setting which if you follow it through to the [WATCOM_SYNTAX] section, has a "PBSelectProcSyntax" section that has the actual SQL that brings back the text of the stored procedure.



CR:215287
CR Number:   215287
Product Name:   PB Enterprise
Product Component:   DPB
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
DPB Server leaks memory on simple remote object function call



CR:215299
CR Number:   215299
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)
14 Aug 2001 Fixed
Description
You will get the following error message if you try to open a window which contains a custom visual user object, which has just been modified:

PowerBuilder Application Error (R0023)
Application terminated.
Error: Cannot assign object of type xxx to variable of type xxx at line x in create event of object xxx.
Workaround Description
 Regenerate the window object.



CR:215336
CR Number:   215336
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 Apr 2000 Fixed
Description
Running two sessions simultaneously of the same PFC app with a treeview, gets memory error.
This has been reproduced in house using the peat app. It happens in development mode as well as with exes. Run a session of PB with the Peat app and the initial frame and sheet open. The sheet has a treeview in the left pane. Now without moving the visible window, start up another PB session agin with the Peat app. Run it and the error occurs before the second sessions treeview sheet is visible.
.
Efforts to simplify this have failed. Simple windows with treeviews do not fail. Simple PFC apps with sheets inherited from w_sheet and that have treeviews do not fail. Even creating a different sheet in the treeview app with a treeview does not always fail. The original peat app is the best reproduction.
Workaround Description
 1. Move the code which open the window with treeview from pfc_open event to pfc_postopen event.
2. Move the code which open the window with treeview from pfc_open to a Menu item."



CR:215399
CR Number:   215399
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)
25 Feb 2004 Fixed
Description
PFC: The of_rollback function in the pfc_n_tr object has the rollback inside the test for isvalid on gnv_app.
All other functions of n_tr have the actual sql statement outside of this if block.



CR:215458
CR Number:   215458
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)
16 Mar 2004 EOL'd version. Not to be Fixed.
Description
7.0 Regression. A label style datawindow that once printed fine on 5.0.04 now shifts down each label (one label per page) on each subsequent tractor fed page.



CR:215462
CR Number:   215462
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)
17 Oct 2000 Duplicate
Description
7.0 Regression. Listview (rightmouse up) pbm_rbuttonup (and LEFTmouse up pbm_lbuttonup) don't fire anymore. May be due to the fact that we're using the Microsoft Listview Control. When the user rightclicks using the mouse on the treeview, PowerBuilder 6.0 would fire the rightclicked (pbm_lvrclicked), then the rightbuttonup (pbm_rbuttonup). In 7.0, the rightclicked event is being fired but not the rightbuttonup.

The rightbuttonup event only gets fired when the user rightDOUBLEclicks on the listview, not when they rightclick. This would affect code in the rbuttonup event. PFC uses this event to popup a menu (2 different ones depending if you rightclick in a blank area or over a specific item in the listview).

Workaround: If using the PFC_U_LV and PFC_U_LVS and the feature to use popup menus... Rightdoubleclick seems to bring up the popup menus. (mostly because it does fire the rbuttonup event)

NOTE: The leftbuttonup (pbm_lbuttonup) also doesn't fire on clicked or doubleclicked events for the LEFT mouse in 7.0 - similar to the rightbuttonup (pbm_rbuttonup). This is not a standard event, you have to map it.



CR:215488
CR Number:   215488
Product Name:   PB Enterprise
Product Component:   DW DDDW
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 8027 28 Apr 2000 Fixed
Description
If the country settings are set to:
- decimal separator to comma
- grouping symbol to space.
And a dddw stores for example the decimal values 10,000 and 10,001 and 10,002 and 10,003.
If you choose for example 10,002 from the dddw and if you then press tab key.
=> It will show 10,000 instaed of 10,002.
This doesn't happen if you type in the value or if the dddw does not include the 10,000.



CR:215513
CR Number:   215513
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.2 8046 13 Jul 2000 Fixed
Description
7.0.2ebf Regression. Datawindow rows getting cut off (scrolling up into header) when the horizontalscrollsplit property is set on and the user scrolls by page by clicking beneath the thumb on the elevator of the vertical scrollbar. After 2-3 clicks, the top row on the datawindow is half scrolled into the header band text (if there are objects up there)

Related to CR214817. "7.0.2 Regression. Footer band data no longer showing in datawindow painter." and broken around the same time.

Related to CR219443. You cannot click on the LAST visible row in the detail band in the datawindow control.

Update from Development:
The problem with datawindow rows getting cut off (scrolling up into header) when the horizontalscrollsplit property is set on and the user scrolls by page by clicking beneath the thumb on the elevator of the vertical scrollbar has been fixed.
NOTE: As a result of re-working the ScrollBar Initialization routines:
1) If the dwControl is wide enough to show the entire width of the report, then a Horizontal ScrollBar is NOT required and is not shown.
2) If the Horizontal ScrollBar is not shown then the Split Control is not shown.



CR:215525
CR Number:   215525
Product Name:   PB Enterprise
Product Component:   DB Oracle
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 8036 25 Feb 2004 Fixed
Description
Database driver handle leaks showing up using O73, O84 drivers. This is particularly bad in Web.PB, distributed and Jaguar applications.



CR:215545
CR Number:   215545
Product Name:   PB Enterprise
Product Component:   DW ActiveX
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 9008 25 Feb 2004 Fixed
Description
GetItem & SetItem don't function properly with a Web control for ActiveX if value is null.
SetItem doesn't actually set the value and returns -1 return code.
GetItem doesn't return NULL value when column value is indeed NULL.
Workaround Description
 No workaround. Fix required.



CR:215553
CR Number:   215553
Product Name:   PB Enterprise
Product Component:   Language - Runtime
Status:   Closed
OS:   MS Windows 3.1
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
Openwithparm may lead to GPF in PBVM60W.DLL at 004F:2844 in specific circumstances.



CR:215556
CR Number:   215556
Product Name:   PB Enterprise
Product Component:   Script Painter
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
20 Dec 2000 Fixed
Description
Script Painter swapping script between function and event on a save.
Verified fixed in 7.0.2 8046 EBF C3.



CR:215622
CR Number:   215622
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)
13 Jul 2000 Fixed
Description
7.0 Regression. The Find/Replace dialog (also known as the 'Replace Text' dialog) "Replace All" with "Wrap at Beginning and End" checked does not replace the LAST instance BEFORE the cursor position as it wraps around.

For example, if the script shows:

// sqlca (Line 1)
// sqlca (Line 2) < > <---- Put cursor inside brackets
// sqlca (Line 3)

If you perform a Edit/Replace replacing sqlca with another string (with "Wrap at Beginning and End" checked and click on the "Replace All" button, it won't replace the sqlca in Line 2.



CR:215628
CR Number:   215628
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)
16 Oct 2000 Not a Bug
Description
7.0 Regression. 7.0 Regression. Treeview pbm_tvnrbuttonup (right mouse up), pbm_lbuttonup (left mouse up) and pbm_tvnrdoubleclicked (Right doubleclicked) events don't fire. May be due to the fact that we're using the Microsoft treeview Control in PB 7.0. The rightclicked event does fire, however.

NOTE: The change in behavior is due to us using the Microsoft Treeview control in 7.0. Unlike the listview, the treeview doesn't have the WM_Contextmenu (pbm_contextmenu) so the user might use the rightmouseup to handle any popup menus.

Differences between 6.5 and 7.0

right mouse click:
6.5 rightbuttonup, rightbuttonclicked
7.0 only fires rightbuttonclicked, not rightbuttonup

right mouse doubleclicked:
6.5 rightbuttonup, rightbuttonclicked, rightbuttondoubleclicked,rightbuttonup, rightbuttonclicked
7.0 rightbuttonclicked, rightbuttonup (reverse order + other events missing)

LEFT mouse clicked:
6.5 leftbuttonup, leftbuttonclicked
7.0 leftbuttonclicked,leftbuttonup (opposite order from 6.5)

LEFT mouse doubleclicked:
6.5 leftbuttonup, leftbuttonclicked, doubleclicked, leftbuttonup, leftbuttonclicked
7.0 leftbuttonclicked, leftbuttonup, doubleclicked,leftbuttonup (different than 6.5)

Workarounds:

For rdoubleclicked, (pbm_tvnrdoubleclick), use pbm_rbuttondblclk
For lbuttonup, use pbm_lbuttonup.



CR:215633
CR Number:   215633
Product Name:   PB Enterprise
Product Component:   Installation
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
19 Jun 2000 Presently Not Targeted For Any Future Release Of This Product
Description
7.0.2 Maintenance update CD (contains all updates, InfoMaker, Desktop, Professional, Enterprise to go from 7.0 or 7.0.1 to 7.0.2) doesn't update PB Professional 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:215642
CR Number:   215642
Product Name:   PB Enterprise
Product Component:   UO Painter
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. User object painter is crashing in PBVM70.DLL when working with a custom visual user object "a". If you first delete one nested object "b" from "a" and then insert another custom visual user object "c" to replace "b" and "c" contains a treeview, when you try to save the object, it crashes.

NOTE: Custom Visual User Objects "b" and "c" have a common ancestor.



CR:215653
CR Number:   215653
Product Name:   PB Enterprise
Product Component:   DW Painter
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 1180 17 May 2000 Fixed
Description
Win95B/Win98 GPF in PBDWE60.DLL/PBDWE70.DLL manipulating Scale MinimumValue on Value Axis (changing it to anything but zero and trying to save). This does not happen on Win95a machines or NT 4.0.

Workaround: Export the datawindow and change the value manually and re-import.



CR:215673
CR Number:   215673
Product Name:   PB Enterprise
Product Component:   MTS Integration
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 8030 31 Oct 2002 Fixed
Description
A com object created in pb 6.5.1 (build 1173) fails
when running in MTS. The following error is given in the browser:
error 'ASP 0115'
Unexpected error
testcrash6.asp

The com object is just creating and destroying a datastore.

The problem happens when the com object is registered and installed
under IIS. Happens when the package properties "run in separate
memory space (isolated process)" is unchecked. Works ok when checked.
Workaround Description
 The problem happens when the com object is registered and installed
under IIS. Happens when the package properties "run in separate
memory space (isolated process)" is unchecked. Works ok when checked
using a single cpu.



CR:215706
CR Number:   215706
Product Name:   PB Enterprise
Product Component:   DW Printing
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
Fonts are not correctly printed (PB 6 and PB 7) for a driver called "Tharo Gemini " on windows 95
Works fine on Windows NT
Works fine on Windows NT and windows 95 when using PB V5
Workaround Description
 use True type font such as 3of9.ttf



CR:215720
CR Number:   215720
Product Name:   PB Enterprise
Product Component:   DB ODBC
Status:   Closed
OS:   Microsoft Windows 98
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
24 Apr 2001 Not a Bug
Description
This problem appears for outer join syntax using ODBC interface connection to Oracle database and NOT for PB NATIVE Oracle database connection.
"Outer join" construct is a standard method in SQL.

The PB 7.x error msg when try to preview an SQL query with an outer join is:-
[Oracle][ODBC Oracle Driver][Oracle OCI]ORA-00933: SQL command not properly ended.
Workaround Description
 Temporarily use native connection instead of ODBC for Oracle.



CR:215722
CR Number:   215722
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)
03 May 2000 Fixed
Description
Having the option 'Show Focus Rectangle' for a datawindow column object will replace the EditMask format with 'yes'. Turning the option off will change it to 'no'



CR:215753
CR Number:   215753
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)
31 Oct 2002 Presently Not Targeted For Any Future Release Of This Product
Description
6.5.1 Regression. Grid lines in grid datawindow not correct at runtime. In 6.5 444, both used "AppWrkSpace" (application workspace) color for development and runtime. In 6.5.1 and above, it uses "AppWrkSpace" in the painter but ButtonFace at runtime.



CR:215775
CR Number:   215775
Product Name:   PB Enterprise
Product Component:   DB Oracle
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11 Aug 2004 Not reproducible with latest version of the product available as of Resolution Date
Description
Problem: Oracle -Datawindow retrieval with comma decimal separator does not work if DisableBind is not set to 1.
Workaround Description
 set Disablebind = 1



CR:215781
CR Number:   215781
Product Name:   PB Enterprise
Product Component:   Script Painter
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15 Sep 2000 Fixed
Description
breakpoints set in the scriptpainters could disappears if changing code of an object
Workaround Description
 Set breakpoints in the debugger.



CR:215812
CR Number:   215812
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)
25 Feb 2004 EOL'd version. Not to be Fixed.
Description
OLE object connected to Word: oleobject.Selection.HomeKey(6) leaks memory.
Use tempory oleobject for oleobject.Selection to avoid the leak.
Workaround Description
 OLEObject lole_temp
lole_temp = iole_word.Selection // Do this once before the loop and save the reference in lole_temp
Do While NOT ib_cancel
lole_temp.HomeKey(6) // Call the function using our saved reference.
Loop



CR:215813
CR Number:   215813
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)
20 Feb 2004 EOL'd version. Not to be Fixed.
Description
Enhancement request to re-instate "reset properties" in PowerBuilder 7.x



The following should also be included in this enhancement request:

There should be the possibility to select the individual items to reset instead of a global reset.



CR:215866
CR Number:   215866
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)
16 Mar 2004 EOL'd version. Not to be Fixed.
Description
Unable to open existing Jaguar Component project object. The error is: "Unable to open this project because the add-on software was used to create it could not be found. Perhaps this project was build on anther system?"

The reason is PowerBuilder found PBVM and PBDWE on the path somewhere BUT NOT IN THE SAME DIRECTORY as PBCOM70.DLL or PBJCG70.DLL (the Jaguar component generator DLL is). This seems to be a requirement to build or look at an existing project.

- Check your system for duplicates.
- With PB running and the error message up., run listdlls > list.txt and see where it's finding PBDWE and PBVM. Rename or delete them. Set up your path so the DLLs are in the same directory.



CR:215869
CR Number:   215869
Product Name:   PB Enterprise
Product Component:   DW Edit Mask
Status:   Closed
OS:   Solaris 2.5.1
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2002 Fixed
Description
If you have an EditMask of DD/MM/YY on PowerBuilder 6.5 for Solaris. You are not able to populate the DD section of the date field until you have populated the MM section of the date field.
Workaround Description
 Populate the MM before populating DD.



CR:215884
CR Number:   215884
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
When bringing up the datawindow sort dialogue in runtime, the dialogue does not have a horizontal scrollbar. In development, this same sort dialogue has a horizontal scrollbar.

This is a problem when the table names are long with same prefix.



CR:215886
CR Number:   215886
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 Fixed
Description
Jaguar 3.5 error running a PB component. Related somewhat to CR173311. Getting "bad run time function reference." or R0094 Application terminated "corba system exception: corba_internal at line xxx calling the remote object from a client application."
CR173311 was the general pass by ref (since fixed). This has a twist in that the argument passed to jag is then again passed by reference to an External DLL.

The workaround is to have the remote function argument described as "by value".



CR:215969
CR Number:   215969
Product Name:   PB Enterprise
Product Component:   DW Edit Mask
Status:   Closed
OS:   Microsoft Windows 98
Original Version:   6.5.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.5.1 1197 29 Nov 2000 Fixed
Description
Date datatype editmask 'day' part allows values 44,55,66,77,88,99 till 'month' part evaluated
This is a problem for PB6.x only.
For PB7.x, the user entry cursor validates at the first digit position of the editmask 'dd/mm/yyyy' when numeric
keys 4 - 9 are pressed.
Workaround Description
 In Pb6.x, this behaviour is an inconvenience. The entry cursor for 'dd/mm/yyyy' does stop at the MONTH part(after validating the DAY with the MONTH value) to reject the values.



CR:215993
CR Number:   215993
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)
15 Jun 2004 EOL'd version. Not to be Fixed.
Description
If you have any text/computed field in a DataWindow footer with build 8004 of PowerBuilder 7.0.2 onwards and you try and enable the HSplitScroll property in the DataWindow control. The text/computed field will no longer be visible.



CR:215997
CR Number:   215997
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)
7.0.2 8027 26 Apr 2000 Fixed
Description
When application uses syntax to dynamically create a sorted group dw and then the syntax is retrieved through either dot notation or through a describe the resulting syntax is missing the sort information making it hard for the customer to modify the sort criteria dynamically without building the syntax anew each time.



CR:216037
CR Number:   216037
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)
7.0.2 8038 25 Feb 2004 Fixed
Description
WebDW cannot handle DateTime retrieval arguments.

The code inside the of_convert_value function does not properly handle a DateTime value.
All strings are passed in as a string containing both the date and time. The current code tries to use this string without parsing it first. Therefore, the value is dectected as an invalid date, causing a result of 01/01/1900 00:00:00.

Following is the current code, and a potential code fix.
]
Within nv_retrieval_arg of_convert_value function, here is the problem code:
case TYPE_DATETIME
date ld_date
time lt_time
ld_date = Date(as_passedValue)
lt_time = Time(as_passedValue)
aa_newValue = DateTime(ld_date, lt_time)

This will always result in aa_newValue as 01/01/1900 00:00:00, since both the Date and Time functions will detect as_passedValue as invalid. The Date function expects a string containing only a date, and the Time function expects a string containing only a time. Therefore, there needs to be logic to parse the as_passedValue string, to extract out the date and time portions seperatly.

WORKAROUND:
Here is new code to fix the problem:

case TYPE_DATETIME

date ld_date
time lt_time
string ls_date, ls_time
char c[]

// convert he passed string into a character array
c = as_passedvalue

// parse characters to extract date, until find a space
integer li_ndx = 1
DO WHILE ( li_ndx <= 10 )
if c[li_ndx] = " " then exit
ls_date+= string(c[li_ndx])
li_ndx++
LOOP

// parse rest of characters to extract time
integer li_length = 1
li_ndx++
DO WHILE ( li_length <= 8 )
ls_time+= string(c[li_ndx])
li_ndx++
li_length++
LOOP

// use the extracted date and time strings to create a DateTime value
ld_date = Date(ls_date)
lt_time = Time(ls_time)
aa_newValue = DateTime(ld_date, lt_time)
Workaround Description
 The only workaround is to create a custom WebDW component and put in the suggested fix, then use the custom component instead of the WebDW.



CR:216095
CR Number:   216095
Product Name:   PB Enterprise
Product Component:   DW Wizards
Status:   Closed
OS:   Microsoft Windows 98
Original Version:   7.x Catalina
Fixed Version Build Resolution Date Closure Code (If Appropriate)
25 Feb 2004 EOL'd version. Not to be Fixed.
Description
This is a problem for PB7.x .
PB6.x is stable.
PB produces an application error (gpf's) for this circumstance :-
=====================================================
Create new crosstab dw wizard {Manipulating number of columns in the "column" OR "rows" part of the crosstab definition is unstable.}



CR:216105
CR Number:   216105
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 9001 06 Jul 2000 Fixed
Description
Spin control icon overlaying data at smaller editmask heights.
Verified fixed in 7.0.2 build 9023.
Workaround Description
 Make the editmask height larger if you can.



CR:216115
CR Number:   216115
Product Name:   PB Enterprise
Product Component:   DW Painter
Status:   Closed
OS:   Microsoft Windows 98
Original Version:   7.0.3
Fixed Version Build Resolution Date Closure Code (If Appropriate)
07 Aug 2000 Fixed
Description
In the DW painter:
The problem is that the graph dw properties, tabpage "Axis" does not redisplay the "sort" property
and it's attribute value after a change has been made.
However if the dw object is saved and closed, then re-opened in the painter, the "sort" property is viewable and enabled.

This is a regression problem for post PB7.02MR ;
PB6.x and pre-release PB8.x do not exhibit this problem.
Workaround Description
 Make the change to the "sort" property attribute. Close and save the dw object and re-open. Tabpage "Axis" displays "sort" property.



CR:216182
CR Number:   216182
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)
07 Aug 2000 Fixed
Description
phonenumber style editmask not working. Mask (###) ###-#### cursor can be placed before parentheses. First character is dropped when typing from this position.



CR:216196
CR Number:   216196
Product Name:   PB Enterprise
Product Component:   DW Painter
Status:   Closed
OS:   Microsoft Windows 98
Original Version:   7.0.3
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15 Jun 2004 EOL'd version. Not to be Fixed.
Description
In the DW painter:
The problem is that PB gets an application error when tabpage focus is changed and "Axis" tabpage properties toggled. These are the following steps to reproduce the error.

a)Connect to EASDemo db
b)Create New -> Graph -> SQL Select -> Next.
c)From table "employee", select columns emp_lname, state
d)Set category to be "state"
e)Set value to be "count(emp_lname for graph)". Save dw.
f)Select dw properties, choose tabpage "Axis"
g)Change "Axis" property to "category" (ddlb)

h)Change "sort" property to a different choice from the existing one- unsorted/ascending/descending
i)Change focus to a different tabpage.
j)Return/change focus to "Axis"
k)Change "axis" property to "Value" instead of "Category"
GPF in module PBVM70.dll ;



CR:216198
CR Number:   216198
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)
25 Feb 2004 EOL'd version. Not to be Fixed.
Description
A PowerBuilder-Built COM object works fine called from a PowerBuilder client crashes (Exceptions) out at RtlSizeHeap( b60000, 1090020 ) when running the Visual C++ 6.0 client executable calling the same PowerBuilder COM object. The VC++ application then crashes with a box "OleMainThreadWndName: Comtest.exe - Application error. The instruction at 0x00b49ca1 referenced memory at 0x00000008 could not be read. Click OK to terminate the application..



CR:216218
CR Number:   216218
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)
25 Feb 2004 EOL'd version. Not to be Fixed.
Description
An array element as a reference variable used to access an nvo constant, fails.



CR:216277
CR Number:   216277
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)
02 May 2000 Fixed
Description
7.0 Regression. MinimumValue/MaximumValue on value axis of a graph datawindow (or graph object on a datawindow) is limited to 65535. Follow on from CR215653. There was a 2 billion limit to these spin controls for the value axis in 6.5



CR:216279
CR Number:   216279
Product Name:   PB Enterprise
Product Component:   Help
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   7.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15 Aug 2000 Fixed
Description
Documentation Issue: Online Help: PWDialog for Oracle is not listed as a valid dbParm.



CR:216293
CR Number:   216293
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
An html dw page shows different results in the browser
than what's in dwmine.context after a priorpage,nextpage,pagefirst,pagelast
thru javascript.

From the html page if you insert 2 empty rows and then populate the columns
except the primary key column and then hit the prior page button, the page
refreshes but the last row inserted is empty. If all columns are populated
(including the primary key) and then hit prior page than all the data is retained
in the html page.



CR:216303
CR Number:   216303
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)
7.0.3 10045 25 Feb 2004 Fixed
Description
Can't save a userobject with a user event that references an array argument.



CR:216447
CR Number:   216447
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 8028 05 Jun 2000 Fixed
Description
7.0 Regression. Crosstab and Graph datawindow types do not allow the user to complete the datawindow when using retrieval arguments AND SYNTAX MODE when creating a NEW datawindow. This worked fine in 6.5 and you got the crosstab definition dialog. When using retrieval arguments and SYNTAX MODE, the 7.0 wizard page equivalent of the crosstab or graph definition dialog has no data in it.

This "Syntax mode" is often required on complex SQL that can't be painted and might be pasted in from another datawindow where the user wants a Crosstab presentation of the same select shown already in, say, a tabular.

The workaround to perhaps use a real number or value (the dept_id = 100 below):
select dept_id,etc, etc from department where dept_id = 100

and going back to add the retrieval argument later doesn't work either since 7.0.2 8025 now GPFs in PBDWP70.DLL at the last stage (after the "Define Crosstab Rows, Columns, Values" wizard page while actually creating the crosstab.) This means you can't create a crosstab in syntax mode even if it doesn't use a retrieval argument.



CR:216460
CR Number:   216460
Product Name:   PB Enterprise
Product Component:   MAPI
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 - MAPI - Add the ability to read messages from folders other than the inbox.



CR:216528
CR Number:   216528
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)
17 Nov 2000 Fixed
Description
If GetFullState is used with a datawindow or datastore which contains a nested dw with more than 20 args PB crashes. Reproduced in PB 6, 7 and 8.
With 7.02.8025 it crashes PBVM at 015f:113ec066
Same code with a composite dw will also crash
Same code with 20 or less args also works OK.
Workaround Description
 Reorganise dw nesting to avoid having a nested dw requiring so many args.



CR:216529
CR Number:   216529
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 May 2000 Duplicate
Description
if you create a composite dw and you add a nested report with not used retrieval arguments or if you add later a new retrieval argument, the dw painter causes gpf if you click on nested report to view the properties. This could be similar to CR 213152 & CR 209335.

Workaround:
- After adding the new retrieval argument to the nested report export the composite datawindow
- edit the exportfile of the composite datawindow and delete the retrievalarguments - for example:
a) nest_arguments=((" id ")) in a row starting with "report".
b) delete -> nest_arguments=((" id "))
c) save the exported report
- import the composite dw into PB again
- reassign the retrieval arguments in the composite dw



CR:216535
CR Number:   216535
Product Name:   PB Enterprise
Product Component:   DW DDDW
Status:   Open
OS:   MS Windows NT 4.0
Original Version:   7.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
For a background to this problem see CRs 148750, 154422, 193974 and 207244 (very closely related to this case).

When a datawindow column has a dddw associated with a date column AND the 'allow edit' property is checked
the following behaviour occurs:

If the date entered corresponds to a date in the dddw list of values everything works fine.
If the date does NOT correspond to a date in the dddw list one of the following will occur:

When 'always show arrow' selected - the date appears in format yyyy-mm-dd when the column has focus and also when focus moves to another column (this is CR 207244)

When 'always show arrow' selected - the date appears in format yyyy-mm-dd ONLY when the column has focus then it returns to the system shortdate.

Other CRs for this problem have concentrated on trying to make it possible to specify an edit mask for a dddw
This CR is being created to ask for that hardcoded date format of yyyy-mm-dd be changed to either the system shortdate or is made configurable in some way (ie in pb.ini/registry or a checkbox for the dddw properties).



CR:216619
CR Number:   216619
Product Name:   PB Enterprise
Product Component:   DW DDDW
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
When a datawindow is in query mode, columns of edit style dropdowndatawindow do not collapse when you click on other columns in the dw ONLY IF THE UPPER case conversion is set on.
PB 6.x only : Then, if you choose an item of the DDDW, it fires a gpf



CR:216630
CR Number:   216630
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 22 May 2000 Fixed
Description
7.02 Regression

Cut and paste from one string field in a datawindow into another. If only part of the string is selected, the copy and paste will still take the entire field instead of only the part selected. Problem is with the copy/clipboard functions



CR:216631
CR Number:   216631
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
Memory leaks using datawindow dot notation. Workaround is to use dw.Describe.
Workaround Description
 Workaround is to use dw.Describe.



CR:216640
CR Number:   216640
Product Name:   PB Enterprise
Product Component:   DW SaveAs
Status:   Closed
OS:   MS Windows NT 4.0
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
6.5.1 1195 09 Jun 2000 Fixed
Description
6.0/6.5 Regression. PSR file generation -SaveAs(PSReport!) - spins PB 6.5 with no output and gives "out of memory" message in 7.0 and crashes when table has around 300,000 rows. In some cases, depending on your configuration, this can happen with a fewer number of rows (75000). A small PSR file will be created (maybe 40-80k bytes) and the system just keeps spinning and using up Virtual Memory. In 5.0, the file saved very quickly (15-20 seconds) - you could hear the disk writing - and there was no use of virtual memory.

There is another similar 'out of memory' problem 6.0 in
CR211553-6.0 Regression. Large retrievals and/or imports into datawindow result in 'Out of Memory'. These two bugs are not directly related.

Fixed in 6.5 builds > 1195 and in 7.0.2 ebf builds > 8033.



CR:216725
CR Number:   216725
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)
15 Jun 2004 EOL'd version. Not to be Fixed.
Description
7.0 Regression. Datetime or time editmask shows 'tt' in mask (part of the control panel regional settings for time mask) when it shouldn't. This happens in the datawindow and window editmask when using
[time] or [date][time], the defaults..

Notice the Control Panel Regional Settings for Time are 'hh:mm:ss tt'

Workaround: In 7.0,
Datetime columns: Change the editmask from [date][time] to
mm/dd/yyyy hh:mm:ss AM/PM

Time columns: Change [time] editmask to 'hh:mm:ss AM/PM'



CR:216812
CR Number:   216812
Product Name:   PB Enterprise
Product Component:   Font
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
Desc-
The problem is that the fontcharset does not get translated correctly for some
text entry properties.
This CR is concerned with the East European Charset (CE) and Polish(214) keyboard setting.
The incorrect conversions display as upside-down question mark symbol and
small subscript numbers(see htm source code file below for wrong character
interpretation)
Workaround Description
 Keyboard layout is = Polish (214), change regional settings to Polish instead of current country setting e.g. english. Tick the "Set as default" checkbox. Will be prompted to copy a file called c_852.nls from WInNT installation disk.
Reboot.



CR:216819
CR Number:   216819
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.2 11 May 2000 Fixed
Description
A memory leak occurs with the use of dot notation while parsing through the rows in the DW. The rows have to be NULL and if the datatype of the column is time related i.e. time, timestamp, date and datetime.

There is no problem if the value in the column is NOT NULL.

The following section of code is used to demonstrate the memory leak:

ll_rows = dw_1.rowcount()
do while ll_counter <= ll_rows
dw_1.object.test_timestamp[ll_counter]
loop



CR:216847
CR Number:   216847
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)
02 Oct 2000 Fixed
Description
Jaguar server crashes with the following error in the
jaguar server console:
SmartHeap error handler recursively re-entered
Abort, Ignore?

Problem happens using a date field and then doing a insert and update. Problem
happens using jds and o84 driver.





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

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

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

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

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

各种误操作:

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

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

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


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

Sybase ASE数据库恢复工具READSYBDEVICE:

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

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

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

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

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


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

SQL Server数据库恢复工具SQLRescue:

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

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

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

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

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

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

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