Thank you for downloading Autodesk Topobase Client 2009 Update 1.

This readme contains the latest information regarding the installation and use of this update. It is strongly recommended that you read this entire document before you apply the update to your product. For reference, you should save this readme to your hard drive or print a copy.

Contents

• Who Should Install This Update?
• Topobase Client 2009 Update 1 Information
  • Action Required
  • General Information
• Primary Issues Resolved by This Update
  • Updates to Topobase Client 2009
  • Updates to AutoCAD 2009 and AutoCAD Map 3D 2009
  • Known Issues With This Update
• Supported Operating Systems
• Installation Instructions
  • To Install This Update
  • To Update the Topobase System User TBSYS
  • To Update the Document Structure

Update 1 is for the Autodesk Topobase Client 2009 and Autodesk Topobase Administrator 2009 components, in all languages, running on all supported operating systems.

Action Required

After the installation of the SP1, you must manually update the Topobase System User (TBSYS) using Topobase Server Administrator.

Topobase server and Client versions must match. That means:

• If you have updated Topobase System User (TBSYS) you must update all Client workstations.
• If you have updated a Client workstation you must update the Topobase System User (TBSYS).

General Information

The Topobase Client 2009 Update 1 contains updates for the following components:

• Topobase Administrator
• Topobase Client
• Topobase Electric CE
• Topobase Electric NA
• Topobase Survey
• Topobase Wastewater

Additional updates are available for Topobase Adminstrator and Topobase Web.

After you install Topobase Client Update 1, the following server and client side updates are ready to be performed:

1. Update of the Topobase System User (TBSYS) using Topobase Server Administrator. This operation loads Topobase.jar.
2. Update the Topobase document structure by opening each workspace and responding to the update prompt.

During the TBSYS update you must connect to the Oracle database. Make sure your administrator provides the password for the Oracle user with rights on SYS.DBMS_RLS and DBA rights (default “SYS AS SYSDBA”).

Updates to Topobase Client 2009

The following defects have been fixed:

Topobase Administrator

Workspace

• When you import a document with an invalid FID_MODEL value, Topobase Administrator fails to update the structure.

Topobase Client

API

• When you update feature attributes or geometry data, Topobase Client regenerates the graphics more often than needed.

Coordinate Systems

• Advanced Generate Graphics does not work correctly with Coordinate Systems.

Display Model

• When you automatically load layers and save them twice to the Display Model, the autolayers appear unchecked in the Display Model.
• When you save a Display Model twice without generating graphics between each save, the second saved Display Model contains only referenced layer files.
• When you create a new plot and deselect "Plot.tbdm" in the Display Model Combobox, Topobase Client continues to generate "Plot.tbdm".
• When you delete the BlockDefinitions.dwg in the saved Display Model folder and then generate graphics, Topobase Client crashes.
• Topobase Client changes the connection name after you generate graphics in the Display Model.
• When you drag and drop layer files into the Display Manager, the layers are not saved as links.
• Referenced layers are not used consistently. When you generate graphics and the newly saved Display Model uses read-only referenced layer files, Topobase Client crashes.
• When you restart Topobase Client and open a saved Display model to which you added raster images from a folder, the raster images do not appear.
• When you use the Save Display Manager option to save a Display Model with a different name, all features with AutoLoad checked appear unchecked.
• You cannot delete a Display Model from the ComboBox drop-down list.
• The default Display Model is not selected in the drop-down list.
• The Display Manager connection names are reset in the Display Model.
• Although the Filter check-box in the Save / SaveAs Properties dialog box is disabled, it appears checked.
• When you save a simple Display Model and name it "Default Display Model", Topobase Client does not open the saved default Display Model.
• When you generate graphics using a drawing that contains invalid layers, Topobase Base Client crashes.
• When you save a Display Model with two drawings that both include calculations in Display Manager, generating graphics fails to work.
• When you work with multi-map Display Models and a command is pending in a drawing, regenerating features and highlighting causes Topobase Client to crash.

Forms

• The SQLLabel, Combobox, and Geometry controls run queries while they are not visible.
  

