Home / Products / UltraDev / Support / Downloads  
Icon or Spacer Macromedia Dreamweaver UltraDevSupport Center Release Notes

Dreamweaver UltraDev 4 and 4.01 Release Notes

This document addresses issues fixed in the 4.01 updater and issues that are not discussed in the Dreamweaver UltraDev documentation and may be updated as more information becomes available.

Dreamweaver UltraDev 4.01 updater

Dreamweaver UltraDev 4

Dreamweaver UltraDev 4.01 updater release notes
The Dreamweaver UltraDev 4.01 updater fixes several problems found with Dreamweaver UltraDev 4 after its release.

To use the updater, you must first purchase and install a full version of Dreamweaver UltraDev 4. The 4.01 updater is available for download on the Dreamweaver UltraDev Support Center.

Macintosh specific fixes
Windows specific fixes
Fixes on both Macintosh and Windows
Additional Reference Content

The following is a list of problems fixed by the updater:

Macintosh specific fixes
Macintosh OS 9.1
Certain GIF images are no longer distorted in the Dreamweaver UltraDev document window.
Users will no longer have trouble selecting text in while other specific programs are running in the background.
Other minor performance issues on Macintosh OS 9.1 have been fixed.
For more detailed information on the fixes for OS 9.1, refer to the TechNote: Macintosh OS 9.1 issues in Dreamweaver
Macintosh Double-byte Language Support
Can now view double-byte characters in Dreamweaver UltraDev on Macintosh OS 9 with double-byte language support installed.
Windows specific fixes
Windows ME
Dreamweaver UltraDev, and other programs that make browser calls, sometimes crash when Previewing in Browser on Windows ME. This updater should resolve this problem in many cases.
Fixes on both Macintosh and Windows
Simple Recordset and MDAC2.6RTM
The simple recordset behavior test button will no longer produce JavaScript errors when MDAC2.6RTM is installed.
Log Out User server behavior (Cold Fusion version)
The Cold Fusion log out user server behavior runtime code now uses a variable "UR_MM_newQS" instead of "MM_newQS".
FTP will now honor the ASCII or BINARY transfer mode indicated in the FTPExtensionMap.txt file. This means that .cgi and .htm files will, by default, use ASCII transfer mode.
EUC encoded templates
Changing the encoding of EUC encoded templates and updating files based on those templates will no longer cause corruption.
Context sensitive Reference lookup will now work if you have one or more of the JSP/ASP/CFML reference books installed.
Netscape 6
Additional Dreamweaver support for Netscape 6. This includes Check Target Browser, and JavaScript Behavior updates. Specifically, behaviors now work correctly across frames in Netscape 6, Drag Layer works, as well as Set Text of Layers.
This fix can be downloaded independently, or as a part of this updater. To download independently, go to
JavaScript API
Added a function dw.getNaturalSize( ) to get the size at which the image was saved. The function dw.getNaturalSize( ) takes a file URL as an argument and returns an array or 2 integers (or null if the argument is not a valid local image URL).
SourceSafe Integration
Fixes a number of issues with the current Dreamweaver UltraDev integration with Visual SourceSafe (VSS). The Windows version of the updater fixes several problems with checkout, checkin, and Design Notes. The Macintosh version fixes these same problems as well as problems with the Shared Site Column feature and login dialog labels.
This fix can be downloaded independently, or as a part of this updater. To download independently, go to
WebDAV Integration
Fixes a number of issues with the current Dreamweaver UltraDev integration with WebDAV including problems with host headers, header case-sensitivity, design note encoding, use of illegal characters in connection data, port numbers, and unknown file sizes in the Site window. For more in depth explanation of these fixes, please see the TechNote: Troubleshooting WebDAV Connections.
This fix can be downloaded independently, or as a part of this updater. To download independently, go to
Reference Content: Cold Fusion, Wrox ASP, Wrox JSP
Allaire CFML Language Reference

