ER/Studio Data Architect 9.0.1 ReadMe

Welcome to ER/Studio Data Architect® 9.0.1

ER/Studio Home | ER/Studio Documentation | Embarcadero Technical Support | www.embarcadero.com

Thank you for using Embarcadero ER/Studio Data Architect, previously known as ER/Studio, the award-winning data modeling application for logical and physical database design and construction. ER/Studio Data Architect's (ER/Studio DA) powerful, multi-level design environment addresses the everyday needs of database administrators, developers and data architects who build and maintain large, complex database applications.

ER/Studio DA's progressive interface and processes have been logically organized to effectively address the ease-of-use issues that have plagued data modeling tools for the past decade. The application facilitates your ability to create, understand and manage the mission-critical database designs within an enterprise. It offers strong logical design capabilities, bidirectional synchronization of logical and physical designs, automatic database construction, accurate reverse engineering of databases, and powerful HTML-based documentation and reporting facilities. Before you use ER/Studio, please read the information below.

For instructions and more detailed descriptions of new features in our last major release, see the ERStudioQuickStart.pdf file, in the ER/Studio DA installation Readme directory or download the most-recent guide from Embarcadero's Web site, http://www.embarcadero.com/resources/documentation.html.

WHAT'S NEW IN VERSION ER/Studio DA 9.0.1

Customer requests continue to guide us in our quest to bring to market the best database tools available. Thank you for your support.

User Interface Improvement

Double-click behavior on the Where Used tab of the Table Editor and Entity Editor can be controlled by the Tools > Options > Where used tab so that double-clicking an object will either bring up the object editor or the user-defined mapping editor.

DB2 z/OS Support Improvement

For DB2 z/OS physical models a new Generated by Default option is available for ROWID columns and columns marked as IDENTITY columns. That option is also available for TIMESTAMP data types to indicate a "row change timestamp" column.

WHAT'S NEW IN VERSION ER/Studio DA 9.0 and ER/Studio Repository 6.0

Additional Operating System Support

ER/Studio DA and ER/Studio Repository now support Windows 7, 64-bit mode in addition to 32-bit mode.

Additional Platform Support

ER/Studio DA now fully supports Netezza 4.6 and 5.0.

User Interface Improvements

Denormalizations are no longer displayed in the Data Model Tree, denormalizations such as Horizontal and Vertical Splits, and Rollups and Rolldowns, are maintained with the table data and appear on the Where Used tab of the Table Editor. From the Where Used tab you can see the denormalization history of the table. You can also edit and delete denormalization mapping from the Where Used tab. For more information, see the Denormalization section in the ER/Studio Data Architact User Guide or online help.

ER/Studio Repository Performance Improvements

ER/Studio Repository software is now multi-threaded, enabling some processes to occur concurrently. The following describes some important rules that affect multi-threading on the Repository:

If a Check In transaction is being processed on a given Diagram or Data Dictionary, all other operations on that Diagram or Data Dictionary must wait until the Check In completes.
If an Add or Check In transaction is being processed, all other Add or Check In transactions must wait until the initial transaction completes. This same rule applies to Set Named Release, Branch and Branch/Merge Check In operations.
Most other common tasks, including Log Ins, Log Outs, Gets, Check Outs and Security Center operations are processed concurrently by the server, but may be affected by database level-locking mechanisms.

Release Notes

Important Installation Notes

Important Advisory Notes

Known Issues

Bug Fixes

Upgrade Instructions

Upgrading ER/Studio DA

Upgrading ER/Studio Repository

Additional Resources

Licensing Your Embarcadero Product

Embarcadero Technologies Product Support

Embarcadero Technologies Technical Support

Embarcadero Technologies on the Web

Release Notes

Important Installation Notes

To install ER/Studio DA on Windows XP Professional, Windows XP Home Edition or Windows Vista, you must have administrative privileges. Once you have installed ER/Studio DA, you can then log in as a standard or limited user and use the application without having administrative privileges.
In order to run ER/Studio DA, you must provide valid licensing information.
When you install ER/Studio DA, certain files and directories that were previously stored under the Program Files folder are now by default installed to system-specified application data directories.
During installation, the following directories are created:

For Datatype Mapping Editor files, which is also the default location for user-generated Datatype Mapping files:

Windows XP: C:\Documents and Settings\All Users\Application Data\Embarcadero\ERStudioDA_X.X\DatatypeMapping
Windows Vista: C:\ProgramData\Embarcadero\ERStudioDA_X.X\DatatypeMapping

