Switch to standard view 
  Sybase logo
 
 
 



Document ID: DC00047-01-0150-01

Topic

Page

1. Accessing current release bulletin information

2. Product summary

2.1 Third-party software

3. Special installation instructions

4. Changed functionality in this version

4.1 WebDataWindowControl for Web form applications

4.2 Access to DataWindow object properties

4.3 New properties

4.4 New GetDataWindowObjectEntries utility method

4.5 Ink controls for the DataWindowControl

4.6 SQLConnection for ADO.NET connections

4.7 Oracle 10g database interface

4.8 Event handlers and triggers in the Database painter

4.9 Support for GNU Ghostscript 8.x

5. Known problems

5.1 DataWindow .NET issues

5.2 DataWindow issues

5.3 Web DataWindow issues

5.4 Database connectivity issues

6. Product compatibilities

7. Documentation updates and clarifications

7.1 Microsoft files required for deployment

8. Technical support

9. Other sources of information

9.1 Sybase certifications on the Web

9.2 Sybase EBFs and software maintenance

1. 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 release of the product CD, use the Sybase Technical Library Product Manuals Web site.

Accessing release bulletins at the Technical Library Product Manuals Web site

  1. Go to Product Manuals.

  2. Follow the links to the appropriate Sybase product.

  3. Select the Release Bulletins link.

  4. Select the Sybase product version from the Release Bulletins list.

  5. From the list of individual documents, select the link to the release bulletin for your platform. You can either download the PDF version or browse the document online.


2. Product summary

This product is Sybase DataWindow .NET™ version 1.5, which is compatible with the following platform and operating system configurations:

2.1 Third-party software

For third-party software licenses that apply to this product, see the Getting Started CD in your DataWindow .NET 1.5 software package.

3. Special installation instructions

The Installation Guide on the Getting Started CD describes how to install the software.

4. Changed functionality in this version

The New Features section of the DataWindow .NET compiled HTML Help file (dwnet10.chm) describes changes in this release. This Help is installed in your DataWindow .NET 1.5\help directory.

The following sections summarize changes in DataWindow .NET 1.5.

4.1 WebDataWindowControl for Web form applications

The DataWindow .NET WebDataWindowControl is a custom Web server control that inherits from the System.Web.UI.WebControls.WebControl class.

You can use a WebDataWindowControl in a Web Form in an ASP.NET Web application in much the same way that you use a DataWindowControl in a form in a Windows application in .NET. The WebDataWindowControl can render a DataWindow object and its data as a Web DataWindow in HTML, XHTML, or XML and display it in an ASP.NET (.aspx) page in a browser.

4.1.1 About the Web DataWindow

The Web DataWindow is a DataWindow that is generated for use in Web applications. The Web DataWindow offers a thin-client solution that provides most of the data manipulation, presentation, and coding capabilities of the DataWindow without requiring any DLLs on the Web client. The DataWindow that displays in the Web browser looks very much like the DataWindow you designed in the DataWindow painter.

The Web DataWindow supports the same DataWindow presentation styles as the DataWindow in Windows forms. Graphs can be displayed in a DataWindow in a stand-alone image file or in an image stream embedded into the Web page.

Features include:

For more information, see the DataWindow .NET Programmer’s Guide.

4.1.2 About the WebDataWindowControl

To use the Web DataWindow in an ASP.NET Web forms application, drag a WebDataWindowControl from the Toolbox to a Web form.

The WebDataWindowControl class is defined in the Sybase.DataWindow.Web namespace and is delivered in the WebDataWindow.dll file. The class extends the .NET System.Web.UI.WebControls.WebControl class. It implements the IPostBackEventHandler and IPostBackDataHandler interfaces to handle client-side postbacks, and the IDataStore interface to enable ShareData, RowsCopy, and RowsMove methods to be called between the WebDataWindowControl and DataStore.

Internally, the WebDataWindowControl uses an instance of the DataStore class to expose methods and properties and render the DataWindow in the selected rendering format.

4.2 Access to DataWindow object properties

Version 1.5 of DataWindow .NET introduces a change in how some DataWindow object properties are accessed.

4.2.1 Expression-based properties

Properties that use expressions can be accessed using a descendant of the ExpressionBasedProperty class. Each property object has two properties: Value returns a System.Drawing.Color and Expression returns a String.

A System.Drawing.Color ValueInRow ( Int32 rowNumber ) method has also been added. This method returns the value of a property for a column in a particular row.

This change requires minor changes in your code. For example, the following code accesses the TextColor property in Version 1.0:

GraphicObjectEditableColumn gobColumn;
System.Drawing.Color C;
String expr;