Add CFML documentation to your UltraDev 4 Reference Panel. The Allaire CFML Language Reference contains a description of each CFML tag, its attributes, and its usage.Allaire CFML Language Reference Copyright 1999, Allaire Corporation

Wrox ASP 3.0 Reference

Provides reference information for ASP developers direct from Wrox Press

Professional Active Server Pages 3.0
Copyright 1999 Wrox Press
Authors: Alex Homer, Dave Sussman, Brian Francis, Dino Esposito, Andrea Chiarelli, Simon Robinson, Richard Anderson, George Reilly, Craig McQueen, Chris Blexrud, Daniel Denault, John Schenken, Bill Kropog, Dean Sonderegger and Matthew Gibbs.

WROX JSP Reference

Provides reference information for JSP developers direct from Wrox Press

Professional JSP
Copyright 2000 Wrox Press
Authors: Karl Avedal, Danny Ayers, Timothy Briggs, Carl Burnham, Ari Halberstadt, Ray Haynes, Peter Henderson, Mac Holden, Sing Li, Dan Malks, Tom Myers, Alexander Nakhimovsky, Stphane Osmont, Grant Palmer, John Timney, Sameer Tyagi,Geert Van Damme, Mark Wilcox, Steve Wilkinson, Stefan Zeiger, John Zukowski

This content can be downloaded independently, or as a part of this updater. To download independently, go to
Dreamweaver UltraDev 4 Release Notes
System requirements
Important information on upgrading from UltraDev 1
Issues for both Windows and Macintosh
Windows-only issues
Macintosh-only issues
Double Byte and High ASCII Character Set issues
How to report bugs
System Requirements  
Windows Macintosh
Intel Pentium Processor or equivalent 166 + MHz Power Macintosh
Windows 95/98/2000, ME or NT 4.0 (Service Pack 5) OS 8.6 or OS 9.x
64 MB of available RAM 64 MB of available RAM
170 MB of available disk space 130 MB of available disk space
256-color monitor capable of 800x600 resolution 256-color monitor capable of 800x600 resolution
Additional Requirements
UltraDev 4 connects to a database using the connection defined on your Application Server. However, if you are running your application server on your own machine (for example Personal Web Server), or wish to make a direct connection to the database from your machine, the following applies:

Microsoft Data Access Components 2.5 (Windows only)
To connect to databases using ADO or ODBC on Microsoft Windows 98 or NT version 4, you will need Microsoft Data Access Components (MDAC) version 2.5 or later. Often this is installed automatically with applications such as Microsoft Office 2000. If you do not have MDAC or have a version earlier than 2.5, you may download and install the latest MDAC version from Microsoft.

Mac OS Runtime for Java (Macintosh only)
To connect directly to databases from your Macintosh with a JDBC driver from your database vendor, you will need the Mac OS Runtime for Java (MRJ) version 2.2 or later. If you do not have the MRJ installed on your Macintosh or have a version earlier than 2.2, you may download and install the latest MRJ version from Apple.
Suggested Requirements for creating Dynamic Data
Creating a Web application in UltraDev consists of building dynamic pages. To run dynamic pages, you need a Web server that supports serving dynamic pages. UltraDev 4 includes support for Active Server Pages (ASP), Cold Fusion Markup Language (CFML), and Java Server Pages (JSP).
To use UltraDev 4 with ASP you will need an ASP server such as:
Microsoft IIS 4.0 or 5.0
Microsoft Personal Web Server

Chili!Soft ASP

To use UltraDev 4 with CFML you will need a CFML server such as:
Cold Fusion 4.0 or 4.5
To use UltraDev 4 with JSP you will need a JSP 1.0 or greater compliant server, such as:
IBM WebSphere 3.0 or 3.5
BEA WebLogic
Netscape iPlanet Enterprise Server
Allaire JRun 3.0
Jakarta Tomcat 3.1 or later

Sun Java Web Server 2.0