For Automation Handler files, which is also the default location for sample macros:

Windows XP: C:\Documents and Settings\All Users\Application Data\Embarcadero\ERStudioDA_X.X\Macros
Windows Vista: C:\ProgramData\Embarcadero\ERStudioDA_X.X\Macros

For sample model files, for which a shortcut is generated in the ER/Studio DA program group:

Windows XP: C:\Documents and Settings\All Users\Application Data\Embarcadero\ERStudioDA_X.X\Sample Models
Windows Vista: C:\ProgramData\Embarcadero\ERStudioDA_X.X\Sample Models

When the application is run for the first time, the following directories are created by ER/Studio DA:

Directories used by the Repository client to transfer files to and from the Repository server:

Windows XP:

C:\Documents and Settings\<user>\Application Data\Embarcadero\ERStudio\RepoIn
C:\Documents and Settings\<user>\Application Data\Embarcadero\ERStudio\RepoOut

Windows Vista:

C:\Users\<user>\AppData\Roaming\Embarcadero\ERStudio\RepoIn
C:\Users\<user>\AppData\Roaming\Embarcadero\ERStudio\RepoOut

Default directory for Report files:

Windows XP: C:\Documents and Settings\<user>\Application Data\Embarcadero\ERStudio\Reports
Windows Vista: C:\Users\<user>\AppData\Roaming\Embarcadero\ERStudio\Reports

Default directory for SQL scripts:

Windows XP: C:\Documents and Settings\<user>\Application Data\Embarcadero\ERStudio\SQLCode
Windows Vista: C:\Users\<user>\AppData\Roaming\Embarcadero\ERStudio\SQLCode

Default directory for Quicklaunch files:

Windows XP: C:\Documents and Settings\<user>\Application Data\Embarcadero\ERStudio\XML
Windows Vista: C:\Users\<user>\AppData\Roaming\Embarcadero\ERStudio\XML

Default Save location for new diagrams:

Windows XP: C:\Documents and Settings\All Users\Application Data\Embarcadero\ERStudioDA_X.X\Sample Models
Windows Vista: C:\Users\<user>\Documents\ERStudioDA_X.X

Known Issues
ERS-19014	When merging tables of a Netezza model, the Repository does not detect the RANDOM flag on the Distribution tab.
ERS-19140	The Distibute On Random property is not applied to the diagrams on the Review Changes Window when merging a diagram to the Repository.
ERS-19199	The Sybase ASE 15.x client is not yet supported
ERS-19221	Support for ROW SECURITY has not yet been implemented for Netezza.
ERS-19252	Denormalization and User mapping changes are still under construction.
ERS-19268	Editing an associative table after breaking the link to the corresponding non-specific relationship in the physical model can lead to data corruption.
ERS-19269	A Repository Merge Error 3 error may occur when a relationship is deleted on one machine and modified on another machine.
ERS-19274	Repository Log In hangs when the Repository database server is down.
ERS-19308	The edit data lineage source/target mapping dialog comes up slowly.
ERS-19331	Tables that are already the target of a denorm cannot be added as the target for another denormalization.
ERS-19363	The View Parser currently does not support the Netezza cast syntax.
ERS-19429	Denormalization Mappings are not displayed properly in the Repository Review Changes dialog.
ERS-19552	It is currently not possible to edit names of pre-mapped tables in Denormalizaton Mappings.
ERS-19562	In the Edit Mappings dialog, applying an attachment to one table involved in a Denormalization Mappings will apply the attachment to all tables in the mapping.
ERS-19590	On some systems it may be necessary to reinstall after uninstalling an older version.
ERS-19597	RepoServerFix has not yet been updated to work with Repository 6.0.
ERS-19633	It is currently not possible to set the PRIQTY and SECQTY fields to -1 for DB2 z/OS index and tablespace partitions.

Bug Fixes

Use your browser Find feature to locate a particular bug number or click a link below to see the issues addressed in a specific build.

Bugs Fixed in ER/Studio DA 9.0.1

Bugs Fixed in ER/Studio DA 9.0

Bugs Fixed in ER/Studio DA 9.0.1

