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

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.

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, Stéphane Osmont, Grant Palmer, John Timney, Sameer Tyagi,Geert Van Damme, Mark Wilcox, Steve Wilkinson, Stefan Zeiger, John Zukowski

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.

Chili!Soft ASP

Sun Java Web Server 2.0

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.

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

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

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

CF
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:
<CFAPPLICATION NAME="Name"
SESSIONMANAGEMENT="Yes" >

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

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

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

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

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

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.

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
<yoursite>/Connections/<yourConn>.asp).

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.

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.

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.

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:

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.

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.

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:

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.

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

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

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:

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.

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.

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

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.