Intersection

• When you calculate the intersection and change the job state, Topobase Client crashes.
• When you calculate the intersection for a feature class, Topobase Client crashes.
  

Jobs

• When you are working with larger modifications, some functions in the Job Explorer perform slow.
• When you change the job state from open to pending, you receive an error message stating that Topobase Client is no longer connected to the database.

Other

• When you use the "Display Managers Save to DWG" command, Topobase Client exports points and lines with an incorrect scale.
• Some operations in Topobase Client increase the memory consumption of acad.exe.
• When you perform geometry validation on a feature class that has a large amount of records, Topobase Client crashes.
• When you close Topobase, you will hear a "Critical Stop" sound.
• When you edit an annotation, the editing template uses the default font size and 0 for the orientation.

Plot

• When you create a new plot and enter a large value for the scale, the plot does not appear in the plot library and Topobase Client creates orphaned records in the database.
• When you create a plot with an immense scale, Topobase Client crashes.
• When you enter "0" for the number of copies in the Batch Plot dialog box, Topobase Client crashes.
• When you use a complex Display Model to create a plot, Topobase Client crashes.
• When you digitize a rectangle with a form to create a Map placeholder whose width or length is 0, Topobase Client crashes.

Schematic/Multiple Location

• You cannot create a Geoschematic in the Electric CE Technical Training document.

Working with Map

• Some raster layers do not work.
• When you use the TBExportDWG command to save a drawing with a Drawing2007 format, Topobase Client crashes.
• When you import a new point style, some controls are missing after import.
• If you reference an invalid topic, the default Display Model fails to generate.
• When you regenerate a feature that occurs outside of the drawing extrema, Topobase Client overwrites the "make selectable" option of a layer.
• Each time you hover over a point and the point is highlighted, the memory usage increases by 1 MB.
• When you zoom in to a drawing at specific scales, a line connected to an arc does not display correctly.
• When a layer file contains a named extension, the named extension disappears from the layer file and Topobase Client crashes.
• When you zoom in to a drawing, the line style changes according to the scale.
• After you apply the refresh hotfix, saving a new Display Model causes Topobase Client to crash (German language version only).
• When you create a feature from native geometry, Topobase Client crashes.
• When you zoom out of TBEXPORTDWG before you export, Topobase Client breaks the geometry.
• When you generate graphics for TBExportDWG, Topobase Client produces corrupt drawing files.

Workspace

• The amount of time that elapses when a workspace opens is longer than expected.

Topobase Electric CE

Cross Sections

• When you assign a predefined cross section to a segment, the duct geometry is not created.
• When you create a duct, an unhandled exception occurs.
• When you move a conductor to a separate duct, Topobase Client crashes.
• When you choose two ducts to create an underground conductor to them, an unhandled exception occurs.

Help

• When Label Conductors are in a batch, the insert point should be defined outside the multiple conductors.

Topobase Electric NA

Maintenance Workflow

• When you execute the Load Transfer workflow and select switch to close and open, an error message appears and the load transfer fails.

Topobase Survey

Dialog Measurement

• When you use a blank space instead of a comma as the thousand separator, a fatal error occurs (French language version only).

Wizard

• When you calculate an adjustment, the Tolerance statement of the field code distribution list causes Topobase Client to crash (French language version only).
• When you select UniversalReduction and CH1903.LV03, Topobase Client crashes (French language version only).
• When you create a network plan using a 3D Survey document in Oracle 10g and 11g, Topobase Client crashes.
• When you import the CalculationDetails report template to a survey document, Topobase Administrator crashes (French language version only).

Topobase Wastewater

Classification