Most Web applications need a way to store and retrieve data on a database server. Small to medium size database applications will be able to use a desktop database program such as Microsoft Access. Larger applications will require a larger, industrial-strength database system such as Oracle 8i, Microsoft SQL Server, or IBM DB2.
Important information on upgrading from UltraDev 1
If you have been using UltraDev 1, we recommend that you make a backup of your sites before installing UltraDev 4.
UltraDev 4 changed the way recordsets are created on your page. UltraDev 4 will allow you to convert recordsets created with older versions of UltraDev 1, however please note the following:
Recordsets will be converted to the new UltraDev 4 version when you open them. The recordsets cannot be reverted to the previous version.

Therefore, it is important that you make a backup copy of a site before converting recordsets with UltraDev 4.

If you are using UltraDev 1, you may want to keep that version installed to continue using the older recordset format for production or mission-critical applications. By default UltraDev 4 will be installed in a different directory. Make a backup copy of any sites that you are working on with the older version and use a separate copy of the site with UltraDev 4.

Also note that when a recordset is updated from UltraDev 1 to UltraDev 4, custom code in the recordset will not be migrated and must be manually reapplied.

If you are using UltraDev 1, you may want to keep that version installed to continue using the older recordset format for production or mission-critical applications. By default UltraDev 4 will be installed in a different directory. Make a backup copy of any sites that you are working on with the older version and use a separate copy of the site with UltraDev 4.

Also note that when a recordset is updated from UltraDev 1 to UltraDev 4, custom code in the recordset will not be migrated and must be manually reapplied.

Issues for both Windows and Macintosh

After you open an ASP VB page in an ASP JS site, or an ASP JS page in an ASP VB site, the page directive is changed automatically when a server behavior is added. This can cause runtime errors if scripts in both languages are on the same page with only one language directive.

With Cold Fusion, using the Property inspector to bind data to an object parameter causes two Dynamic Attributes to be displayed in the Server Behavior inspector.

When creating repeated regions with Cold Fusion server model, an error may be reported indicating that this is not supported and instructing the user to delete the outer cfoutput tags. This occurs when the selection is of a row which contains a dynamic data item for a table that already has cfoutput tags around the table.

When updating a repeat region on a Cold Fusion page, custom attributes are not preserved when changing repeat some to repeat all.
With Cold Fusion, the Log In User session does not expire when the browser is closed. If you restart the browser the session still exists. This behavior is a manifestation of the CF server. The CF server sets the session ID cookie with an expiration well into the future and this cookie persists even when the client browser is stopped and restarted.

In the connection setup section of the Help system, there is no reference to RDS.

When using CFML scripts like User Authentication, a file named Application.cfm is needed in the root directory to enable session variables. The Application.cfm file is run before any other CF template in a directory where the Application.cfm file appears.

The Application.cfm file needs to contains the following code:

Cold Fusion requires username for a password protected database. If a password is given you must also enter the username. If no username is given, the error "Error, password is invalid" will be returned.
The workaround is to set the username as Admin.

A page cannot be named default.jsp. Naming a page default.jsp causes a compiler error because default is a reserved word in JSP.

With JSP on the Tomcat application server, running and submitting a Delete Record page which uses the URL redirect causes an 'exhausted record' error because the page tries to execute the query again for the record that was just deleted.
The workaround is to put all dynamic data inside the HTML tag inside a "Show if Recordset is not empty".

When using JSP with Microsoft SQL Server and the com.inet.tds.TdsDriver
driver, a callable gives the parameter direction as "in/out" when it actually should be "out". Even if you modify the parameter direction to be out, when you relaunch the callable dialog, it incorrectly resets it to in/out.
When using a JavaBean, data outside of repeat region will not display for collections. Because the property is not indexed when not in a repeated region, dynamic data from a collection will not have values outside of a repeated region, and will not convert from the visual cue in Live Data.