ERS-14534	ER/Studio DA no longer places quotes around the keyword USER in DB2 LUW column defaults.
ERS-18696	ER/Studio DA no longer generates duplicate Foreign Key constraint DROP statements when generating alter script.
ERS-18702	The Compare Wizard now properly matches functions with the same name in different schemas.
ERS-18703	The Function Editor now supports creating functions with the same name in different schemas.
ERS-18704	The Compare Wizard now properly merges views between models.
ERS-18914	The DDL Wizard now generates the table type for all MySQL tables.
ERS-18934	The Review Changes dialog no longer displays "Update unified." messages.
ERS-19000	ER/Studio DA now generates an error when attempting to rename an "Other Source" in the Data Lineage tree with the name of an existing physical model.
ERS-19008	The About box now reflects the current license type.
ERS-19011	The Compare Wizard now ignores "Freeze Names" differences when comparing against a database.
ERS-19073	The ReverseEngineer.Database automation property now works for Sybase databases.
ERS-19165	The Repository Rename Filename dialog no longer allows users to specify illegal filename characters.
ERS-19194	The DDL Wizard now properly generates bitmap indexes on partitioned tables.
ERS-19243	Mapped images in HTML Reports now work properly when the zoom level is something other than 100%.
ERS-19280	The DDL Wizard now offers the Enclose Names in Quotes/Brackets option for Netezza.
ERS-19299	Capacity Planning estimates are now reverse-engineered properly from Oracle databases.
ERS-19333	Owner name is no longer shown unnecessarily in Where Used.
ERS-19304	The Compare Wizard now merges differences in brackets around owner and view names.
ERS-19314	The Compare Wizard now retains the column list when merging a view.
ERS-19337	The RepoSrvDb.log file now contains the name of the diagram being deleted from the Repository.
ERS-19412	The Duplicate Named Attribute editor now appears when multiple relationships are drawn from the same parent to a child.
ERS-19427	Reverse engineering from Netezza via automation no longer fails if the owner is the wrong case.
ERS-19448	The DDL Wizard now generates column level check constraints for columns bound to UDTs when the "Generate table-level check constraints" option is enabled.
ERS-19503	It is no longer necessary to open, save, close, and reopen files from previous versions before a Report can be generated.
ERS-19537	Denorm mapping folders are now correctly shown in data model tree in some cases.
ERS-19538	Denormalization Mappings are now displayed correctly in HTML Reports containing multiple physical models.
ERS-19591	The Compare Wizard no longer truncates FK constraint names in DB2 z/OS alter scripts.
ERS-19616	User-defined mappings are shown properly in reports.
ERS-19619	Nested column mappings are now properly updated when loading files from older versions.
ERS-19691	The "Generate By Default" option has been added for DB2 z/OS TIMESTAMP columns.
ERS-19733	ER/Studio no longer prefixes the owner name on denormalized tables when converting the DM1 from an earlier version.
ERS-19752	The Submodel.SchemaObjDisplays collection now returns all schema objects in the submodel.
ERS-19755	The Entity/Table editor now displays the Logical/Physical Only status of FK columns in read-only format.
ERS-19811	The License Registration dialog is no longer displayed when performing a "silent" installation.
ERS-19842	The "Data Lineage Import from Excel" macro has been updated to not generate "Stack overflow" errors when the model constains large table and/or column id's.

Bugs Fixed in Bugs Fixed in ER/Studio DA 9.0