C = gobColumn.TextColor;
expr = gobColumn.TextColorExpression;

gobColumn.TextColor = System.Drawing.Color.Aqua;
gobColumn.TextColorExpression = expr;

The following code accesses the TextColor property in Version 1.5 and shows the new ValueInRow method:

GraphicObjectEditableColumn gobColumn;
Int32 someRow;
System.Drawing.Color C;
String expr;

C = gobColumn.TextColor.Value;
expr = gobColumn.TextColor.Expression;
C = gobColumn.TextColor.ValueInRow ( someRow );

gobColumn.TextColor.Value = System.Drawing.Color.Aqua;
gobColumn.TextColor.Expression = expr;

These changes apply to all DataWindow object properties that can be set using an expression.

4.2.2 Properties with subproperties

For properties that use multiple “dots,” new property objects are instantiated when they are needed.

4.2.3 PrintProperties class

The PrintProperties class encapsulates DataWindow and DataStore print properties, and the corresponding PrintProperties property returns the properties. For example, the following code sets the Collate print property to true:

dwEmp.PrintProperties.Collate = true;

See the description of the PrintProperties class in the online Help in Visual Studio .NET for a complete list of properties.

4.2.4 Edit styles

The classes in the following table encapsulate the edit style properties of the GraphicObjectEditableColumnObject.

Class and property

Edit style

CheckBox

CheckBox

DDDW

DropDownDW

DDLB

DropDownListBox

SimpleEdit

Edit

EditMask

EditMask

InkEdit

InkEdit

RadioButton

RadioButtons

4.3 New properties

The following properties have been added to DataWindowControl, DataStore, and DataWindowChild: ColumnCount, PrintProperties, and Syntax.

The following properties have been added to DataWindowControl: BackgroundColor, QueryMode, FirstRowOnPage, and LastRowOnPage.

For more information, see the Sybase DataWindow help in Visual Studio .NET.

4.4 New GetDataWindowObjectEntries utility method

The GetDataWindowObjectEntries method in the Utility class lists the DataWindow objects present in a given PBL or PBD. The method takes a library name as an argument and returns an array of DataWindowObjectEntry objects, each of which holds the name of a DataWindow object as well as its last-modified date and comments. This feature is available in Windows form and Web form applications.

4.5 Ink controls for the DataWindowControl

You can use an InkEdit edit style for columns and you can insert an InkPicture control into a DataWindow. These features are designed for use on a Tablet PC. They are not supported in Web DataWindows.

4.6 SQLConnection for ADO.NET connections

In DataWindow .NET 1.0 you could establish an ADO.NET connection to a database using the .NET Framework DataProvider for OLE DB. In DataWindow .NET 1.5, you can connect to Microsoft SQL Server 7.0 or later using the .NET Data Provider for SQL Server. The OLE DB data provider uses an OleDbConnection object to connect to the database. The SQL Server provider uses a SqlConnection object.

4.7 Oracle 10g database interface

The Oracle 10g database interface allows you to connect to Oracle 10g servers using Oracle 10g Database Client or Oracle 10g Instant Client. It supports BINARY_FLOAT and BINARY_DOUBLE datatypes and increased size limits for CLOB and NCLOB datatypes. Oracle 10g clients can connect to Oracle9i or Oracle 10g servers. They cannot connect to Oracle8i or earlier servers.

4.8 Event handlers and triggers in the Database painter

When you expand an Adaptive Server® Anywhere (ASA) database profile in the Objects view in the Database painter, an Events folder displays at the top level. Expanding the folder displays any event handlers defined for the database. Expanding a table in an ASA or Adaptive Server® Enterprise profile in the Objects view displays a Triggers folder.

4.9 Support for GNU Ghostscript 8.x

DataWindow .NET now supports GNU Ghostscript 8.x. PDF creation has been tested with versions 8.00 and 8.14. You can download the self-extracting executable file for the version of Ghostscript you want from one of the sites listed on the Ghostscript Web site.

5. Known problems

5.1 DataWindow .NET issues

5.1.1 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]

5.1.2 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]

5.2 DataWindow issues

5.2.1 Save As PDF fails on Windows 2003 Server

Saving as PDF fails at runtime on Windows 2003 Server. This is caused by a Group Policy that by default disallows installation of printers that use kernel-mode drivers. Kernel-mode drivers have access to system-wide memory, and poorly written drivers can cause system failures. To allow installation of kernel-mode drivers, follow these steps:

  1. Select Run from the Windows Start menu.

  2. In the Open box, type gpedit.msc and click OK.

  3. In the Group Policy console, expand Computer Configuration, Administrative Templates, and Printers.

  4. Disable “Disallow Installation of Printers Using Kernel-Mode Drivers.”