The Log-in User server behavior has incompatibility across some JSP servers. Instead of using FileName.jsp or /FileName.jsp, use the file name /Site-Root-OnAppServer/FileName.jsp which will work for all JSP application servers. The current API gives the /Site-Root-OnLocalMachine/ but we need the /Site-Root-OnAppServer/. In some cases you are redirected to the correct page, but ";$sessionid$(session_id_here)" is appended to the query string. In other cases, the URL is incorrectly formed.

Double getObject calls cause errors with JDBC 1.0 compliant drivers. UltraDev generates a script using a double getObject call for JSP dynamic list/menu.
Possible workarounds include using a different driver or editing the server behavior script.

The sun.jdbc.odbc driver does not display dynamic data of nvarchar, nchar, nor ntext type of a SQL Server database.

When using the IBM WebSphere JSP application server, the redirect paths used for server behaviors should be full paths, for example: use
/udtests/jsp/menu.jsp instead of menu.jsp.

When using Live Data with a JSP page with JRun as the application server, the page may not be rendered in the document view if it contains "jrun" tags. Live Data works with "jsp:" tags, but it doesn't currently support "jrun" tags or other custom tags.
On JSP, the Check New Username server behavior allows you to insert duplicate usernames.

The Insert Record, Update Record, and Delete Record server behaviors always append request variables to the redirect URL string. Users can change the redirect location by setting a variable within the code.

This can be done by creating a new server behavior using the Server Behavior Builder. This server behavior should be inserted above HTML code with a weight of 25. The code would set the variable MM_editRedirectUrl to the redirect location. No request variables will be added if this variable is set.

Double quote characters cannot be used in the SQL query dialog. Double quotes in SQL, such as in an alias, do not get handled correctly, and reopening the Recordset dialog results in the SQL statement getting corrupted.

Two recordset navigation status objects cannot be used from two different recordsets on one page. When the second object is applied, all the recordset names referred in script blocks are changed to the second recordset, rendering the first object nonfunctional.

A JavaScript reserved word cannot be used as a parameter in a server behavior created with the Server Behavior Builder. For example, do not use "URL" as a parameter as it is a reserved word.
Instead, use a modified name such as "myURL".

For a page that was created with UltraDev 1, if design time and runtime connection are both on the local machine, and HTTP is set to true, this will cause the connection to fail on UltraDev 4. Since it's really a local connection the HTTP should not have been set to true.