ERS-11021	Entity names now wrap properly in Name display mode.
ERS-12204	It is now possible to set PRIQTY -1 for DB2 indexes and tablespaces.
ERS-15307	Relationship lines are now drawn properly after copy/paste.
ERS-16515	Auto-Layout now properly handles subtype relationships.
ERS-16568	Performance of Repository Get Diagram has been improved.
ERS-18001	The Automation Interface methods for Visual Data Lineage now work properly.
ERS-18111	Duplicate attributes are no longer created during check-in after deleting a relationship with Make Native enabled.
ERS-18341	The Compare Wizard now generates the index COMPRESS clause when comparing against an Oracle database.
ERS-18410	The performance of copying and pasting stored procedures has been improved.
ERS-18588	Foreign Keys are now displayed in the Binding Information tab of the domain and UDT editors.
ERS-18682	The Submodel Synch Utilty no longer synchronizes submodel members when the option is unchecked.
ERS-18732	The Project.AddDiagrams automation interface method now works properly.
ERS-18737	The Compare Wizard now generates the correct alter script when modifying DB2 tables that have Generated columns.
ERS-18752	The Compare Wizard now properly drops indexes prior to recreating PK constraints that use indexes.
ERS-18798	The Compare Wizard now properly generates "GENERATED ALWAYS" columns when altering a DB2 table.
ERS-18809	HTML Report images no longer contain errant relationship lines.
ERS-18833	SQL Import now supports TeraData scripts with the COMMENT clause.
ERS-18837	Performance of Repository Get Diagram has been improved.
ERS-18842	The DDL Wizard now properly generates Foreign Keys.
ERS-18848	HTML Reports no longer include tree nodes for submodels that were excluded from the report.
ERS-18849	The Automation Interface now remains stable when exporting submodel images.
ERS-18862	The XML Schema Wizard now includes datatype lengths for local simple types.
ERS-18880	The MergeModelObject automation method now uses the specified quicklaunch file.
ERS-18903	The Model.Entities collection now only returns entities in the current model.
ERS-18905	The DDL Wizard now properly generates Foreign Keys.
ERS-18931	The ERSVersion automation method now returns the entire version string.
ERS-18941	Oracle triggers using the keyword EXEMPT as an identifier are now supported.
ERS-18956	The Generate DLL wizard now checks to make sure that the owner name being bracketed inside procedures and views is followed by a period.
ERS-18978	ER/Studio Data Architect now remains stable when revese-engineer DB2 sequence object permissions.
ERS-19118	The Automation Interface methods for Visual Data Lineage now work properly.
ERS-19152	The View parser now supports SQL Server views that use INTERSECT.
ERS-19154	The View parser now supports SQL Server views that use EXCEPT.
ERS-19187	HTML Report images no longer contain errant relationship lines.
ERS-19226	The correct column sequence is now maintained when merging new columns into split tables.
ERS-19235	Adding entities with relationships to a submodel no longer affects other submodels.
ERS-19244	The Positioning Complete option has been removed from the View menu.
ERS-19245	The DDL Wizard now properly generates Foreign Keys.
ERS-19260	A file now remains marked dirty if an error occurs when saving the file.
ERS-19355	The Automation Interface methods for Visual Data Lineage now work properly.
ERS-19388	Naming Standards are no longer applied to Foreign Keys when translating Physical to Logical in a physical model
ERS-19422	Diagram Attachments are now preserved after renaming a diagram
ERS-19510	SQL Import now supports DB2 objects that have an owner name that begins with "$".

Upgrade Instructions

Upgrading ER/Studio Data Architect

Use the following checklist to ensure ER/Studio Data Architect is correctly upgraded.

Upgrade Checklist

Download ER/Studio Data Architect Upgrade. To download the most current release, go to http://www.embarcadero.com/downloads.
Review the ER/Studio Data Architect ReadMe. For the most current installation and usage information, see the ReadMe at http://docs.embarcadero.com.
Prepare to Upgrade. For what to do before you upgrade to the latest version, see "Preparing to Upgrade".
Upgrade ER/Studio Data Architect. For ER/Studio Data Architect upgrade details, see "Upgrading ER/Studio Data Architect".
Upgrade ER/Studio Data Architect Diagrams. For ER/Studio Data Architect diagram upgrade details, see "Upgrading Diagrams".

Important Notes

You can install ER/Studio Data Architect 9.x and an earlier ER/Studio Data Architect version on the same workstation.
If you have an ER/Studio Enterprise installation, which includes ER/Studio Repository, you must also upgrade the Repository to coincide with the build date of ER/Studio Data Architect.
Any *.dm1 files from the previous version you open will be upgraded to 9.x format when you open them for the first time. You can then choose to save the file in the new format using the same or a different name. Previous versions of ER/Studio Data Architect cannot read version 9.x files.
Since the denormalization feature has changed in 9.0, any documents containing denormalization mappings will be upgraded to use the new feature of ER/Studio DA 9.0. Denormalization mappings are now retained with the table data and can be viewed and edited on the Where Used tab of the Table Editor. Denormalization history, including Columns, Indexes, and Relationships of pre-map tables, is no longer retained, so the undo and make permanent functions specifically for denormalizations are no longer available. Denormalization mappings have been worked into the normal undo function of the product allowing them to be undone like other operations. However, the names of the pre-map tables are retained. Retaining only essential pre-map information means that the DM1 file with denormalizations is smaller and therefore opens faster.
Upgrading diagrams can be time consuming and memory intensive. The number and size of ER/Studio Data Architect diagrams managed in the upgraded Repository will dictate how long the upgrade process takes.
Reference Models supported in previous versions are not supported in ER/Studio Data Architect 7.x and later releases.
If you decide to uninstall a previous version, you will be given the option of saving your existing license. If you decide to reinstall the previous version, you will have the option to restore your license or to use a trial license.