• When you try to classify a section with observation data in a Live/Pending job, Topobase Client crashes.
• In data validation, some of the isybau96 codes are invalid.
• When you enter an observation code for a section/manhole and then classify it, the SkdeAuto, SkbeAtuo, and SkseAuto columns are empty.
• When you classify a section for an ISYBAU classifier that contains the observation code BAB/BAE/BAF/BAM/BAL/BAK, you receive an incorrect classification result.
• You receive an "Classification Set Error" message for codes that are valid.
• When you classify a manhole using the DAL/DAK code for the ISYBAU classifier, the observation codes in the Excel file are incorrectly classified.
• When you classify a workflow for isybau96, manholes and sections with observation data are categorized as failed and do not have any classified results in the form.
• You cannot get a complete classification result for section/manhole for ISYBAU XML, DWA, and ISYBAU 96/01.
• When you validate the imported dwa/isybau data, the observation codes appear valid, but should be categorized as invalid.

Import/Export

• End point geometry for a section feature is not exported correctly in EN 13508-2 format.
• When you create a new Wastewater import and select ISYBAU as the format, Topobase Client crashes.
• When you select to export a section with observation data, the Time Code attributes do not export correctly.
• The values for Quantification 1 and Quantification 2 Numeric are not exported correctly.

• All section observations with control code "K" are regarded as invalid.
• When you create a new import and add an arbitrary file with an .s, .k, .h, .ey, or .lh extension, Topobase Client crashes.
• When you run data validation on a section that contains the observation code BAL/BAK with standard annotation, the code is invalid.
• When you run data validation on a section that contains the observation code DAK with standard annotation, the code is invalid.
• You cannot import Bremerhaven data.

Updates to AutoCAD 2009 and AutoCAD Map 3D 2009

The following defects have been fixed:

.NET API

• When a .NET function with a LispFunction attribute has the return type as object, an exception is thrown in AutoCAD.

ADE Save Back

• When you save back edited objects in the save set, AutoCAD Map 3D crashes.

Annotation Scaling

• A drawing that contains a large number of anonymous blocks and copies of annotative entities created in AutoCAD 2007, or an earlier release, opens slowly in AutoCAD 2009.
• A scale is infinitely enumerated when you insert a drawing that contains the same scale as a block or an external reference (xref).

Attributes

• When you attempt to display a tooltip of a multiline text (mtext) attribute that contains 281 characters or more, AutoCAD crashes.
• When you move a block using an insertion grip, mtext attributes move incorrectly.
• When the default value of an mtext attribute in a block contains a field, you cannot edit the attribute text to replace the field with other data.

Blocks

• When you insert or redefine a block that contains attributes on a locked layer, AutoCAD crashes.
• When you change the scale of a block through the Properties Palette, an attribute displays incorrectly.

Calculated Fields and Intrinsic

• When the stylization rule uses a calculated property and a default style rule does not exist, selection highlighting and checked out object rendering do not work.

Display Manager

• When you add a new theme to your drawing and use global characters for the legend labels, you cannot save your drawing as an AutoCAD 2004/LT 2004 drawing.
• When you hover over a rotated point feature, a different highlighting style appears for this feature than for a non-rotated feature.
• The Legend thumbnail becomes a long line after you zoom in and out of your drawing.
• When you perform simple ACAD commands, which trigger a ACAD reactor to REGEN, AutoCAD Map 3D crashes.
• When you transform a coordinate system for FDO data, the composite line style does not display.
• You cannot link any stylization to LineString layers with more than one thematic rule.
• You cannot script the MAPEXPORTCURRENTMAPTODWG command because it does not respect the FILEDIA setting.

Export a Layout to Model Space

When you export a layout to model space the following occurs:

• The linetype scale changes.
• Dimension arrowheads do not display.
• Text does not rotate correctly.
• Drawing properties are lost.

External Reference ESW

• The External References palette does not display when auto-hidden and used with the XREF or IMAGE commands are used.

FDO ArcSDE

• When you move a drawing to another machine and open it, AutoCAD Map 3D freezes when it populates the feature cache.

FDO Connect

• When you connect to feature sources with unknown coordinate systems, long schema loading times can occur.

FDO Coordsys

• Changing the coordinate system of a map may cause performance issues and change the drawing order of the layers.

FDO Create/Edit