You can workaround this by changing the HTTP="true" to HTTP="false" in the connection file generated by UltraDev 4 (for example

The Insert Record and Update Record server behaviors include a "Submit As" option for using Access date data types. Also, if you are using an Access database you may use either the Access date data type or the regular date data type.
The Log-in User server behavior file URL is not updated when a document is saved. When browsing to a file in local folder, if the document is not saved yet, a "file:\\macintosh\...." directory will be assigned. However, after saving the page, the URL should be updated to reflect the relative path.

The Move to Specific Record and Go To Related Page cannot be placed on the same page. When a Move to Specific Record server behavior and a Go to Related Page server behavior are placed on the same page, the Go To's URL parameter is erased. If the user wants to go to another detail page, they should use the Go To Detail Page server behavior.

The Flash button and text link dialog should not allow dynamic parameters. Flash will treat it as a literal, and it won't be processed at runtime. Parameters can be used, just not dynamic parameters.

When a page has Protect Page server behavior on it, it cannot be viewed in Live Data.
The workaround is to add the needed session variables to the Live Data settings initialization scripts.

You cannot select a file from another folder as a Detail page with the Master Detail Live Object. The Detail page must be in the same folder as the Master page.

If you want to use the Server Behavior Builder to create both ASP/VB and ASP/JS versions of the same behavior (and use the same name), you currently need to make modifications to the behavior file by hand.

Manually take out the JavaScript declaration in the HTML file in the ASP folder under Server Behaviors. Also, the code blocks have to have different names. If you have an Untitled1_block1 in VBscript, you need to change the name to to something different, for example: Untitled1_block2 for JSP, block3 for CF and block4 for JavaScript.

Server behaviors created using the dynamic text control option will most likely lead to nested directives. This option was added to allow special cases, such as a dynamic title tag.
The workaround is to take out the nested directives by hand after the server behavior is applied.

Modifying a repeat region in a file that uses a template deletes the associated recordset.

A Jump Menu behavior applied to a dynamic list/menu shows MM locked region in the Behavior panel. The beginlock and endlock tags are not actually visible in the user's document. Instead, they show up in the UI for the Jump Menu JavaScript behavior. If this is encountered, removing the script may still have some residual issues. In that case the workaround is to delete the Jump Menu altogether and start over.

You cannot use Check New Username server behavior if SQLServer field type is text.
The workaround is to change the database field type to varchar.

The Restrict Access server behavior allows user access to a page when validating access levels if no access level has been defined for the user.

To avoid a user having access to all pages if you are using access levels, be sure to set some access level for every user in the database. If no access level is set for a user, that user will not be restricted from viewing pages.

Cold Fusion and JSP pages break when tags are set to uppercase. The problem can appear two different ways:

If the user has put the include file to the server, then when they switch to Live Data they will see yellow tags at the top of their page.

If the user has not put the include file, they will get a Live Data or Preview in Browser error.

You should not use uppercase in tags when typing in code for Cold Fusion or JSP.

If the Override Case for Tags is on, you should turn it off by selecting Edit > Preferences > Code Format and unchecking the Override Case for Tags checkbox.

Note: If you force-upper and then force-lower, the head close tag does not get updated, and you will end up with <head></HEAD>.

The GIF-LZW capability described in the Extensibility Manual is not included in Dreamweaver UltraDev.

The Using Dreamweaver and Using UltraDev documentation (printed and PDF files) incorrectly uses the name Package Manager to refer to the Extension Manager.
The help system uses the correct name: Extension Manager.
Behaviors can now be used in pages from Templates. These behaviors will be preserved even if you later update the page to incorporate changes in the original template.
Fireworks 4 single image attributes
The link and alt attributes assigned to a single image in Dreamweaver UltraDev do not show up in Fireworks, but are retained.
For detailed information on creating new button templates using Flash and the Generator text object, see the article on the Dreamweaver Support Center. Also visit the Macromedia Exchange to find additional downloadable Flash Buttons.
Flash Objects in Dreamweaver UltraDev do not automatically detect whether a user has Flash installed in their browser. If you'd like to do this kind of detection, please use the behaviors in the JavaScript Integration Kit for Macromedia Flash 5, which is available on the Macromedia Exchange.

Netscape 6
Dreamweaver UltraDev 4 does not fully support Netscape 6. For more information see the Netscape 6 TechNote (TechNote 14876) on the Dreamweaver Support Center.

New keyboard shortcut changes
Some keyboard shortcuts have been changed in Dreamweaver UltraDev 4 to be consistent with other Macromedia products. Dreamweaver UltraDev 4 also ships with a set of Dreamweaver 3 keyboard shortcuts if you prefer to work with the same set as Dreamweaver 3.
The Synchronize feature may not work reliably with WebDAV integration if the system time on the server is significantly different than the system time on your computer.

To use the JavaScript Debugger you must have Java and JavaScript enabled in your browser.

The JavaScript Debugger in Dreamweaver UltraDev will work with the following browsers:

Internet Explorer 4.0+, Netscape 4.5+, excluding Netscape 6

Netscape 4.5+, excluding Netscape 6

Windows-only issues

You will not be able to install Dreamweaver UltraDev on a Windows NT or Windows 2000 server unless you have administrator privileges.
Although there is an error message that states this clearly, this is a change from previous versions.

Debugger Security warning on Windows ME often pops up behind the debugging browser window and sometimes behind Dreamweaver UltraDev windows as well.
To see the security warning, you can either minimize all windows or click the security dialog in the taskbar to bring it to the front.

Using the JavaScript Debugger with Internet Explorer
Dreamweaver UltraDev may appear to freeze if you try to make a new folder or rename a folder or file in Windows while the JavaScript Debugger is open in Internet Explorer. Closing the browser window should fix this problem.

Macintosh-only issues

When working with Cold Fusion on the Macintosh, you should set the Line Breaks preference to "CR LF Windows". If a default Macintosh line break is used with Cold Fusion, a number of issues may be encountered:

The CFML server treats the file as one long line. If a CFSCRIPT contains a "//" comment, then the rest of the script is treated as one big comment.
WebDAV transfers Cold Fusion files with Macintosh carriage returns, causing Cold Fusion Server to have problems with the file.

Navigation Bar, Master-Detail, Move To Record server behaviors will encounter Cold Fusion Server errors.

To change your preferences to use Window-style line endings: select Edit > Preferences > Code Format and change the Line Breaks setting to "CR LF Windows".

With Cold Fusion, Live Data reports an error if the path has a space in it. Spaces above the site root are usually okay, but there should not be any spaces in the path in the site itself.

If you create a server behavior with the Server Behavior Builder that has no parameters, that server behavior's name will not appear in the Server Behavior Panel when applied to a page.

There are two workarounds:

In the Server Behavior Builder, create a parameter and then delete it.

Add a title tag to the XML group file by hand.

When starting the JavaScript debugger, the alert "Please wait for the Dreamweaver Debugger Applet to load. Click OK after giving the applet permission to run." may appear multiple times. After clicking through several of these messages, the debugger will start.

BBEdit 6.01 fixes two bugs in the Dreamweaver-BBEdit integration. BBEdit 6.01 demo version and the BBEdit 6.01 updater will be on the Dreamweaver UltraDev 4 Macintosh CD. Customers who have already purchased BBEdit 6.0 should be aware of the free updater that fixes the Dreamweaver UltraDev integration.
See the BBEdit 6.01 release notes for more details or the BBEdit Updates page to download the updater.

SourceSafe Integration on the Macintosh requires some additional set up steps before you can get started.
Read Working with SourceSafe on the Macintosh on the Dreamweaver Support Center for detailed instructions on how to set up Dreamweaver SourceSafe integration.

Create Web Photo Album on the Macintosh will not work if there are no open Dreamweaver UltraDev documents.
The Search button in Using Dreamweaver, Using UltraDev or Extending Dreamweaver and UltraDev Help systems may not work in Internet Explorer 4.5 on the Macintosh. Upgrading to Apple Mac OS Runtime for Java (MRJ) 2.2.3 will fix this problem.

The Search button in Using Dreamweaver, Using UltraDev or Extending Dreamweaver and UltraDev Help systems may not work in Netscape 6 on some Macintosh systems.
To workaround this problem, set another browser as your primary browser in Dreamweaver.

JavaScript Debugger will not work when TCP/IP is set to PPP and you are not logged in.

After launching help, clicking back to UltraDev relatively quickly results in an invisible text insertion point, no keyboard keys function, and attempting to select text results in disjointed highlighted regions.
Double Byte and High ASCII Character Set issues
All Server Models

Avoid using DSN's containing double byte or accented characters.

Shift JIS is the only supported Japanese encoding.
File names and file paths containing double byte characters should not be used.
UltraDev only supports the IBM WebSphere JSP application server on double byte operating systems. Other JSP application servers have known incompatibilities with double byte character sets.

Only the following drivers have been tested with UltraDev and are supported to handle double byte data correctly when used with an application server. Be sure that the "Using Driver on the Application Server" option is selected.

Oracle Thin Driver
IBM DB2 App Driver

IBM DB2 Net Driver

Double byte table names, column names, and stored procedures are not supported.
Creating a filter for a string with double byte characters works on the server but using the test button will not return the correct data.
JavaBeans class names should not contain double byte or accented characters.
Cold Fusion
Cold Fusion Server does not support Table Names, Column Names and Stored Procedures which contain double byte or accented characters.
How to report bugs
Find a bug? Please use the Bug Report Form to send bugs to the Dreamweaver UltraDev team.