Preparing to Upgrade

The steps that follow are for ER/Studio Enterprise installations only, which include ER/Studio Repository.

Ensure you have backed up all your .dm1 files.
Check in all your diagrams and objects. If you attempt check in a file from a previous-version that has the same name as an existing file, the existing file will become corrupted.
Rename all local copies of Repository diagrams in the active file directory as follows:

From the ER/Studio Data Architect Main menu, choose Repository > Options.
Make note of the name of the Active File Directory.
Switch to Windows Explorer> and rename all the diagrams in the Active File Directory.

Ensure no one is logged into the Repository.
Backup the current Repository database.
Remove the previous version of the Repository application. Choose Control Panel > Add Remove Programs > Repository x.x, and then click Remove.
Restart the Repository host computer.

Upgrading ER/Studio Data Architect

Follow the instruction for installing ER/Studio Data Architect, in ER/Studio Quick Start Guide located in the installation Readme directory.

Upgrading Diagrams

If you have an ER/Studio Data Architect installation that does not include ER/Studio Repository, see "Upgrading ER/Studio Data Architect Standard Diagrams". If you have ER/Studio Enterprise, which includes ER/Studio Repository, see "Upgrading ER/Studio Data Architect Diagrams".

Note: Since the denormalization feature has changed in 9.0, any documents containing denormalization mappings will be upgraded to use the new feature of ER/Studio DA 9.0. Denormalization mappings are now retained with the table data and can be viewed and edited on the Where Used tab of the Table Editor. Denormalization history, including Columns, Indexes, and Relationships of pre-map tables, is no longer retained, so the undo and make permanent functions specifically for denormalizations are no longer available. Denormalization mappings have been worked into the normal undo function of the product allowing them to be undone like other operations. However, the names of the pre-map tables are retained. Retaining only essential pre-map information means that the DM1 file with denormalizations is smaller and therefore opens faster.

Upgrading ER/Studio Data Architect Standard Diagrams

Note: This procedure is for ER/Studio Data Architect Standard installations only, which do not include the Repository.

Once you have installed the new version of ER/Studio Data Architect, from the new version of ER/Studio Data Architect, open each of your old *.dm1 files. ER/Studio Data Architect will convert the files to the new format before opening them. Then save the files with a new name or overwrite the previous version by using the same name.

Upgrading ER/Studio Data Architect Diagrams

Note: This procedure is for ER/Studio Enterprise installations only, which include ER/Studio Repository.

Update your existing diagrams before you check out any diagrams or do any work with the new version of ER/Studio Data Architect.

Upgrading diagrams can be time consuming and memory intensive. The number and size of ER/Studio Data Architect diagrams managed in the upgraded Repository will dictate how long the upgrade process takes.

Start ER/Studio Data Architect.
Update the Repository Options to recognize the new ER/Studio Repository as follows:
- From the ER/Studio Data Architect Main menu, choose Repository > Repository Options.
- In the Server Machine box, type the host name or IP address of the Repository machine, and then click OK.
Log on to the Repository using an account with Super User privileges
Run the Diagram Data Version Upgrade utility as follows: From the ER/Studio Data Architect Main menu, choose Repository > Administration > Diagram Data Version Upgrade.

This will update your existing diagrams to the latest version.

Notes

By default, the Super User role is assigned to the Admin user. The default Admin user name and password are: Admin and Admin.
The diagram data version upgrade does not upgrade Named Releases. The system prompts you to upgrade named releases the first time you open them after you upgrade ER/Studio Data Architect.
After the diagrams are updated, each user must perform a clean get of all Repository diagrams they were working on previously.

Upgrading ER/Studio Repository

Use the following checklist to ensure ER/Studio Repository is correctly upgraded.

Upgrade Checklist

Download ER/Studio Enterprise Upgrade. To download the most current release, go to http://www.embarcadero.com/upgrade/upgrade.html.
Review the ER/Studio ReadMe. For the most current installation and usage information, see the ReadMe at http://docs.embarcadero.com.
Prepare to upgrade. For what to do before you upgrade to the latest version, see "Preparing to Upgrade".
Upgrade ER/Studio Repository. For ER/Studio Enterprise installations, which include the Repository. For ER/Studio Repository upgrade details, see "Upgrading the Repository".