• The MAPFEATUREEDIT command does not work properly.
• When using the COPY command, if you cancel the check out of a large number of features, AutoCAD Map 3D becomes inactive.
• When you create a new road using an arc, you cannot check it into the SHP source.
• When you select to work offline after deleting a SHP feature, a fatal error occurs.
• When you copy a checked-out object while in 3D, AutoCAD Map 3D crashes.
• You cannot copy a feature on a joined layer if that feature has a match in the secondary table.
• OSNAP intersection does not work correctly with FDO features that are not checked-out.
• When you use the MAPLINESTRINGCREATE command, the node OSNAP does not work for some points.

FDO Raster

• When you use FDO Raster, the resolution of the image decreases compared to using the MAPIINSERT command.
• When you zoom in on a 24 bit uncompressed tiff, the alignment of the image shifts.

Geospatial API

• In the Draw Order mode, platform API reports incorrect layer group information.
• When you remove layers and reinsert them, the draw order changes.

GIS Annotation

• When you create a new annotation and add multiple '\P' codes to the label text, the space progressively increases between each line.
• The new annotation text size differs from the old stylization.
• Device context labels render at twice the expected size.
• The plot preview is inconsistent with the map drawing.
• The text features in the Quick View Layout appear larger than in the Map drawing.

GIS Display Manager

• When you paste an FDO layer into the Display Manager, the feature graphics will not display in your map.
• When the theming dialog attempts to retrieve a non-existent symbol using the index from a previous selection, an unhandled exception occurs.
• When you create a legend using sample data, the drawing fills with color.
• When you change a band in the Style Editor dialog, you must close and then re-open the Style Editor in order to change another band.
• When you edit the scale order of a drawing, an unhandled exception occurs.
• When you add a thematic rule and select a block from the symbol library as a point style, the point disappears from your drawing.
• Layers that use scale dependent line styles may use an incorrect line style in the layout view and plot preview.
• When you select Band details in the Style Editor, the first color in the palette may replace the last color previewed in the Theme dialog box.

GIS Joins

• The Expression Builder properties list does not list the joined class properties.

Hatch

• When you recreate a hatch boundary, it consists of separate line segments rather than a closed polyline.

Hide/Shade

• When you plot, objects in an xref are not correctly hidden.

Import/Export

• When you export to a Shape file, if your drawing contains a Japanese field name, AutoCAD Map 3D converts that name to English.
• When you import an object data table from AutoCAD Map 3D 2007, the order of the data fields changes.

Menu Browser

• You cannot access the menu browser in a non-English version of AutoCAD using the shortcut Alt+Key.

Multileader (mleader)

• When created on a rotated UCS, a multileader does not respect POLAR or ORTHO settings.

Multiline Text (mtext)

• When you drag and drop a drawing while the In-Place Text Editor is active, AutoCAD crashes.
• When some of the values in the In-Place Text Editor are changed, AutoCAD crashes.
• Some mtext objects with double byte characters display as a single line.

Open/Save

• When you attempt to save a file with a long file name, AutoCAD may crash.
• When you drag and drop a file from Windows Explorer into the AutoCAD title bar while in Single Document Interface (SDI) mode, AutoCAD may crash.
• When you attempt to open multiple files from Windows Explorer, only the first selected file opens.

Partial Open

• When the OPENPARTIAL system variable is set to 1, if you use the PURGE command, drawings may become corrupted.

Plot

• When you plot upside-down, an OLE object does not plot correctly.

Plot/Publish

• Some point symbols are unavailable in the map sample data.
• In the Plot Preview window, labels do not display correctly.

Polygon Object

• When you create an MPOLYGON with outer boundaries that contain arc bulges, the boundaries are not nested correctly.

Property Palette

• In the Properties palette, the Dimension Style control may display an incorrect dimension style name.

Publish

• In the Publish dialog box, the Publish To setting always defaults to DWF format even if you select a different setting.
• When you link an Excel spreadsheet to a Map object data table, you cannot publish to DWF.

Publish to Autodesk MapGuide

• When you publish a symbol layer to Autodesk MapGuide, an unhandled exception may occur.
• When you publish block symbols to Autodesk MapGuide, AutoCAD Map 3D ignores the symbol’s insertion point.

