Release Bulletin DataWindow .NET™ 2.0.1
Document ID: DC00047-01-0201-01
Last revised: November 10, 2006
Accessing current release bulletin information
A more recent version of this release bulletin may be available on the Web. To check for critical product or document information added after the product release, use the Sybase Product Manuals Web site.Accessing release bulletins at the Sybase Product Manuals Web site
This product is Sybase DataWindow .NET™ version 2.0.1, which is compatible with the following platform and operating system configurations:
For third-party software licenses that apply to this product, see the Getting Started CD in your DataWindow .NET 2.0 software package.
Special installation instructions
Before you install
Before you install this release, shut down any applications running on your system. Restart your system after all the installations are complete. The executable files in this release extract setup files to the folder specified by your TMP environment variable, or the folder specified by your TEMP environment variable if TMP is not defined or specifies a directory that does not exist. Make sure you have enough disk space on the drive containing this folder before beginning the installation.
To specify an alternative location, open the System Properties dialog box from the Windows Control Panel, select the TMP user variable (or TEMP if TMP does not exist) on the Environment or Advanced tab page, and specify a location that has sufficient space.
Installing DataWindow .NET
You can download DataWindow .NET 2.0.1 from the PowerBuilder page of the Sybase EBFs/Maintenance site. Download the files you require and extract the contents of the zip files following the instructions in the download notes that accompany the release.
To install DataWindow .NET 2.0.1, you must have already installed DataWindow .NET version 2.0 on your computer.To update DataWindow .NET:
Changed functionality in this version
New Features in DataWindow .NET 2.0 describes features added in DataWindow .NET 2.0. You can view this book on the Sybase Product Manuals Web site. Select DataWindow .NET from the list of products and click Go, then select DataWindow .NET 2.0 and select this title.
The features listed in the following sections have been added in DataWindow .NET 2.0.1.
Showing button background color on XP
When you change the background color of a button in a DataWindow on the XP operating system, the change does not display by default in the Preview view or when you run the application, because the XP theme typically controls the background color of buttons.
To display the change in Preview mode, set the ShowBackColorOnXP property
[Data Window] ShowBackColorOnXP=1
To display the change at runtime, add the following statement to code that runs before the DataWindow is displayed:
dw_1.Modify("DataWindow.ShowBackColorOnXP = yes")
This change is also available in DataWindow .NET 2.0 EBF Build 5063 and 1.5.1 EBF Build 9671 and later builds.
Adaptive Server Enterprise 15 support
A new interface (ASE) has been added for connections to Adaptive Server® Enterprise. The ASE interface is identical to the SYC interface with two exceptions: the ASE interface supports only Adaptive Server 15 and later releases and includes support for large identifier names not available in the SYC interface. The ASE driver supports column names with up to 128 characters.
Unsigned datatype support for ASE 15
Support for three unsigned datatypes, UnsignedBigInt, UnsignedInt, and UnsignedSmallInt, introduced in Adaptive Server 15, was included in the SYC and JDBC drivers for DataWindow .NET 2.0. It is available for the ODBC and ASE drivers in DataWindow .NET 2.0.1.
ServerCursor database parameter
When you use the OLE DB database interface with a Microsoft SQL Server database and retrieve data into a DataWindow, server-side cursors are used to support multiple command execution. If this has a negative impact on performance, try increasing the size of the Block database parameter to 500 or more, or adding the following line to the [Microsoft SQL Server] section in the PBODB105.INI file to turn off server-side cursors:
ServerCursor = 'NO'
The ServerCursor parameter can be used only in the PBODB initialization file.
DataWindow .NET issues
GetFullState and SetFullState cause OutOfMemoryException
When used with a large volume of data in a distributed (.NET remoting) application, the GetFullState and SetFullState methods consume excessive memory and an OutOfMemoryException is thrown. The same technique in a client/server application works correctly. [CR 360283]
ADO.NET driver does not support Oracle stored procedures
The DataWindow .NET ADO.NET database driver cannot retrieve a DataWindow built using an Oracle stored procedure as its data source. It reports the following error: “SqlDbCode = 999. SqlErrText = Select error: Requested result set not found.” The same DataWindow can be retrieved successfully using the DataWindow .NET Transaction object. [CR 347692]
DataWindow blobs do not support Web services
The DataWindowFullState and DataWindowChanges classes cannot be used in a Web service because some of their members are internal or protected and therefore cannot be serialized using XML serialization. [CR 404157]
AutoSize Height issues with header band
When two reports are included one above the other in the header band of a DataWindow object and the AutoSize.Height property is set to true for the header band and false for the detail band, the DataWindow displays incorrectly in preview. The lower report overlaps the upper report. The report displays correctly if the Autosize.Height property is set to true in both the header and detail bands.[CR 405033]
Limitations in default PostScript drivers
The PostScript drivers installed with DataWindow .NET do not support searching the generated PDF file, and when a DataWindow object has more columns than fit on a single page, so that data is wrapped to a new page in the PDF file, sometimes the last column on each page is clipped. The workaround is to use an alternative driver. See the Installation Guide for how to install and use an alternative driver. [CR 324579, CR 332365]
DropDownListBox displays incorrect value with a shared DataWindow
In an application with two DataWindowControls, one DataWindow is shared with a DataStore and the value for the second is set using GetChanges and SetChanges in a round trip to the server in the ItemChanged event. Selecting an item in a DropDownListBox in the second DataWindow displays an incorrect value. [CR 421580]
Web DataWindow issues
Page error when page scripting language set to VBScript
ResetUpdateStatus in external Web DataWindow
When a DataWindow has been retrieved from a database, calling ResetUpdateStatus after InsertRow resets the client context and no row is inserted on the client. This is expected behavior. However, when a DataWindow has been created using DataWindowSyntaxFromSql, the client context is not reset and a row is inserted on the client. If you make another change before calling ResetUpdateStatus, such as calling SetItem, the client context is reset and no row is inserted. [CR 380438]
Web DataWindow Retrieve fails with retrieval arguments
When there are retrieval arguments, the Web DataWindow client-side Retrieve method returns -1 and fails to retrieve data. [CR 382988]
Incorrect rendering after client-side insert, append, or delete
In an N-Up Web DataWindow using the XML RenderFormat and XmlClientSide PagingMethod, some items in the detail band, such as a computed field or text, are rendered in the wrong position after a client-side insert, append, or delete row. Newly inserted or appended rows are not rendered correctly. These actions are not supported on the client side in N-Up Web DataWindows. [CR 423620]
Sort from column header fails if column is linked
In a Grid Web DataWindow, clicking a column header to sort by that column fails if the column has an HTML link. [CR 442523]
Groupbox rendered on top of Rectangle in XML Web DataWindow
If a Rectangle control is placed on top of a Groupbox control in the DataWindow painter, the Groupbox displays on top of the Rectangle at runtime when the Web DataWindow uses the XML RenderFormat. The Rectangle displays on top with the XHTML and HTML RenderFormats. [CR 422749]
Groupbox and Rectangle not rendered in Graph XML Web DataWindow
In a Graph Web DataWindow using the XML RenderFormat and XmlClientSide PagingMethod, Groupbox and Rectangle controls are not rendered if they are in the foreground layer. [CR 422757]
Database connectivity issues
Window is a reserved word in ASA
In ASA 9, the word “window” is a reserved word. As a result, SELECT statements on a column with the name window do not work correctly. There are several ways to work around this issue:
Alter table limitations with OLE DB and Microsoft SQL Server
When you connect using OLE DB and change the name or width of a column in a Microsoft SQL Server 2000 database using Alter Table in the Database painter in DataWindow Designer, the column is moved to the end of the table and all its data is lost. To prevent this from occurring, DataWindow Designer does not allow you to alter a table's column name and column size. You can alter the table outside the painter using ISQL scripts. [CR 348581]
Informix interface does not work with UTF-8
The IN9 Informix database interface cannot update and retrieve data when the Informix server uses the UTF-8 character set. The interface works correctly with ANSI and DBCS. [CR 349535]
Microsecond portion of Adaptive Server times not retrieved
When you use the OLE DB interface to connect to an Adaptive Server Enterprise database and select a column with the DateTime or Time datatype, the microsecond portion of the time value is not retrieved. When you use the ODBC and JDBC interfaces, the microsecond portion of a DateTime column value is retrieved correctly, but the microsecond portion of a Time column value is not. [CR 399257]
This product is compatible with development environments that support the Microsoft .NET Framework Version 2.0. It has been tested with Microsoft Visual Studio .NET 2005 Professional and Standard editions. DataWindow .NET 2.0 has not been fully tested with Visual Studio .NET 2005 Express editions and they are currently not supported.
Microsoft .NET Framework Version 2.0 is required for deployment.
Microsoft Internet Information Services (IIS) 5.0 or later and ASP.NET 2.0 or later are required for Web DataWindow development and on the Web server.
The ability to save DataWindow objects in PDF files has been tested with AFPL Ghostscript 8.53.
Each Sybase installation that has purchased a support contract has one or more designated people who are authorized to contact Sybase Technical Support. If you have any questions about this installation or if you need assistance during the installation process, ask the designated person to contact Sybase Technical Support or the Sybase subsidiary in your area.
Other sources of information
Use the Sybase Getting Started CD, the SyBooks CD, and the Sybase Product Manuals Web site to learn more about your product:
Sybase certifications on the Web
Technical documentation at the Sybase Web site is updated frequently.Finding the latest information on product certifications
Set up a MySybase profile. MySybase is a free service that allows you to create a personalized view of Sybase Web pages.
Sybase EBFs and software maintenanceFinding the latest information on EBFs and software maintenance