Thank you for downloading Autodesk Topobase Client 2010 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 2010 Update 1 Information
  • Action Required
  • General Information
• Primary Issues Resolved by This Update
  • Updates to Topobase Client 2010
  • Updates to AutoCAD 2010 and AutoCAD Map 3D 2010
  • 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 2010 and Autodesk Topobase Administrator 2010 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 2010 Update 1 contains updates for the following components:

• Topobase Administrator
• Topobase Client
• Topobase Wastewater
• Topobase Electric
• Topobase Survey

Additional updates are available for Topobase Web.

After you install Topobase Client Update 1, the following server side update is ready to be performed:

1. Update of the Topobase System User (TBSYS) using Topobase Server Administrator. This operation loads Topobase.jar.

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 2010

The following defects have been fixed:

Topobase Administrator

Topology

• Area topology checker now handles all topologies with arcs as expected.
• Area topologies that use filter expressions are now updated as expected.
• Initializing topologies with the option "Create Logfile Of Topology Errors" enabled now works as expected.

Other

• Creating a schema line feature class with a long name no longer causes the program to fail unexpectedly.

Topobase Client

Display Model

• Saving a Display model that uses a block from a file that is no longer available no longer causes the program to fail unexpectedly.
• Saving a Display model that has invalid settings no longer causes the program to fail unexpectedly.
• Invalid layer files no longer cause the program to fail unexpectedly.

Export to DWG (TBEXPORTDWG)

• Polygon fill pattern is now saved.
• Exporting labels where the stylization properties have been changed no longer causes the program to fail unexpectedly.
• Exporting point layers with symbols from external DWGs no longer causes the program to fail unexpectedly. Note that the export might take some time.
• Exporting multiple layers of the same feature class now works as expected.

Interlis Import

• Vertical alignment values, special characters (ä, ö, ü), and labels with long names are now imported as expected.

Intersection

• Intersections that are performed when the job state changes now work as expected.
• Intersections of features with arc geometry now work as expected.
• Intersection on specific circumstances with data (2 points are equal on the result of the intersection) no longer causes the program to fail unexpectedly.

Other

• Highlighting of features on layers that use views now works as expected.
• Highlighting of selected features that have a schematic representation now works as expected.
• Refreshing graphics after updating features from feature classes where the parent column is not the primary key no longer closes the program unexpectedly.
• COGO - Inserting a point into a line where the points before and after the insertion point belong to different feature classes now works as expected.
• COGO - Inserting multiple points into a line now works as expected.
• Editing centroids of an area topology that use filter expressions now works as expected.
• Saving the current map to DWG now works as expected.
• Editing features on autoload layers with some OSNAP options now works as expected.
• Stability of the Redland.NET library has been improved.

Plot

• Editing features in a DWG that has been created by Topobase Plot now works as expected.
• Using plot templates with the Plot To File Settings enabled now works as expected for batch plots, if you specify a single printer.

  NOTE: In TB_SETTINGS, use the variable (ITEMTHEMA=TOPOBASE.PLOT, ITEMKEY=FORCEPLOTTOFILE, ITEMVALE=0/1), if you want to specify a batch PDF printer that is different from the PDF printer for the single plot, but want to use the output file name from the single plot.

Topobase Electric

• Find Fed Devices for transformers now works as expected.
• Find Connected workflow with the option "Always Display Highlighted Features" no longer causes the program to fail unexpectedly.
• A duct in a scaled cross section now has the same scale as the segment cross section.
• Creation of conductors in cross sections of different types now works as expected.
• Using COGO tools to split or to join a conductor no longer causes the program to fail unexpectedly.

Topobase Survey

• In the Wizard, step 7, updating the A-Priori Standard deviation now works as expected.
• The Result dialog displays the NB, NA values as expected.

Topobase Wastewater

Classification

• ISYBAU 2006 classification now handles invalid observation codes as expected.

Import/Export

