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
Go to Product Manuals.
Follow the links to the appropriate Sybase product.
Select the Release Bulletins link.
Select the Sybase product version from the Release Bulletins list.
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
Microsoft Windows 2000 with Service Pack 4
Microsoft Windows XP with Service Pack 2
Microsoft Windows Server 2003
Sybase has performed minimal testing of DataWindow .NET on the Windows 2003 platform; however, this platform is fully supported.
2.1 Third-party software licenses
This product includes software developed by the Apache Software Foundation ( http://xml.apache.org/). For a copy of the Apache Software License that applies to Xerces, see the APACHE_LICENSE.TXT file in the Support folder on the CD.
This product uses GNU Ghostscript to save DataWindow® objects in PDF format. To use this feature, you must download and install gs705w32.exe or gs706w32.exe. These versions are available on the University of Wisconsin Computer Sciences Web site and the SourceForge Web site.
You can find a list of sites that mirror the University of Wisconsin Web site here: Mirror Sites. You can also search the Web for the file names gs705w32.exe or gs706w32.exe to find a local download site. Mirror sites for the GNU FTP site where you can obtain Ghostscript source files are listed on the GNU Web site.
Your use of GNU Ghostscript is subject to the terms and conditions of the GNU General Public License (GPL). For a copy of this license, see http://www.gnu.org/licenses/gpl.txt.
3. Special installation instructions
3.1 Before you install
Before you install this release, shut down any applications running on your system. Reboot your system after all the installations are complete. The self-extracting executable file in this release extracts 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 tab page or Advanced tab page, and specify a location that has sufficient space.
3.2 Installing DataWindow .NET
DataWindow .NET 1.0.1 is available on the DataWindow .NET page of the Sybase EBFs/Maintenance site. Download the files you require and extract the contents of the zip file following the instructions in the download notes that accompany the release.
In order to install DataWindow .NET version 1.0.1, you must have already installed DataWindow .NET version 1.0 on your computer.
To update DataWindow .NET:
Copy the contents of your Sybase\DataWindow .NET 1.0 and Sybase\DataWindow Designer 1.0 directories to another directory to provide a backup.
Run the setup.exe file in the DataWindow.NET directory extracted from the DataWindowDotNET.zip file.
Run the setup.exe file in the DataWindow_Designer directory extracted from the DataWindow_Designer.zip file.
4. Changed functionality in this version
4.1 Strong-named assemblies
DataWindow.dll and DataWindowInterop.dll are strong-named assemblies in this release. A strong name includes the assembly’s identity as well as a public key and a digital signature. For how to deploy these files, see “7.2 Deploying .NET assemblies”.
4.2 PrintDialog method
The new PrintDialog method on IDataWindow and DataWindowControl invokes the system Print dialog box to allow users to change printer settings at runtime. You can also display the dialog box using a new overloaded version of the Print method with two boolean arguments. Set the second argument to true to invoke the system Print dialog box.
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 application 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 Database connectivity issues
5.2.1 Window is a reserved word in ASA
Set the DelimitIdentifier database parameter to “Yes” in the ConnectString.
Set the ASA database option “SET OPTION NON_KEYWORDS = ‘WINDOW’”.
Enclose the column name in quotation marks in SQL statements.
5.2.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.2.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.2.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.2.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]
5.3 DataWindow issues
5.3.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:
Select Run from the Windows Start menu.
In the Open box, type gpedit.msc and click OK.
In the Group Policy console, expand Computer Configuration, Administrative Templates, and Printers.
Disable “Disallow Installation of Printers Using Kernel-Mode Drivers.”
5.3.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]
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 and Borland C#Builder.
Microsoft .NET Framework Version 1.1 is required for deployment.
7. Documentation updates and clarifications
7.1 Using an ADO.NET connection
DataWindow .NET provides two objects, Transaction and AdoTransaction, that you can use to manage your application’s connection to a database.
The Transaction object is available in the Visual Studio .NET 2003 Toolbox so that you can use drag-and-drop to add it to a form, but it does not export a public interface and can be used only with DataWindow objects. To share an ADO.NET connection with other objects or controls in your application, declare an instance of the AdoTransaction object in your code. For more information, see the chapter on transaction objects in the Programmer’s Guide.
7.2 Deploying .NET assemblies
Deploy .NET assemblies in the same directory as the executable file for the application.
Use a .NET application configuration file to assign the path of the .NET assembly. The file contains configuration settings that the common language runtime (CLR) reads as well as settings that the application reads. For an executable file, the configuration file has the same name as the executable file with the extension .config.
For more information about configuration files, see the section on application configuration files in the .NET Framework Developer’s Guide.
Add the assembly to the Global Assembly Cache (GAC). Use this technique only when the assembly must be shared by several applications. You can no longer install an application using xcopy if one of the assemblies it uses is in the GAC. To use this option, your .NET assemblies must have strong names.
For more information about the GAC, see the section on the Global Assembly Cache in the .NET Framework Developer’s Guide.
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
The Getting Started CD contains release bulletins and installation guides in PDF format, and may also contain other documents or updated information not included on the Technical Library CD. It was included with your DataWindow .NET 1.0 software. To read or print documents on the Getting Started CD you need Adobe Acrobat Reader (downloadable at no charge from the Adobe Web site, using a link provided on the CD).
The Technical Library CD contains product manuals and was included with your DataWindow .NET 1.0 software. The DynaText reader (included on the Technical Library CD) allows you to access technical information about your product in an easy-to-use format.
Refer to the Technical Library Installation Guide in your documentation package for instructions on installing and starting the Technical Library.
The Technical Library Product Manuals Web site is an HTML version of the Technical Library CD that you can access using a standard Web browser. In addition to product manuals, you will find links to EBFs/Updates, Technical Documents, Case Management, Solved Cases, newsgroups, and the Sybase Developer Network.
To access the Technical Library Product Manuals Web site, go to Product Manuals.
9.1 Sybase certifications on the Web
Technical documentation at the Sybase Web site is updated frequently.
Finding the latest information on product certifications
Point your Web browser to Technical Documents.
Select Products from the navigation bar on the left.
Select a product name from the product list and click Go.
Select the Certification Report filter, specify a time frame, and click Go.
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.
Point your Web browser to Technical Documents.
Click MySybase and create a MySybase profile.
9.2 Sybase EBFs and software maintenance
Finding the latest information on EBFs and software maintenance
Point your Web browser to the Sybase Support Page.
Select EBFs/Maintenance. If prompted, enter your MySybase user name and password.
Select a product.
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.
Click the Info icon to display the EBF/Maintenance report, or click the product description to download the software.