Quick Properties

• When you change the theme of your operating system while running AutoCAD and then click the Quick Properties window, AutoCAD crashes.

RECOVER

• When you open some valid drawings, you are prompted to use the RECOVER command.

Render

• When you use the RENDER command with certain drawings that contain textured object, AutoCAD crashes.

Ribbon

• When acad.CUI is loaded as a partial CUI, some buttons in the multiline text (mtext) ribbon contextual tab fail.
• On a ribbon panel, you may not be able to move items between rows.
• A ribbon panel continues to display after it is removed from a ribbon tab.
• A button image used on a ribbon panel that is loaded from a resource DLL file lacks a transparent background.
• If you transfer a ribbon panel and a tab, buttons display small.
• Enterprise, main, and partial CUI files display multiple ribbon tabs in workspaces.
• You cannot control a ribbon tab when you use more than one non-AutoCAD CUI file.
• A ribbon tab and/or menu macro may not function properly when referenced from multiple CUI files.
• If you load a CUI file that references a missing BMP file, a fatal error displays.

Visual LISP

• The AutoLISP Redraw function fails to hide or highlight objects.

ZOOM

• When you zoom while inserting some blocks, AutoCAD crashes.

Known Issues with This Update

After you apply this update, you may experience the following ribbon customization-related problems:

An Incorrect or Missing Ribbon Tab

Known Issue: When you display a ribbon tab from a partial of Enterprise CUI file, on the ribbon, the ribbon tab displays incorrectly or is missing.

Workaround: To correctly display a ribbon tab, recreate the workspace used to display the ribbon tab from scratch. Do not duplicate or attempt to update the workspace. Once you create a new workspace, set the workspace current. The ribbon tab should display correctly.

For a partial CUI file, before you add a ribbon tab to a workspace, use the Customize User Interface (CUI) Editor to change the customization group name of the file. The customization group name is represented by the uppermost node of the tree in the Customization In pane.

A Blank Image for a Command

Known Issue: On a ribbon panel, the image associated with a command defined in the Command List pane displays as a blank icon.

Workaround: To recreate a ribbon command item on a ribbon panel, delete it. Then, from the Command List pane, add the command to the ribbon panel.

This update can be used with the following:

• Service Pack 2 (SP2) and Service Pack 3 (SP3) of the following operating system:
  • Microsoft Windows XP Professional Edition
• The following operating systems and Service Pack 1 (SP1) of the following operating systems:
  • Microsoft Windows Vista^® Enterprise
  • Microsoft Windows Vista Business
  • Microsoft Windows Vista Ultimate

• To Install This Update
• To Update the Topobase System User TBSYS
• To Update the Document Structure

Follow these instructions to install this update on a single computer.

1. From the Product Support web site, download the update file.
2. Copy and unzip the Topobase Client 2009 Update 1 zip file to a temporary folder on your computer.
3. Install the Update 1 files for Client and/or Administrator on each workstation.

1. On any updated Client workstation start the Topobase Server Administrator. Click Start ‰ Programs ‰ Autodesk ‰ Autodesk Topobase Administrator 2009 ‰ Autodesk Topobase Server Administrator 2009.
2. Login as Oracle user with rights on SYS.DBMS_RLS and DBA rights (default “SYS AS SYSDBA”). Service name (SID) default is ORCL.
3. In the Topobase Server Administrator, in the Topobase System User section, click Detailed Settings.
4. Under Topobase System User Info, a red value indicates that the Topobase Server Version is not up to date.
5. Under Topobase System User, click Update.
6. Select the topobase.jar file from the \TBSYS folder and click Open.

After the update the log file (\log\Topobase.ServerAdministrator.txt) is shown.

For more information, see the Topobase Installation and Configuration Guide.

1. You can update the document structure from any workstation. Start Topobase Administrator.
2. Open each workspace.
3. When prompted to update the document structure, click Yes.

   Although the Topobase document structure is updated automatically when a user logs in, we recommend that the administrator perform this operation manually.

Copyright ^® 2008 Autodesk, Inc.