• EN 13508-2 data validation now differentiates control codes for manholes and sections.
• When you close the Import dialog during the import, you must not close the dialog again, while the data is rolled back. A message alerts you "The window will be closed after data is rolled back. It may take a few minutes."
• Material values from ISYBAU 96/01 files are now imported correctly.
• Site observations, and site features are now imported correctly.
• Import can now be started if the main document contains read-only feature classes (views).
• For ATV files that use EN coding, the coding system is now imported correctly.
• Import of ATV files (EN coding, or 96/01 coding) now works as expected.
• Import of ISYBAU 96/01 *.S files containing manholes without SI3 records no longer causes the program to close unexpectedly.
• Import of ISYBAU 96/01 files containing incomplete inspection data no longer causes the program to close unexpectedly.
• Importing inspection data on a computer with German (Germany) local settings no longer closes unexpectedly.
• Import of ISYBAU 96/01 inspection pictures now works as expected.
• During import validation, invalid ISYBAU 96/01 *.k files no longer cause the program to close unexpectedly.

Inspection

• Inspection Editor: Fixing Single Damages (create a relation between rehabilitation and WW_SECTION) now works as expected.
• ISYBAU 96/01 classification values can now be imported.

  NOTE: If the import file contains classification values, the import sets the value CLASS_VALUES_WRITE_PROTECTED to true (1). If this flag is set the classification algorithm will not overwrite the imported classification values.

• Inspection videos / pictures for manholes can now be imported.

This update includes the resolution of the following issues:

General

• Creating vector layers no longer causes a memory leak.

64-bit

• An issue with the IRD module of ADE on a 64-bit operating system has been resolved. The program no longer closes unexpectedly if it has been running for a long time or the user has loaded a large data set that results in a higher address value.

ADE Query

• The <F1> Help button for the Data Condition dialog box now works as expected.

CAD on GIS

• The following issues with overlay scalability have been resolved.
• Previously, when you used overlay the program closed unexpectedly.
• Using Intersect Overlay on the Harris data set with zipcodep and parcels layers no longer causes your map to disappear.
• Using overlay on the complete Harris County database no longer causes the program to fail unexpectedly.
• Overlaying PARCELS.shp with FLOOD.shp no longer results in a loss of feature data.
• Overlaying files with dense data no longer causes the program to close unexpectedly.
• Doing an intersection overlay on the Walton County .SHP file now works as expected.
• Doing an overlay analysis on an intersection now works as expected. You no longer receive a message stating that you do not have enough memory to complete the analysis.
• The X marker now displays the correct value in non-WCS.
• A feature that is joined to a source is no longer deleted when it is from a different feature class.
• Editing primary table attibutes that are not part of a joined layer now works as expected.
• The Ignore Rules setting in the Split/Merge group now works as expected.
• An issue with opening the Overlay Input dialog box has been resolved. Previously, the layer and feature class settings did not display and the program closed unexpectedly.
• Clicking the vertex layer of a multipolygon no longer causes the program to close unexpectedly.

COGO

• When you use the MAPCGSETUP command, the Create Text Log checkbox is now selected as the default status.
• The number of temporary point symbols that display is now the same as the temporary symbols of the resulting point.
  

Display Manager

• Using the REGEN command while setting up a plot no longer causes the program to close unexpectedly.

FDO Display Manager

• Advanced placement now displays all map labels.
• A performance issue with turning off all 150 layers in an Electric_NA has been resolved. Previously, selecting all layers and turning them off caused the program to run slowly.
• Loading a layer file with joined layers no longer causes the program to close unexpectedly.
  

FDO Oracle

• Disconnecting a RDBMS data store with an empty feature class and then clicking Maximize/Restore Down no longer causes the program to close unexpectedly.
• An issue with loading a dump file and connecting to the schema has been resolved. Previously, some of the schema features did not display correctly and the data set was unusable.

FDO Raster

• Converting a new image to a grid layer no longer causes the program to close unexpectedly.

FDO SDF

• Recreating an SDF spatial index on an existing SDF file now works as expected.

