Switch to standard view 
  Sybase logo
 
 
 



Topic

Page

1. Accessing current release bulletin information

2. Product summary

2.1 Third-party software

3. Special installation instructions

3.1 Before you install

3.2 Installing DataWindow .NET

4. Changed functionality in this version

4.1 DataWindowControl creation

4.2 Adaptive Server Enterprise 15.0 support

4.3 Support for Sybase Adaptive Server temporary tables

4.4 NCharBind database parameter for Oracle

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

7.2 Xerces 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.1, 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

3.1 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.

3.2 Installing DataWindow .NET

You can download DataWindow .NET 1.5.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 1.5.1, you must have already installed DataWindow .NET version 1.5 on your computer.

To update DataWindow .NET:

  1. Create a backup by copying the contents of your DataWindow .NET 1.5, DataWindow Designer 1.5, and DataWindow Reference 1.5 directories to another directory.

  2. Run the setup.exe file in the directory extracted from the DataWindow.NET.zip file.


4. Changed functionality in this version

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

The following sections summarize changes in DataWindow .NET 1.5.1:

4.1 DataWindowControl creation

A change has been made in the timing of when a DataWindowControl is fully created that affects all builds after DataWindow .NET 1.5 GA. This change might require modifications to your code if

DataWindow .NET can fully create simple controls, such as Button and Label controls, in a form’s Constructor event. The DataWindowControl has more complex properties. Previously, DataWindow .NET created the control each time the user modified a property, and this resulted in slower performance. DataWindow .NET 1.5 now requires the user to complete most modifications to the properties before the control is created.

If you create the DataWindowControl dynamically, you create a new instance using the New operator and assign values to the control’s properties. You must then call the CreateControl method explicitly to fully create the control before you call the SetTransaction or Retrieve methods.

If you create the DataWindowControl by dragging it from the Toolbox to a form, the control is not fully created until the Load event for the form is fired. The DataWindowControl’s CreateControl method is called in the background when the Load event fires. This means that you can call SetTransaction or Retrieve from the Load event, but you cannot call them from the Constructor event unless you explicitly call the CreateControl method first.

4.2 Adaptive Server Enterprise 15.0 support

You can use the native interface for Adaptive Server® Enterprise (pbsyc100.dll) with Adaptive Server version 15.0. It has been enhanced to support the UniText and 64-bit integer (BigInt) SQL datatypes.

To use Adaptive Server 15, install Open Client version 15.0 on the client computer and set the Release parameter to 15 to establish an Open Client 15 client context . You can specify the Release parameter on the Connection page of the Database Profile Setup dialog box for Adaptive Server or in code:

SQLCA.DBParm="Release='15'"

You can use the Open Client 15.0 client context with Adaptive Server 11.x, 12.x, and 15.0.

The SYC driver dynamically links to the appropriate version of the client libraries, and the Open Client context is released when all connections are closed. If you open multiple connections, the first Open Client context established is used for all connections. To establish a new Open Client context in the development environment, close all open connections and establish a new connection with the Release parameter set to the context you require.

4.3 Support for Sybase Adaptive Server temporary tables

DataWindow .NET 1.5.1 allows you to create and edit temporary tables when you use the SYC native driver to connect to an Adaptive Server Enterprise database. You can create temporary tables in the Database painter, SQL painter, or DataWindow painter. Temporary tables persist for the duration of a database connection, residing in a special database called “tempdb”.

Add a temporary table to the tempdb database by assigning a name that starts with the # character when you create a new table in a painter. (Temporary tables must start with the # character.)

After you create a temporary table, you can create indexes and a primary key for the table. If you define a unique index or primary key, you can execute INSERT, UPDATE, and DELETE statements for a temporary table. Select Edit Data from the pop-up menu of a temporary table to retrieve data that you store in that table.



Standard catalog query limitations

When you click Refresh from the pop-up menu for the Tables node in the Database painter or the Objects view of the DataWindow painter, the list of tables displays temporary tables even though they exist only in the tempdb database. However, once you refresh table definitions from the database, the Objects view can no longer list the index or primary key information of the temporary tables and the Layout view can no longer display that information graphically.


4.4 NCharBind database parameter for Oracle

The NCharBind database parameter for Oracle9i and Oracle 10g improves performance by allowing you to specify whether string variables should be treated as Char or NChar datatypes. The default is to treat string variables as Char datatypes. You can set this parameter on the Transaction tab page in the Database Profile Setup dialog box for Oracle9i and Oracle 10g. For more information, see NCharBind in the online Help.

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.1.3 Extra button displays in XML rendering of a group DataWindow

When you generate a group DataWindow as a Web DataWindow using the XML or XHTML rendering style, an extra button is generated in the detail band and displays in the next group header. [CR 398585]

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. Also, 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. To work around this issue, use an alternative driver. See the Installation Guide for instructions on installing and using 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.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 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”.

7.1 Microsoft files required for deployment

Table 1 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.

You can download the Microsoft GDI+ module 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.

7.2 Xerces files required for deployment

When you deploy applications that use the XML or XHTML Web DataWindow or the ability to save or import data as XML, you now need to deploy three files: PBXerces100.dll, xerces-c_2_6.dll, and xerces-depdom_2_6.dll. The xerces-c_2_1_0.dll file listed in Chapter 13 in the Programmer’s Guide and in the online Help for the DataWindow .NET Runtime Packager is no longer required. The new files provide enhanced support for rendering special characters.

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. Click Certification Report.

  3. In the Certification Report filter select a product, platform, and timeframe and then click Go.

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


Finding the latest information on component certifications

  1. Point your Web browser to Availability and Certification Reports.

  2. Either select the product family and product under Search by Base Product; or select the platform and product under Search by Platform.

  3. Select Search to display the availability and certification report for the selection.


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. If prompted, enter your MySybase user name and password.

  3. Select a product.

  4. Specify a time frame and click Go. A list of EBF/Maintenance releases is displayed.

    Padlock icons indicate that you do not have download authorization for certain EBF/Maintenance releases because you are not registered as a Technical Support Contact. If you have not registered, but have valid information provided by your Sybase representative or through your support contract, click Edit Roles to add the “Technical Support Contact” role to your MySybase profile.

  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.