Important Notes

The Repository upgrade must be done incrementally from one major version to the next until the target version is reached. You cannot skip major versions during the Repository upgrade as the installer for each major version only contains the database changes between the new version and the previous one. When upgrading from earlier versions, such as from 4.5 to Repository 6.0, you must first upgrade the Repository to version 5.0, update the database, uninstall version 5.0, then upgrade to 5.5, update the dateabase, uninstall version 5.5, and then upgrade to Repository 6.0 and update the database. Once the Repository upgrade is complete and you have installed the latest version of ER/Studio Data Architect, then you should upgrade your diagrams with the latest version of ER/Studio DA. For more information, see "Upgrading ER/Studio Data Architect Diagrams" . Consult Embarcadero Technical Support when upgrading from versions prior to 4.5.
If you are upgrading to ER/Studio Repository, upgrade your version of ER/Studio Data Architect also. Ensure the build date of ER/Studio Repository coincides with the build date of ER/Studio Data Architect.
If you are also using ER/Studio Portal, you must also upgrade it to the latest version.
You can install ER/Studio Data Architect 9.x and an earlier ER/Studio Data Architect version on the same workstation.
Any *.dm1 files you use from the previous version will be copied and converted to 8.x format when you open them for the first time. You can then save the diagram with a different name or use the same name to write over the old file. Previous versions of ER/Studio Data Architect will not read 8.x and higher files.
Upgrading diagrams can be time consuming and memory intensive. The number and size of ER/Studio Data Architect diagrams managed in the upgraded Repository dictates how long the upgrade process takes.
Reference Models, supported in previous versions, are not supported in ER/Studio Data Architect 7.x and later versions.

Preparing to Upgrade the Repository

Ensure you have backed up all your .dm1 files.
Check in all your diagrams and objects. Note:If you try to check in a file from the previous version with the same name as a current file, the current file will become corrupted.
Rename all local copies of Repository diagrams in the active file directory as follows:

Choose Repository > Options.
Make note of the Active File Directory.
Switch to the Windows Explorer and rename all the diagrams in the Active File Directory.

Ensure no one is logged into the Repository.
Backup the current Repository database.
Restart the Repository host computer.

Upgrading the Repository

Note: This procedure is for ER/Studio Enterprise installations only, which include the Repository. When you upgrade ER/Studio Data Architect you must also upgrade ER/Studio Repository to correspond with the same build date as ER/Studio Data Architect.

Log on to Windows with local administrator privileges.
Start the Repository installation program and follow the prompts. The installation program starts the following services:

Embarcadero Repository Database Server
Embarcadero Repository Event and Dispatch Server

On the Run Database Wizard? page, click Yes.
When the wizard locates your existing database, select Update previous Version Database to current version

Note: If you are upgrading from a Repository version prior to 4.0, you can delete the C:\Program Files\Embarcadero\Repository\Data directory. This directory is not used with Repository versions 4.0 and later.

Additional Resources

Licensing Your Embarcadero Technologies Product

All Embarcadero Technologies products include a 14-day trial period. To continue using the product without interruption, we recommend that you license it as soon as possible. To license your product, use the License Request Wizard found in the Help menu of your respective product. If you have not yet purchased your Embarcadero Technologies product, contact [email protected], or [email protected] for sales in the EMEA region.

Embarcadero Technologies Product Support

The Embarcadero Technologies Web site is an excellent source for additional product information, including white papers, articles, FAQs, discussion groups, and the Embarcadero Knowledge Base. Go to www.embarcadero.com, or click any of the links below, to find:

Embarcadero Technologies Technical Support

If you have a valid maintenance contract with Embarcadero Technologies, the Embarcadero Technical Support team is available to assist you with any problems you have with our applications. Our maintenance contract also entitles registered users of Embarcadero Technologies products to download free software upgrades during the active contract period. Evaluators receive free technical support for the term of their evaluation (14 days).

We encourage you to open technical support cases via the Technical Support request form at the Embarcadero Technologies Web site. For additional information about Embarcadero Technologies Technical Support, go to the Support page on our Web site.

Embarcadero Technologies on the Web

To download evaluations of other Embarcadero Technologies products or to learn more about our company and our products visit us at www.embarcadero.com.