[CR 349868]

5.2.2 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]

5.3 Web DataWindow issues

5.3.1 Page error when page scripting language set to VBScript

If the scripting language of an .aspx page is set to VBScript, the JavaScript inserted when a client event handler is generated from the Properties window causes an “Invalid character” page error. VBScript and JavaScript can coexist on the page as long as the default scripting language is not set to VBScript. [CR 376258]

5.3.2 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]

5.3.3 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]

5.3.4 Drop-down calendar edit mask style does not work in some browsers

The drop-down calendar EditMask edit style format renders correctly in Internet Explorer, but does not display in Netscape and Mozilla browsers. [CR 383968]

5.4 Database connectivity issues

5.4.1 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:

[CR 334166]

5.4.2 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]

5.4.3 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 an MSS2000 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]

5.4.4 OraOleDB faster than Oracle8ADOProvider

When you use an OLE DB connection to an Oracle9idatabase, the Table list or View list displays more quickly in the Database painter if you use OraOleDB instead of the Oracle8ADOProvider. [CR 341835]

5.4.5 Connection issues with CnnPool

In the Database painter, attempting to connect to an Oracle9i or Oracle 10g database from an Oracle9i or Oracle 10g client fails after a connect and disconnect if the CnnPool database parameter is set to ‘Yes’. [CR 355639]

6. Product compatibilities

This product is compatible with development environments that support the Microsoft .NET Framework Version 1.1. It has been tested with Microsoft Visual Studio .NET 2003.

Microsoft .NET Framework Version 1.1 is required for deployment.

Microsoft Internet Information Services (IIS) 5.0 or later is required for Web DataWindow development and on the Web server.

7. Documentation updates and clarifications

The online Help delivered with DataWindow .NET has been updated to describe the new features and changes in functionality described in “4. Changed functionality in this version”.

The following books have been updated on the DataWindow .NET documentation page: Programmer’s Guide, DataWindow Object Reference.

7.1 Microsoft files required for deployment

The following table lists Microsoft files required for deployment.

Table 1: Microsoft runtime files

File name

When required

msvcr71.dll, msvcp71.dll

With all applications. The pbshr100.dll required file has dependencies on these Microsoft Visual C++ runtime libraries. These files are part of the Microsoft .NET Framework 1.1, which is required for all deployed .NET applications.

atl71.dll

With all applications. The pbdwn100.dll file has dependencies on this file, which is the Microsoft .NET Active Template Library module.

gdiplus.dll

If you deploy your application to the Windows 2000 platform. This file is installed as part of the operating system for Windows XP and Windows Server 2003 and is part of the Microsoft GDI+ subsystem that implements enhanced graphics capabilities.

The Microsoft GDI+ module can be downloaded from the Microsoft Downloads Web site. You can deploy the msvcr71.dll, msvcp71.dll, and atl71.dll from your DataWindow .NET installation to target systems in the same way you deploy DataWindow .NET unmanaged DLLs.

For more information about deploying unmanaged DLLs, see the chapter on deployment in the DataWindow .NET Programmer’s Guide.

For information about restrictions on redistributing Microsoft DLLs, see the third party terms for DataWindow .NET.

8. Technical support

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.

9. Other sources of information

Use the Sybase Getting Started CD, the Sybase Technical Library CD, and the Technical Library Product Manuals Web site to learn more about your product:

9.1 Sybase certifications on the Web

Technical documentation at the Sybase Web site is updated frequently.

Finding the latest information on product certifications

  1. Point your Web browser to Technical Documents.

  2. Select Products from the navigation bar on the left.

  3. Select a product name from the product list and click Go.

  4. Select the Certification Report filter, specify a time frame, and click Go.

  5. Click a Certification Report title to display the report.


Creating a personalized view of the Sybase Web site (including support pages)

Set up a MySybase profile. MySybase is a free service that allows you to create a personalized view of Sybase Web pages.

  1. Point your Web browser to Technical Documents.

  2. Click MySybase and create a MySybase profile.


9.2 Sybase EBFs and software maintenance

Finding the latest information on EBFs and software maintenance

  1. Point your Web browser to the Sybase Support Page.

  2. Select EBFs/Maintenance. Enter user name and password information, if prompted (for existing Web accounts) or create a new account (a free service).

  3. Select a product.

  4. Specify a time frame and click Go.

  5. Click the Info icon to display the EBF/Maintenance report, or click the product description to download the software.




Back to Top
© Copyright 2010, Sybase Inc.