FDO SHP

• Deleted rows no longer appear in the data source.

FDO SQL Server 2008

• Connecting to the bikeway data source no longer causes the program to close unexpectedly.

FDO WFS

• Connecting to a WFS server now works as expected. The FDO WFS provider now retrieves all the feature classes from the server.

GIS Joins

• Previously, when you selected Preview before launching the Context Menu, and then created a join between layers with multiple objects the program closed unexpectedly.

Import/Export

• An issue with exporting object data points has been resolved. Previously, the point type data column did not contain any data.
• When you connect to a DGN file the program now imports the correct values for ms_link and entity_num.
• After importing a DGN file, all characters are displayed correctly.

.NET API

• Selecting MgLayer.Selectable now works when calling MgLayer.ForceRfresh().

Schema Editor

• Importing a schema while creating a SDF file now displays the correct attribute values.

Survey

• Adding bulk copied survey data to your map now works as expected. The data store structure displays in the Survey tab.

2D Drawing

• If the PLINETYPE system variable is set to 0, STRETCH does not work as expected on arc segments of polylines.
• When the PLINETYPE system variable is set to 0, the closing point of a polyline with segments of different widths do not display correctly.
• If you use the JOIN command on splines, a duplicate control point is inserted.
• When you use the JOIN command on multiple polylines, AutoCAD may crash.

3D Modeling

• When you open a drawing that contains solids, some solids display briefly and then disappear.
• If a grip on a mesh face, edge, or vertex is highlighted and you use the ViewCube, AutoCAD crashes.

3D Navigation Tools

• When you use the 3DORBIT command, you cannot orbit correctly. You can only orbit around a single pivot point and you cannot orbit around a specific object in a large group of objects.

Action Recorder

• An Action Recorder macro created in AutoCAD 2009 may fail to run in AutoCAD 2010.

Annotation Scaling

• When there are xrefs in a drawing, changing annotation scales takes a long time.
• When an annotative style multiline text (mtext) is rotated or surrounded by a hatch, the boundary box does not display correctly.

Blocks

• When you turn off the display of an attribute with a visibility parameter in a dynamic block, the Enhanced Attribute Editor lists attribute prompts incorrectly.
• You cannot copy an object from an AutoCAD 2009 drawing and paste it as a block into an AutoCAD 2010 drawing.
• You cannot use the Properties palette to set the value of a action parameter to 0.
• When you delete a constraint parameter from a dynamic block, AutoCAD may crash.
• You cannot stretch some dynamic blocks as expected.

Check Spelling

• When you run spellcheck on uppercase words, AutoCAD may crash.

CUI

• When you save a workspace, if the Enterprise CUIx file is read-only, AutoCAD crashes.
• Toolbar flyouts close unexpectedly.

Data Extraction

• When you use Data Extraction to extract the value of a block's multiline attribute into a table, text formatting code displays in the table.

DGN Support

• When a DGN file is imported, some attributes are missing.

Digital Signature

• When you open a drawing, the Invalid signature dialog box may display even if the digital signature is valid.

Dimensions

• You cannot create an angular dimension between two lines in different XY planes.

DWF

• When the background color in AutoCAD is black, some DWF underlays do not display correctly.

Dynamic Dimensions

• When you use the COPYBASE command with Dynamic Input on, AutoCAD crashes.

Export Layout

• When you use the EXPORTLAYOUT command on files in which Standard styles have been renamed, AutoCAD crashes.

External References

• You may not be able to bind multiple xrefs that include nested xrefs.

File Open

• When you try to open a drawing file from a FTP site, AutoCAD may crash.

Find and Replace

• If you use Find and Replace, autonumbering is deleted.

General UI

• On the status bar, the model or paperspace button may be missing, even after you have repeatedly turned it on.

Graphic System

• When the background color is changed in an active paperspace viewport, the cursor disappears.
• After you plot a drawing in AutoCAD, if you lock Microsoft Windows and then unlock it, AutoCAD may crash.

Hatch

• When you turn off the current layer while grip editing a hatch boundary, AutoCAD crashes.
• When the UCSVP system variable is set to 0, hatched objects align with the WCS rather than the UCS.
• When you grip edit a hatch with an elliptical boundary, AutoCAD crashes.

Image

• When you attach some TIFF images, AutoCAD crashes.
• TIFF images may not display correctly.

Inquiry Tools

• The AREA command fails on some polylines.

Keyboard Modifiers

• When temporary overrides are enabled, keyboard input using the Shift key may not display on the command line.

Layers

• Xrefs on locked layers do not display faded as expected. The LAYLOCKFADECTL system variable fails to alter them.
• When you delete a certain layer, all layers may be deleted.
• On the ribbon, the Layer drop-down does not display layers based on the current layer filter.

Licensing

• When you set your system time back more than 2 days, your license is broken.
• When you use a proxy server for internet access, the License Transfer Utility fails.

LiveUpdate

• When you have Autodesk 2009 and AutoCAD 2010 installed side-by-side, LiveUpdate does not work in AutoCAD 2009.

Measurement Tools

• When you use the MEASUREGEOM command, the tooltip and command line results are different. The tooltip result is incorrect.
• When you use the DIST command in model space, the results at the tooltip and the command line are different. The tooltip result is incorrect.

Migration

• When you export certain profiles, AutoCAD crashes.
• When you save certain profiles migrated from AutoCAD 2009, AutoCAD 2010 crashes.

Multileader (mleader)

• When you mirror mleaders that contain blocks with multiline attributes, the mirrored attributes are incorrectly justified.

PDF

• When you plot a drawing as a PDF file, the layer order is not alphabetized as expected.
• When a drawing that contains layers with names that include special characters is exported as a PDF, it cannot be opened.
• When you attach a large PDF file to your drawing, or try to attach it and then cancel the operation, performance is slow.

Publish

• When Windows XP is set to Windows Classic theme, on any Asian language version of AutoCAD 2010, if you use the PUBLISH command, AutoCAD freezes.

Purge

• On Windows Vista, in the Purge dialog box, when you attempt to use the Ctrl or Shift keys to select multiple items, the first highlighted item is de-selected.

QUICKCALC

• Calculations performed by the QUICKCALC command may be incorrect.

Recover

• When you use the RECOVER command on a AutoCAD 2000 formatted drawing file, polylines and splines in the drawing are deleted.

Reference Edit

• When you use the REFSET command, you can only add one instance of a block to the reference set. Other instances are rejected and an error message displays.

Ribbon

• Text styles from an attached xref display in the Ribbon text style control.
• When you switch between AutoCAD Classic and other workspaces (for example, 2D Drafting & Annotation or 3D Modeling), performance becomes slow.
• Layers with a VP Freeze for a viewport indicate the VP Freeze status even when the viewport is not active.
• When you click the File menu in the zero doc state, AutoCAD freezes.
• After you unload a partial CUI file, a tab remains on the ribbon. If you click the tab, AutoCAD crashes.

Section & Flatten

• When you section solids through API, multiple memory leaks occur.

Seek

• The SHAREWITHSEEK command may not work if the port used to communicate with Seek is blocked by a firewall.

Snaps

• When you snap to the grid, there may be a slight offset from the grid.

Visual Lisp

• When you use the CECOLOR system variable, the value returned by using the Getvar function is incorrect.

UCS

• In AutoCAD 2010 German, you cannot use ribbon controls to modify coordinates.

Xrefs

• With the XATTACH command, you cannot select multiple xrefs.

 

Known Issues with This Update

Supported Operating Systems

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

Installation Instructions

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

To Install This Update

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

To Update the Topobase System User TBSYS

1. On any updated Client workstation start the Topobase Server Administrator. Click Start > Programs > Autodesk > Autodesk Topobase 2010 > Autodesk Topobase Server Administrator 2010.
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.

To Update the Document Structure

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 ^® 2009 Autodesk, Inc.