OSPInSight OSPM-Edit 6.52 Release Notes

30/Mar/2006

NEW FEATURES

1- On the Options->Display Options form, on the Treeview tab, there is now an option to export the original line colors to Google Earth.

2- The Export to Google Earth feature now has the option to export data from only a certain region of the network, rather than the entire network. Select your regions (if you are drawing them, we suggest using the Cosmetic layer) on the map, then open the Export to Google Earth form, select the Export Region checkbox, then click Export. Note that you can select multiple regions by holding the Shift key when you click the regions.

3- An Export Map Selection to Google Earth option has been added to the Tools dropdown menu, that will export whatever is selected on your map. You can use the Select tool to highlight multiple objects (on only one layer at a time) by holding down the 'Shift' key while you click. Alternatively, you can use the SQL Select... feature under the Query menu, in combination with the Data Linker to create complex selections and export them to Google Earth. This feature will give users quite a bit of flexibility on the data they can provide to third parties. The export information will be logged in the log file (accessible through the Export to Google Earth form), and you can cancel the process click pressing the 'ESC' key.

4- The Data Linker tool has been updated to allow users to create linked layers with points and regions, as well as create a linked layer for only a specific region. There is also a log file.

5- A 'Disabled' checkbox has been added to the setup, allowing users to disable the workspace without removing the path.

TIPS

1- If you have a large amount of data to export from OSPInSight to Google Earth, it exports somewhat faster in OSPInSight View, due to using MapX rather than MapInfo Professional.

2- If your 'Map' dropdown menu disappears, click the map for it to reappear.

3- You can have the coordinates of the cursor location displayed in the status bar, whenever you move your mouse. In the status bar below the mapper, you can display your Zoom Level, your Map Scale, or your Cursor Location. To select which information to display, click the Map dropdown, then Options. In the Options window, there is a section called "Display in Status Bar". If you want to see your coordinates on the status bar, select the "Cursor Location" radio button. Also note, on that same Map Options form, there is a "Display Coordinates" section, where you can set your coordinates to display in Degrees Decimal, or Degrees Minutes Seconds.

ERRORS RESOLVED

1- Edit was calling MapX code when performing a Push or a Pull in the MapPoint View. This would cause an "ActiveX component cannot create object" error.

2- The Hardware/Materials editor will now verify that cable types have more than 0 fibers.

3- If there was no slack at a frame, enclosure or slack in the spanlength section of a cable span (if the 'in' and 'out' values were the same on a row), a message would indicate that the slack amount was zero, and wouldn't update the totals.

4- The splice schematic was showing incorrect information if a spliced cable didn't end in a slack, enclosure or a frame.

OSPInSight OSPM-Edit 6.5 Release Notes

8/Feb/2006

NEW FEATURES

1- Export OSPInSight layers to Google Earth

OSPInSight layers can now be exported to a .kml file, and then opened in Google's satellite photo application, Google Earth. Simply select the layers you want, click export, and they will open in Google Earth.

Usage

a. Install Google Earth. You can get it from here: http://earth.google.com/downloads.html

b. Load your network in OSPInSight

c. Right click a category or individial object in the Treeview and select "Export to Google Earth", or click Tools-> Export to Google Earth

d. Right-click the grid to invert which layers are selected.

e. The Export to Google Earth form shows how many objects are on each map layer. After the export, it also shows how many were successfully exported. Any that failed to export correctly will be listed in the log file.

f. Click the 'Save Settings' button to save the path for the KML file, as well as the layer selection. You can save the layout (window and column size, and position on screen) by pressing ctrl+s.

g. The "Open KML in Google Earth" button will open a previously exported .kml file in Google Earth, making it so you don't have to wait through the export process again.

h. During the export process you can click the 'Quit' button, to skip to the next layer, or to quit the export process altogether.

i. When you close Google Earth after loading your OSPInSight layers, you will receive the message 'You have unsaved items in your "Temporary Places" folder. Would you like to save them in your "My Places" folder?' We recommend always responding 'No' to saving the exported layers in Google Earth. If you have a large network, and it takes a significant amount of time to export your network data to Google Earth, you can simpy use the "Open KML in Google Earth" button to open a previously exported KML file.

j. Google Earth can be run in DirectX or OpenGL mode. OpenGL is the default mode, but requires more graphics memory, and a more powerful graphics card. On the Google Earth support page they have the following note: "DirectX users will not be able to view line width." In other words, all lines will appear to be 1-pixel thick, even if you change the display options to thicker. You have to go to Tools->Options->View (in Google Earth) and select OpenGL as the Graphics Mode in order to see thicker lines.

k. After your selected layers have been exported successfully to a .kml file, if Google Earth fails to open, or gives an error, then it isn't necessary to wait through the export process again. In the "Google Earth Export" form in OSPInSight, click the button to the right of the file path, that shows the tooltip "Open KML file in Google Earth".

l. You can increase the zoom speed in Google Earth, as by default it zooms to view your network rather slowly. In Google Earth click Tools->Options->Control, and alter the Speed slider.

2- 'B' checkbox column added to the Display Options->More, so you can highlight certain fields in editors. The 'V' column determines if that field is visible.

TIPS

1- MapInfo has added a couple of very useful features as of MapInfo Professional version 7.5.

a. The first is the ability to modify the Snap Tolerance, which is how near your cursor needs to be to an object before it will snap to it. The default is 5 pixels, and as you increase it, the circle around the tip of your tool will increase to show you the snap area. Turn your Snap tool on or off by by selecting the map and pressing the S key. Modify the snap tolerance by clicking Options->Preferences->Map Window, and changing the value for Snap Tolerance.

b. The second is the Crosshairs feature. This feature will give crosshairs that extend to the edge of the map, making it very easy to line things up while drawing. To turn your crosshair feature on or off, make sure the map is selected, and press the C key.

ERRORS RESOLVED

1- Document/Relationship editor's browse buttons weren't disabled before clicking 'modify'

2- Clicking Open for a Document object that was related to a folder (rather than a file) would give an error, and open the wrong folder.

3- Messages have been added to the setup to make it more apparent how the Golden and Backup directories are used.

4- The equipment attached to a jack now displays in the Fiber Panel/Info tab, in the 'patch' field

5- The pwr.loss field in the database was an integer field; thus, if a user input non-integer values for the 'loss' in the Fiber Panel->OTDR tab, they would be saved incorrectly. OSPInSight will now convert the field to a 'double'.

6- Relations for Rings (cable span) were showing only one span, regardless of the number of spans that were actually part of that ring.

7- The columns were offset when exporting the splice spreadsheet report to Excel. We recommend using the Excel 8.0 (XLS) format when exporting from Crystal, rather than the Excel 8.0 (XLS) Extended.

8- While terminating fibers, a message saying: "Choose a different value, not enough positions" would sometimes innappropriately appear

9- The variable that stored the number of layers when printing was previously a BYTE, causing an overflow error if there were more than 256 layers open. The variable has not been changed to an Integer

10- A "Key is not unique in collection" error was displayed when finding relations on a cable span that was attached to a pole

11- In the Query form of the Installed Materials/Hardware report, selecting specific columns rather than using an asterisk in the Select field would generate an error: "Item cannot be found in the collection corresponding to the requested name or ordinal."

12- If no specific layer was specified as the text layer, OSPInSight would by default use the *TXT.tab layer for text, but wasn't showing that in the Edit Options->Misc Options tab. Also a tooltip was added to that field.

13- OSPM Edit failed to give a message when there were more terminations for a frame than there were ports. It now gives a message when you open the fiber panel.

OSPInSight OSPM-Edit 6.07.1 Release Notes

07/Nov/2005

ERRORS RESOLVED

1- On some computers the 6.07 executable would fail to load any networks, due tof an issue with OSPInSight looking for MapX

OSPInSight OSPM-Edit 6.07 Release Notes

02/Nov/2005

NEW FEATURES

1- A pole attachment editor has been added, that will add one attachment record at a time to all poles in a selected region. Be careful with it, as there is no roll-back feature at this point.

In order to use the Pole attachment feature:

a- Open a pole editor

b- Select an existing, or create an attachment record you wish to add to other poles

c- Draw a region on the map around the poles you want to update, I would suggest on the animosp layer

d- Select that region

e- Click the Region button in the Pole editor, then click Attach

2- A Plant Layers tab has been added to the display options, so that users can specify which layers they would like to have visible or invisible when loading a network, without adding them to a workspace.

3- The Display Options->More tab has had an additional column added to it, so that users can now see both the display captions and the database field names simultaneously.

4- When orphan objects on a map layer conflict with new database object input, the input is rolled back, a new more informative message is displayed, and the orphaned object, that needs to be taken care of, is mapped.

5- An option has been added to the Splice Key editor, that allows users to hide fibers that are part of an existing Ring (Termination) record. Hence it is easier to avoid breaking existing records if you have some conflicting data.

6- A Midsheath Integrity/Rollback feature has been added

7- Per customer requests, the scale factor is now only automatically changed to be '1' if it is left at zero. If a user has some specific reason for entering 0.92 as the scale factor, that is now possible.

8- Case sensitivity for user names has been dropped

9- Print Options have been added to the Taper report, so now instead of only having the option of printing through Crystal Reports, you can also print to a generic grid or export all the data to a TAB-delimited text file (which you can then open in MS Excel, or other applications).

TIPS

1- It is possible to section your network map into a grid, and print the entire grid, 1 section per page, from OSPInSight. With the OSPInSight data linker you can add labels also. Below are steps that would include layers for access points and cable.

a. Use the Map->Data Linker tool to create thematic layers for Access Points & Cable

b. Move the layers to the appropriate position in the layer control

c. Configure labeling options for those two thematic layers

d. Zoom to the area you want to print

e. Click Window->New Layout Window, select One Frame, and OK

f. In your layout window, use your zoom tool to zoom out to the paper size you want on the rulers

g. Resize the image to correspond to your paper size

h. Click File->Page setup, and change the paper size to match your printer paper. Select your orientation too...landscape or portrait, if applicable.

i. Print from the file menu.

2- You can add new rows to the database through the lists...by typing in information in the bottom row except for the primary key. When you hit 'update' the primary key field should auto-populate based on a trigger or autoindex, if it is numeric. In the Slack Loop/Lines list you can actually edit the objectid field.

3- The backup feature in OSPInSight has been modified somewhat. The following is a summary of the actions of the backup utility in each folder:

*working directory - OSPInSight copies *all* files from the folder where you edit your network, to the backup directory

*backup directory - OSPInSight will now zip only the network database files in this folder, and place them in the archive folder before overwriting them with the new backup. The archive feature will now ignore other files

*Archive directory - OSPInSight will place zip files in the Archive folder that contatin *only* the network database files.

ERRORS RESOLVED

1- IMPORTANT: Inserting a slack object into the middle of an existing cable (midsheathing) would generate an incorrect distance for one of the new shorter cable segments...leaving it the length of the entire previous segment, but only if you are using the Map Distance. If you believe this has introduced incorrect distances into your network database, contact Advance Fiber Optics technical support department, and we will help restore the correct cable distances.

2- Deleting terminations with an apostraphe in the Group field was unsuccessful, usually with an error about attached equipment

3- If the 'opticallength' field was not checked as visible in Options->Display Options->More->Cable Spans, then the field was not populated at all when inputting Spans. If your database has 0 as a value for records in the span.opticallength field, contact Advance Fiber Optics Technical Support, and we will provide a utility to update the span.opticallength field based on the span.total field for that span.

4- When opening tables from a microsoft access database (such as the .ntk) in MapInfo, MapInfo will sometimes add a MapInfo_ID field to those tables. Modifying the data structure causes problems on insert, update, select and other statements. OSPInSight now automatically checks for and removes the MapInfo_ID fields in tables where they will cause errors.

5- A difficult-to-resolve midsheath error, that caused splicing on one end of the cable to not be updated, has been fixed. A pre-midsheath span integrity check has been added, that checks splicing on both ends, as well as on all the map items, has been added. A post-midsheth integrity check has also been added. If any integrity problems are found or introduced, the entire operation will be rolled back.

6- Unique constraint error generated when updating fields in the Fiber Panel rapidly has been resolved.

7- The Equipment.endq fieldsize has been increased to 20, to avoid certain migration errors.

8- Labeling database objects (buildings, access points etc.) with the getinfo tool where one the fields being labelled had a null value caused an error.

9- Mapping Rings (Terminations) from the Relationships window would give a 'no items selected' message, and not map the ring

10- Grouping the Ring (Terminations) by any field, then finding relations for a frame or span or termination in the treeview related to any Ring(Termination) gave an index out of bounds error.

11- Leased Path Editor was failing under certain circumstances, due to ordering in the database.

12- When using the Change Group form in the Terminations list, if you leave the Start # field blank or with a 0, the 'fiberid' field for those terminations remains unchanged.

13- Editing a field then using the arrow keys in the spanlength grid in the Cable span editor would lose focus up to the top section of the cable span editor.

14- If new fields had been added to the database with spaces in the field name, using the Quick Add feature would fail on those tables. OSPInSight now automatically adds brackets around any field names with spaces in them.

15- New layout window form was cut off.

16- Midsheath operations were being queued, rather than immediately committed. Hence if OSPInSight crashed after midsheaths, the map changes were retained, but the non-map (database) edits were lost, causing orphan and incorrect map objects.

17- Select getinfo tool, click an enclosure, when it asks if you would like to label splicing, select another application that is running...then switch back to OSPInSight: Run-Time Error was generated, and the application would crash.

18- After performing a midsheath with an enclosure, the 'Tray' field was left null...which caused errors when attempting to run the splice spreadsheet.

19- Rings (Cable Spans) weren't correctly captured when manually selecting spans on the map.

20- Printing from the fiber panel would give incorrect Status values

21- Using the quickadd feature for duct left the temporary polyline style, rather than the defined duct style

22- Attempting to perform a midsheath directly over a node would cause this error "Found [,] while searching for [A string constant]. Alter Object Node Add failed." Now a message appears saying that a midsheath cannot be done right on top of a node, and to retry.

23- An aggregate function error occurred if you selected EA1 as the 'Display field' for "Ring (Terminations)" In Options->Display Options, on the Treeview tab

24- Changing a customer name from 'cust:1' to anything else changed the name of a different existing customer

25- In the Lit fiber length report, there was a math error when you switched units

26- Initiating an enclosure midsheath in Oracle, then canceling when the editor appears left the new enclosure record in the enclosure table, though the cable was not split, nor was the map object left on the ENC layer

27- Attempting to map a document from the treeview generated a "Object variable or With block variable not set" error. Now the associated database objects are mapped sequentially.

28- When opening the lists a “disconnected from client” error or "Automation error The object invoked has disconnected from its clients"would frequently appear. OSPInSight will re-establish the database connection now.

29- Changing the capitalization only of an object name (building, enclosure, etc.) would fail; a message would say that that object was already in the database. For example, if a user accidentally named an enclosure or a frame something like

'FRame-1' or 'ENclosure-1', and wanted to change it to 'Frame-1' or 'Enclosure-1', it was necessary to rename the object some intermediate name.

KNOWN ISSUES

1- When printing the map from View with MapPoint as the background, the printout is dark. Also, the print form takes a long time to close

2- Some forms when closed return focus to a different application, other than OSPInSight. It is necessary to re-select OSPInSight

3- When using Microsoft Mappoint as the background, the Back and Forward functions on the map don't always work the first time

Solution: Sometimes the Back & Forward entries on the right-click menu must be clicked twice to do anything

4- Any Equipment records that have an invalid TypeID value (such as 'none' when that is not in the TypeID list) will not show up in the "Customers/Equipment Report".

Solution: If you suspect that the report is not displaying all of your customers or equipment, open your Equipment List or Equipment/Customer Editor in OSPM-Edit and update the TypeID values such that they all correspond with an entry from the TypeID list (from the Hardware/Materials Editor)

6- Currently in the schematics, the Span/LocateID text dynamically resizes to fit the "span" field and not overrun the "fiber" field. However, it still isn't perfect, and depending on how big the form is, it will still run into the next column a little.

Solution: If there is some text overlap, simply resize the form until the text in the span column is not conflicting with the text in the fiber column.

7- When using MapPoint as a background (or when any Raster image is loaded in MapX), zooming in past 0.1 miles will typically invert the mapper. Labeling will also behave oddly at this zoom level with any raster images displayed.

Solution: There is currently no known resolution to this issue.

8- Sometimes you will see odd window/column behavior in the Ductbank Cross section editor.

Solution: Reset the layout for that editor:

OSPInSight OSPM-Edit 6.06 Release Notes

24/Jun/2005

NEW FEATURES

1- The Setup form has been updated to make it's use more intuitive

2- The Route highlight has been moved from the animosp layer to a new layer called 'mapping', allowing users to click objects, open editors, map items, etc. without losing route or cable highlights. By default the route/line highlight is yellow, however this can be changed. Open your layer control, select the "Mapping" layer, click "Display", and change the Style Override to be the color, thickness and line-style you want for your route highlight. To save this change for other sessions, exit your layer control, click the Options->Display Options dropdown, and on the Treeview tab, click the "Save Highlight Style" button. (Note: you must map a cable or ductbank before you can set the Mapping layer display style)

3- It is now possible to designate any layer open in the session as your "Text Layer", which will be made editable when the Text tool is selected. In order to define a Text Layer, open the Edit Options dialog, select the Misc Options tab, then choose your text layer in the Text Layer dropdown.

4- In the Editors, users have the option to cycle through either the fields or the sections when pressing the TAB key. This behavior can be changed by pressing Ctrl+t, but by default the focus in Editors will be moved from field to field by using the TAB key. The same option has been implemented with lists, where the focus also goes from field to field by default. **Important** After you change the TAB key behavior in a list or an editor, you must press CTRL+s to save that behavior, in each list or editor.

5- The "Create Multiple Pole" feature now allows you to create multiple poles along a polyline that are all an equal distance apart, or at a specific distance from the previous pole.

6- When you use the GetInfo tool to label map items you now have the option to display field names as well as the field value. This can be turned on in the Options->Labeling... form by selectiong the "Label Fields" checkbox.

TIPS

1- If you are required to enter a password to get into your setup but would like to remove it, the setup password can be disabled by clicking the "Choose Setup.mdb or Admin.mdb" button in the setup, then clicking the "Change Password" button, and selecting "OK" while the form is still blank.

2- If a list is not saving changes, or a report is not displaying correctly, or an editor is missing a field, then reset the Layout for that form. Click Options->Display Options, then click the Layout tab. Find the checkbox for the form that you wish to reset, check it, then click the "Reset Layouts" button. Use this form to reset the layout of lists, reports or editors where you see any behavioral problems as a first troubleshooting step and possible resolution.

3- Microsoft MapPoint maps can only be used as the background in OSPInSight if the network layers (CAB, BDG, POL etc.) use NAD83 as the projection, because MapPoint uses the NAD83 projection. If you attempt to use a different projection, the MapPoint background typically won't display at all.

4- If you are using MapPoint as the background and it doesn't display, or the Visible check mark is pink in the layer control, then there is likely a MapInfo option that is interfering with the MapPoint display. In the dropdown menus click Options->Preference->Map Window. In the Map Window Preferences, uncheck the option "Automatic Raster Zoom Layering"

5- Remember that after performing a find route or highlighting a span, in order to get rid of the highlight click the Red 'Unselect All' button on the toolbar, or click 'Map->Clear AnimOSP Layer'

ERRORS RESOLVED

1- Changing the name of an enclosure during a midsheath operation caused the error "You cannot add or change a record because a related record is required in table 'enclosure' " to appear, and the midsheath to fail

2- Tools->Tool Manager now stores records and paths for each user, rather than overwriting other users entries. This allows multiple users working on the same network to use the same MapBasic tool

3- The End Point schematic was displaying incorrect SpanID's.

4- The 'Change View' form wasn't opening when selected from the Map dropdown menu

5- Displaying the LocateID in the Endpoint Schematic was not very legible. It has been improved but you still might see some overlay. See Known Issue #6 below

6- The 'ea6' field was not included in the default query for the Building List

7- Reordering lists by a column would reset the horizontal scroll bar back to the left, forcing the user to relocate the column

8- If a user opened a fiber panel, made the form wider and closed it without saving the layout, then the next time it opened the columns would be incorrectly sized

9- The Taper Report's layout was not resetting correctly when Options->Display Options->Layout->Taper Report was selected and the 'Reset Layout' button was clicked

10- The option to map innerducts from the relations window was removed, as selecting it generated an error

11- Clicking in the Relationships section of Treeview caused a Run-Time Error if no Relationships were displayed yet in that session

12- The "Lit Fiber Report", which calculates the length of fiber attached to equipment, was giving an incorrect, and sometimes inconsistent result.

13- The Legend and Port colors for the Fiber Panel Graphic tab are working.

14- The "More Info" section of the Treeview displayed incorrect data in the n_superducts and n_innerducts fields

15- In the Regional and Language Options form for Windows, if your 'Standards and formats' selection was set to Portuguese (Brazil), and your 'Location' selection set to Brazil, the slack midsheath function failed in OSPInSight

16- Using the getinfo tool or the Edit Items tool to click on a group of objects that included a DOC layer object would display incorrect results. The DOC layer object did not have it's own row in the "Multiple Objects Selected" window, but the objectid of that DOC object would be appended to another object's entry.

17- When creating a new Reel, ReelID changes were not permanently saving

18- In the Display Options->Layout tab, there was an entry "enclosure key editor" that was changed to "splice key editor"

19- If an older version of a hardmatdata.ini existed in the settings folder, adding a new cable type and typing in the 'typeid' field would cause OSPInSight to immediately crash.

20- In the Hardware Materials editor, the Reel Testdate field Date select utility was super sensitive and inconsistent. It has been updated to use the same utility as all the other date selects in the application.

21- In Options->Display Options->Layout, resetting the layout for the Termination Assignments report wasn't functioning correctly.

22- The color and style of slack objects was not consistently changing as it should have to the custom style associated with certain placements.

23- In Oracle networks, using an apostraphe ( ' ) in the "User" field would cause an Oracle error: Error Message: Ora-01756: quoted string not properly terminated. Continue?

24- Renaming a Customer that was named 'cust:1' caused a previously entered customer record to be renamed

KNOWN ISSUES

1- When printing the map from View with MapPoint as the background, the printout is dark. Also, the print form takes a long time to close

2- Some forms when closed return focus to a different application, other than OSPInSight. It is necessary to re-select OSPInSight

3- When using Microsoft Mappoint as the background, the Back and Forward functions on the map don't always work the first time

Solution: Sometimes the Back & Forward entries on the right-click menu must be clicked twice to do anything

4- Click 'Print' in the Fiber Panel, and export the data from Crystal to Excel. Note that the data in the last few columns is offset from the headers.

Solution: Select the offset data, and move it so it matches the headers, or vice versa.

5- Any Equipment records that have an invalid TypeID value (such as 'none' when that is not in the TypeID list) will not show up in the "Customers/Equipment Report".

Solution: If you suspect that the report is not displaying all of your customers or equipment, open your Equipment List or Equipment/Customer Editor in OSPM-Edit and update the TypeID values such that they all correspond with an entry from the TypeID list (from the Hardware/Materials Editor)

6- Currently the Span/LocateID text dynamically resizes to fit the "span" field and not overrun the "fiber" field. However, it still isn't perfect, and depending on how big the form is, it will still run into the next column a little.

Solution: If there is some text overlap, simply resize the form until the text in the span column is not conflicting with the text in the fiber column.

7- When using MapPoint as a background (or when any Raster image is loaded in MapX), zooming in past 0.1 miles will typically invert the mapper. Labeling will also behave oddly at this zoom level with any raster images displayed.

Solution: There is currently no known resolution to this issue.

8- Sometimes you will see odd window/column behavior in the Ductbank Cross section editor.

Solution: Reset the layout for that editor:

OSPInSight OSPM-Edit 6.05 Release Notes

04/Nov/2004

NEW FEATURES

1- Cable and Slack can now have their Map Style based on the value of the 'placement' field. Use the Custom Objects editor under the Map dropdown menu to capture styles for various placements

2- The highlight has been moved from the animosp layer to a new layer called 'mapping'

3- The Reel length-usage message will now only display when more reel length is used than is available. Using a ReelID of 'unk' will prevent that message from displaying, or you can also disable that message in the Options->Edit Options->Misc Options form

4- The application will now prompt users to click and drag to draw a building if they attempt to simply click one spot on the map, which makes an invisible building object

5- When inputting cable spans, the 'Use Map Length' option will be checked by default now, meaning that the cable length value will be based on the length of the MapInfo line object itself. If you would rather enter a 'total' distance for cable objects, or use sequentials, click Options->Edit Options->Misc Options and uncheck the 'Use Map Length in cable editor' option

TIPS

1- Sometimes lists can have problematic display characteristics. For example, if your "Types of Enclosures" list is opening with colors that make it difficult or impossible to read (such as black text on black background), simply reset the layout for that list. To do so, open the Display options by clicking Options->Display Options, then click the Layout tab. Find the checkbox for the "Enclosure Types" list, check it, then click the "Reset Layouts" button. Use this form to reset the layout of lists, reports or editors that have similar problems.

2- Another possible issue with lists is that if you highlight the data in a cell, and then press the Delete key on your keyboard, you might be prompted to delete the entire row, rather than only deleting the data in that field. In order to resolve this problem, simply reset the Layouts for your lists. Go to Options->Display Options, select the Layout tab, click the "ALL Lists" box, then click "Reset Layouts"

3- After installing OSPInSight, if you are unable to drag the map to the right or down with a polyline (cable or duct object) but are able to do so to the left or up, simply resize, then maximize the application. Finally, press ctrl+q to save that setting.

ERRORS RESOLVED

1- Selecting map objects on the DOC layer with the GetInfo tool would highlight incorrect documents in the treeview

2- The 'Change View' form wasn't opening when selected from the Map dropdown menu

3- Select an existing cable span and open the editor, select a cable segment in the spanlength grid, click the "Add Duct Bank" button. The Duct Bank Length field was not populating correctly. This is now an auto-calculated length using the map distance.

4- 'Owner' field now shows up in the Display Options and Edit Options->Defaults for building objects. Previously the Owner field was only available in the Building List, but not the editors

5- While a network is opening if the File menu was clicked an error message appeared: Index out of bounds

6- The 'ea6' field was not included in the default query for the Building List

7- Using the Enclosure tool to replace a slack with an enclosure when there was another slack object nearby would cause both slacks to be deleted, rather than only the one that was clicked

8- Hardware Materials Editor, Reelid was not updating in Oracle networks

9- Open a fiber panel with terminations, click the "Edit On" button, click the 'Reserve' button in the notes section. In the "Reserve Current Jack" form, click the Initiator dropdown, then select 'Edit Items'. A "Run-time error '383'" used to appear, then the application crashed

10- Updating values in the lists that had more than ~32,768 records would generate overflow errors

11- The Display Options->Autozoom option was affecting the Fiber Panel->Find Route function, whereas they are now completely independent. The Find Route options now determine the find route mapping

12- When running an SQL Query on a mapinfo table and viewing the results as a table called SELECTION, sometimes SELECTION was not an option in the Browse Table window. Also, if I SELECTION was available, using the scroll bar in it would cause the list to go blank

13- Deleting a Frame with related terminations is now a more straight-forward. Also, orphan termination records will not be left in the list

14- Midsheathing (splitting) a cable that loops over itself with an enclosure or slack loop would cause graphical distortion

15- Copper cables with a placement of 'underground' were not being created with the correct style, based on the Default style entered

16- Patch editing in Fiber Panel updated only one side of the patch. It will now update both sides of the patch

17- In the Schematics, the Print Setup button was not working. The VBPrnDlg.dll had to be placed in the system32 directory and registered

18- LocateID value was displaying incorrectly in the Splice Key editor

19- Colons ( : ) have been restricted as input in the Group field for terminations as well as the Equipment ID field for equipment. Colons are used as delimiters and they cause errors if they are present

KNOWN ISSUES

1- The Custom Objects style is still a little inconsistent for Slack objects. If it fails the first time, just retry it

2- Appending the color code information to fibers in editors will slow the load time for dropdown lists that show those fibers. For example, with the Edit Options->Misc Options->"Append locateid to spans in editors" option checked, the Termination editor will load a little more slowly.

-------------------OSPInSight OSPM Edit 6.04.3 Release Notes--------------------------

27/Jul/2004

******** NEW FEATURES ********

1- Print ability has been added to the Leased Fiber report

2- Layouts for Editors, Reports and Lists can now be reset in the Options->Display Options->Layout form. If there is a third column in the editors, or if you are getting errors or strange behavior in a certain report, editor, or list, simply reset the layout for that form

3- Press Ctrl+t to change how the 'Tab' key behaves in editors. The options are to tab from field to field, or from section to section. By default the Tab key will go from field to field

4- When performing a Find Route, Mapping a ring, or mapping a Cable, the 'highlight' is not simply a selection now, but objects copied to the animosp layer. This means that when a ring is mapped, you can select and work on your network without losing the ring highlight. In order to clear the animosp highlight, click the Red 'Unselect All' button on the toolbar, or click 'Map->Clear AnimOSP Layer'

+++++++++ ERRORS RESOLVED +++++++++

1- Relate a MapInfo object (on the DOC layer) to a Document in the Document Relationships editor, then use the OSPInSight GetInfo tool to click on the MapInfo object. In 6.04.1 doing this would fail to highlight the related document in the Treeview

2- Installed Material/Hardware Report, when run in an Oracle network, would not allow the user to re-order by any column

3- MapPoint background layer didn't stay hidden when disabled in layer control

4- Changing a Frame name failed when there was a frame 'none' in the installed frames list

5- When selecting cable spans from the map with the Leased Path Editor, the conflicts didn't show the first time 'Show Spans' was clicked

6- Poles added to a network database with the 'Create Multiple Poles' feature were not immediately added to the Treeview

7- If the Enclosure Types list was empty in the Hardware Materials editors, the modify button would not enable for any hardware profiles

8- The Find Route options have been updated and streamlined in the Fiber Panel

9- An integrity function has been added that will verify that the scale factor (helix factor) for all cable spans input is greater than or equal to 1, because previously OSPInSight allowed scale factors that were less than 1

10-OSPM would allow slacks enclosures and frames to be placed on top of existing slacks enclosures and frames. That has been prohibited now, except for replacing a slack with an enclosure

11-The 'Browse MapInfo Table' (F2) function would fail with MapPoint as the background

12-After the MapPoint control had been opened in OSPInSight (when using MapPoint as a background) forms would disappear behind the main window

13-Customized column names in lists would be lost after reordering the list

14-Equipment Type list and PlaceobjectID list ordering options have been added to Options->Edit Options->Defaults->Equipment

15-In 6.04.1 the route highlight was STILL lost when zooming or panning sometimes. This has been resolved by changing the way OSPInSight 'highlights' work. See New Features above

16-Mapping without Autozoom selected in the Display options did not change the viewable area to include the mapped object

17-Changing the type for a pre-existing object (building type for example) would not consistently update the map object appropriately, based on custom objects

18-Right-click menus in the 'Relations' section of the Treeview often had disabled options...such as 'Map' or 'Edit'

19-Performing queries in the lists using the Date columns use # instead of ' This has been updated in the lists

20-Apostraphes (') caused errors in many parts of the application. Most, if not all, of these instances should be resolved

21-Deleting a Frame with terminations in an Oracle network generated a 'table does not exist' error or an 'ORA-00918: column ambiguously defined' error

22-Couldn't set order for object (AP, Bldg, etc) dropdown list in doc/rel editor

23-General Status now says 'Application expired' when the application is expired, rather than saying 'Ready'

24-'--Use last input' option wasn't functioning in the Hardware Materials Editor->Equipment types

25-The Schema Generator would sometimes fail to create the SEQ_REL sequence

26-Adding multiple document relationships in an OSPInSight Oracle network gave the following error: ORA-00904: "VAL": invalid identifier

27-When inputting an Access Point and clicking OK in the editor on Windows NT, OSPInSight would lock up

28-Opening a Ring(Termination) editor, and clicking 'OK' or 'Refresh' would lose the span and termination records for that ring

29-The placement selection was not always retained for cable segments and slack loops in the Cable Span editor

30-When working with an Oracle database a MapInfo Resolve Conflicts window would appear fairly frequently. The majority of these occurences should be done away with because now the editors save the corresponding layers and then force a layer refresh

!!!!!!!!!! KNOWN ISSUES !!!!!!!!!!

1- When using Microsoft MapPoint as background data, the map does not refresh as you drag the screen by drawing a polyline or other objects. This makes it impossible to drag a line off the screen and see the streets as you draw.

-WORKAROUND: This can be worked around by drawing a cable stub, doing your edits in and closing the editor, and then reshaping and lengthening the cable to match the route. It might be necessary to add rows to the spanlength section manually, in the cable span editor, such as Frame and Enclosure rows

2- When an object type is selected (such as Access Point type) that is associated with a custom map object, the map is updated but the map object will move slightly.

-WORKAROUND: Move the object back to where you would like it. This is simply a limitation of MapInfo, since information about the centroid of an object is unavailable we have to work with the minimum bounding rectangle, which will be different for different shapes.

3- OSPInSight Oracle schemas created before 6.04.3 are possibly missing a sequence used by a trigger called TR_REL to create document relationships. This error "ORA-04098: trigger '[schema].TR_REL' is invalid and failed re-validation" may appear when you attempt to update a new document relationship.

-WORKAROUND: Create the sequence on that schema using the following command: CREATE SEQUENCE SEQ_REL START WITH 1

-------------------OSPInSight OSPM Edit 6.04.1 Release Notes--------------------------

3/May/2004

******** NEW FEATURES ********

1- A comments field has been added to the Leased table so information such as the lease expiration date can be added

2- The Splice Spreadsheet crystal report is now automatically populated with the In, Out and Typeid values for each span

######## TIPS ########

1- The columns in the spanlength section of the cable editor (the middle section) can be confusing if they are not set in the following order: ord, typ, objectid, lengthin, lengthout, totallength. We also suggest you change the display names for these columns to: Order, Type, Objectid, In, Out, Total. The order and display names can be modified in Options->Display Options->More->Cable Span Length. There are other fields in the Display options that are displayed only in the Cable Span Length list, but you can ignore those fields, as long as the above six fields are in that order. Also keep in mind that once the columns are in the order you want, you can resize them right in the Cable Span editor, and save that layout by pressing Ctrl+S

+++++++++ ERRORS RESOLVED +++++++++

1- A 'Syntax error' or an 'Ora-00936: missing expression' error was generated when using the Leased Path editor with the 'locateid' appended to the spanids

2- Printing schematics to printers other than the default would fail

3- Attaching documents to MapInfo objects on the DOC map layer would sometimes fail

4- In lists, queries in the Where condition field were ignored when the 'From Map Region' button was clicked

5- After performing a Find Route, the highlight was sometimes lost when panning or zooming

6- In the lists, custom field names would revert to the original after queries

7- 'Invalid view layer' error message should no longer appear when loading networks

8- Pointing to an html or url file in the Document Relationship editor would cause a program crash

9- When adding documents in the Document Relationship editor, the final backslash was left off of the path value

10- An error loop occurred when 'Edit Options...' was left as a priority or status in the fiber panel

11- When right-clicking column headers to minimize those columns in the lists a right-click menu inappropriately appeared, in reference to whatever row was highlighted

12- The 'Owner' field is now available in the Building editor, as well as Options->Display Options->More->Buildings, if you click 'Reset'

13- The Pole attachment template selection, as well as the Ductbank cross section template selection, were lost after updating any pole or conduit Edit defaults

14- When querying a list based on a map region and updating values for an entire column, clicking the Update field would make the original values, rather than the new values display in that column until the list was closed and reopened

15- Certain workspaces would take an inordinate amount of time to load in OSPInSight, hence in 6.04.1 the entire workspace opening process has been handed back over to MapInfo, which makes it much quicker. Please be aware, however, of Known Issue #2 below

16- Splitting duct bank with an Access point would generate errors if Quick Add or Custom objects were being used

!!!!!!!!!! KNOWN ISSUES !!!!!!!!!!

1- The tilde (~) is used as a field delimiter in the OSPInSight editors and report forms, hence using the tilde in any field will cause problems. Most fields do not allow the tilde as input, however there are still some fields that do allow it. If you run across a field with a tilde, please delete it using the lists, as the ~ character is visible in the lists, but not in the editors. If you receive a "Syntax error in UPDATE statement" message, or find a field that you are having difficulty updating, find the corresponding record in the lists and delete any tildes you see.

2- OSPInSight Edit is only compatible with workspaces that open one map window. In OSPInSight versions 6.0 - 6.04 OSPInSight would control the workspace opening process, and restrict the number of mappers to one. Versions 6.04.1 and newer will let MapInfo handle the workspace opening process. Therefore, When saving workspaces in MapInfo for use with OSPInSight please verify that only ONE mapper is open

3- Older .ini files will sometimes cause problematic display characteristics. For example, if your "Types of Enclosures" list is opening with colors that make it difficult or impossible to read (such as black text on black background), open your \OSPInSight\OSPM\Edit\Settings\Lists\ folder, find the enclosuretypedata.ini file and delete it. Other lists, editors and reports have corresponding .ini files in the settings folder, that have names based on some derivation of the form name. Deleting the .ini causes the related OSPInSight form to open with size and fields arranged based on the programmatic defaults, but to customize these attributes and recreate the .ini's simply press CTRL+S in any of the forms

4- Conflicts arise when performing a find route where the route has an enclosure and a frame with the same name. Typically the termination in the panel will not be recognized, but there can be other symptoms. In order to work around the error, rename either the conflicting frame or the enclosure in the editor. For example, if you have a frame named "Plaza1", and an enclosure named "Plaza1", then you could rename the frame to "Plaza1 (frame)"

5- Sometimes a message appears after updating to 6.04.1 when attempting to load an Oracle network in OSPInSight that says 'MapInfo DBMS is not installed'. To resolve it, go into the setup and click the 'Users' button. Remove the row referencing the user who is getting the error, and re-add that user

-------------------OSPInSight OSPM Edit 6.04 Release Notes--------------------------

9/March/2004

******** NEW FEATURES ********

1- When performing a Backup or Restore, before OSPInSight network files are overwritten a zipped copy of those files will be created, thus allowing for an easier recovery in the event of the wrong files being replaced

2- Prompt for golden directory download and for automatic backup when exiting - enable in the Setup

3- The Treeview Search allows partial-string searches within the selected folder...type your string and click the binoculars

4- Support for operating system large fonts has been added

######## TIPS ########

1- The LocateID and colorcode can be displayed with all spans and fibers in report forms and editors. To see them in editors click Options->Edit Options->Misc Options, and check the options for appending the colorcode and locateid. To see them in reports click Options->Display Options->Treeview, and check the options for appending the colorcode and locateid

2- The fields displayed in editors and lists can be customized. Go to Options->Display Options->More, then choose your editor. You can uncheck the fields you don't wish to see, reorder the fields and rename them

3- If you are a network editor you SHOULD NEVER overwrite the database you are editing with the copy of the database in the Golden directory. In your case you would use the "Golden/Backup Directory" path in Setup to create a backup copy of the database files you are editing. Click the checkbox for "Prompt to backup when exiting network." if you wish to be prompted to perform the backup each time you exit. When you close the network a prompt appears, asking "Do you want to backup the database?" If you select 'Yes' your network will be copied to the backup location. If you don't wish to be prompted every time you exit, you can manually perform the backup by going to the Database->Backup /Restore dropdown from the OSPInSight startup screen

4- Map Views can be saved in the Map->Map Views form. Zoom to a view of a town, or a node, type a name in the Map Views editor and click Add. With a list of views you can demo your network quickly

5- When you select an item in the Treeview, pressing a letter on the keyboard will find and highlight the next item displayed that starts with that letter, including folders and subfolders. This method will not search through items in a folder that is not expanded. To use the search field above the Treeview, click the folder that contains the item you wish to find, type any part of that item's name in the search field, then click the binoculars button. For example, if you wish to find a pole that has "Benson" in it's name (such as "PL-123 Benson Ln") expand the 'Poles' category, select the first item in the list, type "benson" in the search field, then click the binoculars

6- Sometimes errors will occur if an incorrect value is set as a default for an editor. If an editor is displaying errors when opening or when you are inputting new objects, a good idea is to go to the Edit Options, from the 'Options->Edit Options' dropdown menu item. In the Defaults tab you can select the entry for the editor and click 'Reset', which often removes the problematic value.

+++++++++ ERRORS RESOLVED +++++++++

1- The editor, report, and other .ini files have been updated in the 6.04 release to resolve certain incompatibilities

2- Previously the Reel ID 'ReelID-1' could not be used

3- Workspaces saved with OSPInSight sometimes would force the user to browse to the specified layers when being opened

4- 5.0 to 6.0 convert was not checking datatype for pole lat/lon fields, and was leaving them as NUMBER fields, causing an error when attempting to input poles

5- Installed Materials/Hardware report showed all cables as underground when querying by Placement='underground'

6- Display Options settings were not displayed in the 'Relations...' window

7- Mapping Rings (Cable Span) would get an "expression too complex" error when mapping very large rings. Now the objects are copied to the animosp layer

8- Attempting to connect to Oracle database with OSPInSight when MapInfo DBMS was not installed did not give an error message

9- The data linker was not working with Oracle databases

10-Certain fields in an Oracle schema created by the Schema generator were set to 'non-unique' instead of 'unique'

11-In Windows XP some forms had the bottom slightly cut off

12-The Route Schematic would not run correctly when opened from within the Taper Report

13-Pole list in pole editor for pole attachments loads quicker now

14-Sometimes when performing a find route through splitters the route distance (based on the last path) would calculate incorrectly

15-When Performing a Find Route in the Fiber Panel, the Span column would show the first span in every row

16-Reshaping a MapInfo object on a layer, then selecting and trying to reshape an object on another layer would not succeed

17-Performing a midsheath did not populate the 'tray' field in the splice key...now it populates with a '0'

18-Not all user-defined column widths were saved when ctrl+s was pressed in the taper report

19-The splice spreadsheet was not displaying dead fibers correctly in all situations

20-Text labels would cause an error when saving a panel layout in the panel viewer

21-Entering a duplicate Typeid value for certain hardware profiles in the hardware material editor would cause an infinite-loop error message

22-Change group feature in the Terminations list was failing under certain circumstances

23-Changing an Access Point or Building name sometimes did not update the related duct bank start or end place

24-Installed Material Hardware report terminated when the letter 'e' was pressed in other applications

25-Changing sequentials or total distance for a segment would not always recalculate the entire span in the editor

!!!!!!!!!! KNOWN ISSUES !!!!!!!!!!

1- The Treeview window loads very slowly, depending on the amount of data in a given list. For example, a network with more than 10,000 poles will typically take about a minute to expand the poles category in the Treeview. This problem is important to us and the performance will be improved in a later release

-WORKAROUND: For improved Treeview performance, group large categories. For example, if you have many poles in your network, click Options->Display Options, select the Treeview tab, then click the Poles category. In the 'Group By' dropdown, select an appropriate category by which to group your poles, such as city, type, class, owner, etc. What you want is to have smaller groups of poles. That way when you expand the poles category you will be presented with various groups that load MUCH quicker, and each group will load much quicker as well

2- The zip utility used in the Backup/Restore utility can crash the application if used repeatedly during the same session

3- The Treeview search utility will only search within the folder that has the focus

4- At times an 'Automation Error' is displayed when the user attempts to export list data to a Tab-delimited text file, or a message is displayed stating "Object invoked has disconnected from it's clients"

-WORKAROUND: This error seems to be very inconsistent...sometimes it will occur for an hour or a day, but will work fine when attempted the next day, or after waiting for an hour. In short...just keep trying.

5- When Rings (Terminations) are created based on a find route, performing splicing or termination updates along that route does not automatically update that Ring entry.

6- If the Name field in the Ring (Terminations) editor is left blank by the user when 'OK' is clicked, a blank row will show up in the Treeview. Hence, if you see a blank entry in the Treeview under Ring (Terminations), simply right-click it, select Edit..., and input a name.

7- The Leased Path Editor gives a syntax or expression error and fails to update the Lease information along the route if the Locateid is appended to the spans in editors

-WORKAROUND: Click the Options->Edit Options dropdown, select the Misc Options tab, and un-select the 'Append locateid to spans in editors' option

-------------------OSPInSight OSPM Edit 6.03.8 Release Notes--------------------------

16/January/2004

Errors Resolved:

1- Edit version 6.03.7 was looking for MapX, though the OSPM-Edit installer doesn't install it

2- Lists use only programmed colors now, instead of inconsitently using system colors

3- When clicking on MapInfo objects on the DOC layer with the GetInfo tool that have documents attached, the appropriate record was not highlighted in the Treeview

4- Redundant route/endpoint schematic print form has been eliminated

Known Issues:

1- Installed Materials/Hardware report showed all cables as underground when querying by Placement='underground'

2- Display Options settings are not displayed in the 'Relations...' window

3- 5.0 to 6.0 convert is not checking datatype for pole lat/lon fields, and is leaving them as NUMBER fields, causing an error when attempting to input poles

4- Attempting to connect to Oracle database with OSPInSight when MapInfo DBMS is not installed does not give an error message

-------------------OSPInSight OSPM Edit 6.03.7 Release Notes--------------------------

7/January/2004

New Features:

1- The Pole editor now has an attachment copy feature. Simply select a pole from the dropdown list, click 'Copy', and the attachments will be copied over to the current pole

Errors Resolved:

1- Extremely infrequently the Documents/Relationships editor would only show one row in certain dropdown lists where there should have been various rows

2- Various errors were occuring in certain mapping/map editing situations, displaying a MapClick error. These errors have been resolved in the new executable and new mapclick file

3- If a number was repeated in a color code, (for example: buffer 1 fibers 1-12, buffer2 fibers 12-24) the splice key editor would generate a 'invalid procedure call or argument' error

4- Database backups were not allowing network backups, because drilling down beyond the domain wasn't functioning

5- In the termination editor, when a span on the map that goes into that Panel was selected, then in the End span drop-down, 'select' was clicked an error message was displayed: "That span is not part of this frame. Please try again!" Even though the span was part of the frame

6- The slack placement default was failing

7- The calc.mdb database that is used for report-data formatting has been updated to eliminate "Field is to small to accept the amount of data you have attempted to add" errors

Known Issues:

1- At times an 'Automation Error' is displayed when the user attempts to export list data to a Tab-delimited text file

2- When clicking on MapInfo objects on the DOC layer with the GetInfo tool that have documents attached, the appropriate record is not highlighted in the Treeview

3- When opening a network, if an error appears saying "Error Message: The SELECT statement includes a reserved word or an argument name that is misspelled or missing, or the punctuation is incorrect.", then open the Options->Display Options->Main window, and select a field in the 'Fields to Display' section for each category, and update all of the changes.

4- If you right click on a splice-line in the splice schematic and click 'Taper Report', the correct spanid is not sent to the Taper form. The spanid and fiber number will have to be selected manually.

5- Sometimes the script generated by the Oracle Schema Generator fails to populate the new schema with the default records when it is run

-------------------OSPInSight OSPM Edit 6.03.6 Release Notes--------------------------

31/December/2003

Errors Resolved:

1- After performing a Find route and then a Find fault, the row with the fault was not highlighting in the details tab

2- The ability to add rows manually in the Lists has been re-added in this release

3- In the Route Schematic if the user right-clicked on a frame or enclosure object, a building editor would appear

4- Connecting to an Oracle network with OSPM-Edit as a Read-Only user would either fail, or connect with some edit capabilities

5- Attaching an OTDR trace, or any file, in the fiber panel would fail with a 'file not found' message

-------------------OSPInSight OSPM Edit 6.03.5 Release Notes--------------------------

12/December/2003

New Features:

1- The Taper report Route Details tab now allows the user to open the Route, Splice and Endpoint schematics from a right-click menu

Errors Resolved:

1- Splice spreadsheet column format corrected

2- Printing a duct-bank report, the install year would always display '2000'

3- OSPM View highlighting when mapping and performing find routes has been corrected

4- OSPM View Relations and More Info sections have been updated

Known Issues:

1- The ability to add rows manually in the Lists is unavailable in this release

2- After performing a Find route and then a Find fault, the row with the fault is not highlighting in the details tab

3- When attempting to add OTDR trace files in the Fiber Panel OTDR tab, an error message is displayed. "File not found"

-------------------OSPInSight OSPM Edit 6.03.4 Release Notes--------------------------

25/November/2003

New Features:

1- LocateID and Color Code have been added to the Taper Report

Errors Resolved:

1- Taper report Assignment tab not showing Assignment data

2- Using Quick Add for Duct Banks caused an error when placing ducts

3- Ductbank Template was not functioning correctly

4- Placetype & Placeobjectid fields sometimes were not autopopulating for slack

5- Incorrect default paths were placed in the Data Linker form

6- Edit Options->Defaults->Slack->Placement was not placing the desired value when midsheathing with a slack

7- Network converted from 5.0 to 6.0 format in Oracle had to have all users removed & readded to clear AccessRegion column

8- Trying to display relations on objects with document relations gave an error

-------------------OSPInSight OSPM Edit 6.03 Release Notes--------------------------

24/October/2003

New Features:

1- Automatic Duct Bank placement tool can be used with pre-existing network cable

2- DEL. button added to cable editor to delete span length objects (Delete button now deletes entire span)

3- A text layer can be added to the workspace but saved in a different directory now than other network layers. For example if I have an Oracle schema named 'mytown' to which I connect with OSPInSight, and the network layers are downloading to c:\temp oracle\mytownAP.tab, ~mytownBDG.tab, etc. then I can place a 'mytownTXT.tab' on a network server, and save THAT TXT layer as part of my workspace. From then on when editing Text in my network, the edits will be saved to a common TXT layer. A message does appear at the network load time, however, that warns the user that the TXT layer is in a different directory than all of the other network map files

Tips:

1- When editing the graphic representation of a panel, click and drag objects to move them, or hold the SHIFT key AND THEN click and drag to resize them (including text labels that appear to be cut off)

2- Never save changes to your animosp or animate layer

3- If you are an editor, do not specify a Golden Directory

4- Press Ctrl + Q to save the layout of the toolbars and treeview, press Ctrl + S to save the size and layout of editors and other windows

5- In the Leased Path editor, double click a row in the grid to see Lease information for that cable span

Errors Resolved:

1- List editing issues: deleting, row updating

2- Splice Spreadsheet - Export from Crystal to Excel wasn't working

3- Group name editing in the Termination list has been fixed

4- The Patch editor was not showing all groups in the dropdown field

5- The Fiber Panel graphic was not saving

Known Issues:

1- When editable map objects are selected (clicked, or after performing a find route), and the treeview splitter bar or some non-map areas are clicked, both the Map area and the other area have the focus. Hence if the 'Delete' key is pressed, all selected map objects are deleted

2- After completely installing OSPM 6.03, at times the OSPM 6.03 installer will begin to run, and request that you browse to the install files. In order to make it stop running, simply select the .msi file from the CD or the installation files from which you originally installed and let it run through it's process.

3- Sometimes a MapInfo Conflict window appears when there is apparently no conflict. See Known Issue #6 for OSPInSight Pro 5.05 below

4- The Leased Path editor is sometimes inconsistent with the conflicts when all fibers in a cable are selected by choosing From 0 To 0. Double check the leased information for each span by double clicking the row in the grid

5- Taper Report - Route schematic doesn't display correctly when run in the taper report, the objects are all on top of each other. Workaround: Open the Route Schematic from the 'Reports' drop-down menu instead of from the Taper report

6- There are still some rendering bugs to be worked out in the End Point schematic

7- Inputting the first pole on an Oracle network will produce an 'invalid use of null' error, and can cause additional errors with the 'Create Multiple Poles' feature

-------------------OSPInSight OSPM Edit 6.02 Release Notes--------------------------

30/July/2003

New Features:

1- An Error Log has been added under the Help dropdown menu

2- The TAB key now jumps sections in editors, while the arrow keys traverse the fields within sections

3- All schematic printing functionality has been improved

4- The Oracle Schema Wizard has been replaced with an easier-to-use Oracle Schema generator, which allows scripts to be generated and run, or just stored.

5- The Ductbank midsheath operation has been made more user friendly. Simply use the Access Point tool to click on one side of the ductbank line, and drag to the other side of the line.

Errors Resolved:

1- Placing slack, the Placeobjectid sometimes was not displayed in the cable editor.

2-There was no option to disable the Reel Length Integrity enforcement

3- The usedlength field sometimes did not display in the Reel section of the Hardware materials editor

4- Midsheath a cable span with a slack loop on an access point, note that the placetype, placeobjectid and placement were not populated for the slack

5- Using the Drag & Drop function moves slack and enclosures but neither the AP nor the duct was moved, nor was their an option to move them

6- Sometimes when inputting objects, a message window appeared, querying whether you wished to split the duct bank, though it was at inappropriate times.

7- Various inconsistent errors had been seen while editing a database created by the Oracle database wizard, such as incorrect spanlength data when inputting spans, etc. This was resolved with the new Oracle Schema Generator

8- The TAB order in the editors has been optimized

9- Deleting from various lists (Poles) gave a 'no further transactions can be started' message

10- If you click on duct with the AP tool but don't drag the line, you will be asked if you want to split the duct, but it won't split

11- When converting an OSPM 5.0 database to 6.0, the document relationships fail to copy, because the primary key trigger fails to create

12- The End Point Schematic does not pull up in the Fiber panel after shooting several fibers. If you pull up the Schematic before shooting any fibers, the schematic will pull up.

13- With multiple editors inputting similar objects, some id conflicts are still arising

14- Performing a midsheath Slack that is not on a placeobject (Access Point or Building) gives and 'illegal procedure' error and puts an incorrect value in the 'Placetype' field. The error doesn't cause a problem, and you can manually correct the value in the Placetype field

15- Some longer routes render incorrectly in the route schematic

Known Issues:

1- When editable map objects are selected (clicked, or after performing a find route), and the treeview splitter bar or some non-map areas are clicked, both the Map area and the other area have the focus. Hence if the 'Delete' key is pressed, all selected map objects are deleted

2- The Ductbank midsheath operation is easier. However if you click RIGHT ON the ductbank line, you will be asked if you want to split the duct bank, though regardless of your answer, the duct will not be split

3- Issue 801 Routes passing through about 100 spans fail to display the labels on splice points and fiber panels

4- Issue 749 Taper Report - Route schematic doesn't run in the taper report

5- Issue 784 Splice Spreadsheet - Export from Crystal to Excel not working

6- In the ductbank editor, poles are not available in the start & end place fields

7- After completely installing OSPM 6.02, at times the OSPM 6.02 installer will begin to run, and request that you browse to the install files. In order to make it stop running, simply select the .msi file from the CD or the installation files from which you originally installed and let it run through it's process.

8- When connecting to an Oracle OSPM database and pointing to pre-existing MapInfo tables on the local drive, they are not replaced as they should be, but simply use the pre-existing tables' data. Hence it is best to delete them and allow them to be recreated, or use a new identifier

9- Issue 802 Printing Endpoint schematic renders an additional vertical line

10- When creating a database with the Oracle Wizard, if the Oracle tablespace has run out of room, attempting to load the network in OSPInSight causes it to freeze. Verify that the Tablespace has sufficient space

11- Sometimes a MapInfo Conflict window appears when there is apparently no conflict. See Known Issue #6 for OSPInSight Pro 5.05 below

12- Issue 803 Endpoint Schematic is inaccurate through splitters

13- Attempting to print from schematics with no printer installed causes a Run-time error, and shuts down the application

14- OSPInSight databases created with the Oracle schema generator do not have the sequence or trigger relating to the REL table, which is needed to create document relationships. In order to add the necessary sequence and trigger, run these statements on the schema created with the OSPInSight Oracle Schema Generator:

SQL>Create Sequence SEQ_REL start with 1;

SQL>Create Trigger TR_REL Before Insert On REL For Each Row Begin Select SEQ_REL.nextval into :NEW.ID From dual; end;

-------------------OSPInSight OSPM Edit 6.01 Release Notes--------------------------

20/June/2003

New Features:

1- Deleting items from the lists will also delete them from the Map

2- Ability to open multiple mapper windows

3- 'Refresh' added to category right-click menu in treeview

4- Slack row highlighted when slack added to a cable span

Errors Resolved:

1- Could not insert an access point to an existing ductbank

2- Was no place in some editors to change the object Name or ID on creation of the object

3- An ungraceful error was given if the path was incorrect in the Data Linker

4- Placing '--use last input' in Edit Options Defaults 'medium' field caused the Cable editor 'medium' field to be populated with '--use last input'. If you are still seeing this, click the 'Reset' button in the Edit Options->Cable Spans category

5- 'Placement' was under the Cable Spans category, but was moved to the Cables category

6- Reelid's were not updating permanently

7- Hardware materials editor was displaying an error when attempting to update

8- Plant drawing field now editable for Oracle databases in the Network Setup

9- Changing pole_id in editor did not retain change

10- Added flexibility in Network Setup

11- Group field changes in Termination list were not saving

12- Label edits in the treeview are now disabled

13- Tree View search functioning

14- The enclosureid was not using the 'Object Names' defaults in the Edit Options

15- Some Duct bank changes were not being saved

16- Various Oracle multiple user conflicts have been resolved

17- Reorder termination list by position no longer giving error

18- Many list edits were not being saved to the database

19- Adding cross section to duct added at the same time as a cable gave an error

20- A Termination would give a Run time error under certain circumstances

21- Errors were received when changing status in the Fiber Panel

22- Scores of smaller errors involving updating database fields, highlighting, gui performance and other areas have also been fixed in this revision

20- In order to set the columns, rows, and positions, it was necessary to un-highlight your entry for every character you type, or just paste a number into the field

21- For Reels in the Hardware Materials editor, the 'attenuation' field did not allow decimal points

22- When in the Hardware Materials editor, the Panel viewer for Frame types did not save your edits

23- Selecting an empty Node or category in the treeview gave a 'With block' error

24- Creating a database with the Oracle Database Wizard was not saving the MapInfo symbology

25- Various 'Create Multiple Poles' errors existed, including geographic placement, latitude & longitude, etc.

Known Issues:

1- Placing slack, the Placeobjectid sometimes is not displayed in the cable editor. If this occurs, open the Display Options, select Slacks, and click Reset

2- The End Point Schematic does not pull up in the Fiber panel after shooting several fibers. If you pull up the Schematic before shooting any fibers, the schematic will pull up.

3- In the ductbank editor, poles are not available in the start & end place fields

4- Extra column sometimes appears in editors. If this occurs, go to the \OSPM\Edit\Settings\Editors\ folder and delete the *data.ini file elating to that editor, and resave the layout for that editor

5- There is currently no option to disable the Reel Length Integrity enforcement

6- The usedlength field sometimes does not display in the Reel section of the Hardware materials editor

7- When connecting to an Oracle OSPM database and pointing to pre-existing MapInfo tables on the local drive, they are not replaced as they should be, but simply use the pre-existing tables' data. Hence it is best to delete them and allow them to be recreated, or use a new identifier

8- Midsheath a cable span with a slack loop on an access point, note that the placetype, placeobjectid and placement are NOT populated for the slack

9- Using the Drag & Drop function moves slack and enclosures but neither the AP nor the duct is moved, nor is their an option to move them

10- Sometimes when inputting objects, a message window appears, querying whether you wish to split duct bank, though it is an inappropriate time. Simply exit and re-enter the application when that occurs

11- With multiple editors inputting similar objects, some id conflicts are still arising

12- When editable map objects are selected (clicked, find route), and the treeview splitter bar or some non-map areas are clicked, both the Map area and the other area have the focus. Hence if the 'Delete' key is pressed, all selected map objects are deleted

13- When creating a database with the Oracle Wizard, if the Oracle tablespace has run out of room, attempting to load the network in OSPInSight causes it to freeze. Verify that the Tablespace has sufficient space

14- Various inconsistent errors have been seen while editing a database created by the Oracle database wizard, such as incorrect spanlength data when inputting spans, etc. This should be resolved in 6.02

15- Sometimes a MapInfo Conflict window appears when there is apparently no conflict. See Known Issue #6 for OSPInSight Pro 5.05

16- The TAB order in some of the editors needs to be optimized

17- Some longer routes render incorrectly in the route schematic

18- Deleting from various lists (Poles) gives a 'no further transactions can be started' message. Simply click yes to continue, and the function should succeed.

19- The Endpoint schematic fails to show span lines at times

20- Various words are reserved by Oracle, hence using the OSPInSight Oracle Database Wizard to create a schema with a reserved word will not load correctly. Examples of reserved words are: convert,

21- If you click on duct with the AP tool but don't drag the line, you will be asked if you want to split the duct, but it won't split.

22- When converting an OSPM 5.0 database to 6.0, the document relationships fail to copy, because the primary key trigger fails to create.

23- Performing a midsheath Slack that is not on a placeobject (Access Point or Building) gives and 'illegal procedure' error and puts an incorrect value in the 'Placetype' field. The error doesn't cause a problem, and you can manually correct the value in the Placetype field

-------------------OSPInSight OSPM Edit 6.0 Release Notes---------------------------

2/June/2003

New Features:

1- Press Shift+~ to disable and re-enable MapInfo Callbacks. Disabling MapInfo Callbacks will disable some labeling functionality, however certain map-intensive operations will run much more quickly

2- Editor and Report forms can be customized and the layout saved by pressing Ctrl+S

3- Field names, displays and placement can be customized and saved

4- All network layers can be saved as part of the workspace, allowing customized display of tables such as pole, conduit, etc.

5- Leased Path Editor to mark an entire path as leased

6- True treeview structure for navigation

7- Improved customizable Treeview display options

8- Custom object template tool

9- Automatic Duct Bank placement tool when drawing cable

10- QuickAdd feature, to input network items without using the Editors, which includes a QuickAdd log

11- Customizable Fiber Panel layout

12- Interactive Route Schematic, Endpoint Schematic, and Splice Schematic

13- Ability to save a history of Splice Schematics

14- Bundle & colors displayed in splice key, ability to splice by buffer tube

15- Create multiple poles at fixed increments along a polyline function

16- Reel integrity enforcement (tracks fiber amount used from a reel)

17- Data Linker tool which facilitates thematic mapping and MapInfo labeling

18- Ductbank Template

19- Pole Template

20- Improved Document/Relationship Editor which allows many-to-many

21- Customizable toolbar layout press Ctrl+Q

22- MapInfo Hotlink tool accessible in OSPInSight

23- MapInfo Layout window

24- Oracle Database creation Wizard

25- MapPoint data available as background map

26- More complete Installed Material/Hardware report

27- Splice tray field allows multiple trays

28- Improved Termination status integrity

29- Bi-directional Find Route function

30- Extended attributes fields added for network items, allowing users to add customized data

31- Ability to perform a find route independent of the map

32- Red line capability now available View only version

33- Title and page number have been added to Work Order Report printout

34- Equipment added to Work Order Report

35- Ability to relate folders, as well as individual files, to network objects

36- Ability to save map views

37- Enhanced ring/circuit data storage editor

Errors Resolved:

1-If a cable span is using a cable with a COLORCODEID of 6 or more digits, an Overflow error from CRoute:RouteFindColor was generated upon running the Find Fault function.

2-A 'MapClick error #644, argument 2 out of range' was received when attempting to perform a midsheath, if the cable object was a LINE object

3-When editable map objects are selected, and the treeview or any non-map area is clicked, both the Map area and the other area would have the focus. Hence if the 'Delete' key was pressed, all selected map objects were deleted, typically inadvertently

4-When performing a Find Route, the span field in the Assignments tab did not show the correct spanids

Known Issues:

1-Rendering some very large panel graphics can be a little slow, in panel designer, and the fiber panel.

2-MapInfo Conflict window appears when there is apparently no conflict. See Known Issue #6 for OSPInSight Pro 5.05

3-Color Code Legend in the splice schematic covers the splice data

4-In windows XP some forms have the bottom slightly clipped

5-At the completion of the MapX install an innocuous error is generated, "Incorrect command line parameters"

6-In the fiber panel, after unchecking the 'Highlight route' option, it is necessary to reload the form to re-enable them

7-Infrequently when a right-click menu is displayed (from map or treeview) and a toolbar or dropdown menu is left-clicked, the application will ungracefully exit

8-Geosets created in OSPM View are incompatible with MapInfo's Geoset utility

Known Oracle Issues:

1-Adding cross section to duct added at the same time as a cable gives an error

2-While editing in the lists, some errors are encountered

3-With multiple editors inputting similar objects, some id conflicts are arising

4-Error while duct bank +++++++++++++++++++++++++++++++++++++++++++++

5-Creating a new OSPM Oracle database with the Database wizard needs some primary keys manually created

6-After creating an OSPM Oracle database with the wizard, drawing network objects gives an error

7-After adding an existing OSPM Oracle database to the setup list, an error is displayed 'check that the database is not read only' and the database cannot be loaded if Oracle client isn't installed

-------------------OSPInSight Pro 5.07 Limited Release Notes-------------------

Errors Resolved:

Updated rptconduit.rpt handles 0 in install date fields 1/15/03

-------------------OSPInSight Pro 5.06 Release Notes---------------------------

11/December/2002

Errors Resolved:

1-When inputting objects MapClick.mbx checked for intersecting objects with a circle, sometimes returning incorrect values

2-Referenced colorcodeid was not updated for cable type when a colorcodeid was changed

3-Splitting duct bank with an access point did not correctly update related duct bank splices

4-Material hardware report would give an error when performed on a region with over 1000 objects in it

5-Midsheathing on certain segments of a span would cause cable segments to have incorrect spanid's

6-The Splice Schematic Setup default has been modified, and better instructions on how to use it have been added to the help file

7-With a golden directory specified, if you click File, then 'Download data from Golden Directory', and then clicked 'No', you received an error.

Known Issues:

1-If a cable span is using a cable with a COLORCODEID of 6 or more digits, an Overflow error from CRoute:RouteFindColor will be generated upon running the Find Fault function.

-Resolution: Give COLORCODE IDs of 5 or less digits

2-MapInfo Conflict window appears when there is apparently no conflict. See Known Issue #6 for OSPInSight Pro 5.05

3-If you receive a 'MapClick error #644, argument 2 out of range' when attempting to perform a midsheath, check to see if the cable object is a LINE object. If it is, convert it to a POLYLINE object, and then retry the midsheath function.

-------------------OSPInSight Pro 5.05 Release Notes---------------------------

7/August/2002

Errors Resolved:

1- When connected to an Oracle database, attempting to change the group gave an error

2- When connecting to an Oracle database in InSight, if you selected 'no' to download the spatial tables, attempting to update the MapInfo tables later would cause a window to appear asking for connection information, and not allow you to add objects without it

3- It is now much easier to edit past the fifth superduct in the Ductbank editor

4- The 'tab' order has been corrected in the superduct and innerduct sections of the Ductbank editor

5- When entering decimal losses in the fiber panel, the decimal places were lost upon exiting the panel, because the field was defined as a long integer in the MS Access database

6- The Work Order Crystal Report had been left out of previous installs. It is now present

7- The 'Leased' button is now disabled in the cable editor when the 'Leased Fibers' form is open

8- Midsheathing a duct bank did not correctly update the endpoints

9- Deleting a ductbank did not correctly resolve related ductbank splices

10- Copy duct bank function took an unnecessarily long time

11- After registering the software, infrequently it would lose the registration and give a message saying you needed to register again. The registration depends on the 'computer number', which was generated based on your computer's BIOS. For some reason, on some computers, this number would change, and invalidate the registration. In order to resolve this, the algorithm has been changed, so that instead of looking at the BIOS, the registration function now utilizes hard drive in order to derive a 'computer number', which should make it more consistent. After registering once with the new algorithm, the registration should not be lost again

12- When connected to an Oracle database with OSP InSight, if you used the GETINFO tool or 'Edit Item' tool to select an object with the 'info tool' window open, incorrect results were displayed and other errors were caused

13- 'Invalid use of NULL' error displayed when attempting to create a ductbank without super/innerducts

14- Pole-enclosure relationships have been corrected

15- The Leased Fiber report was not consolidating all of a company's leased fiber, and had some calculation errors

16- When editing an Access Point or a Building name, the endpoint fields were not updated in the related ductbanks

17- Dropdown lists have been added for all fields where it is necessary in lists, instead of allowing the user to type

18- 'Spurs' (a cable spliced back upon itself) did not display correctly in the Splice Enclosure Spreadsheet

19- In the Edit/Options menu, on the defaults tab, if you had '--use last input' selected for the installcompany, installday, installmonth, or installyear on Enclosures, you received an error when inputting or modifying enclosures stating that 'key column information is insufficient...'

20- When midsheathing a cable span, it did not update duct relations

21- When displaying a Splice Schematic for fiber cables with more than 16 fibers per buffer tube, or for copper cables, and also displaying the colorcode, the colorcode and schematic lines overlap. But it is now possible to adjust the schematic so that they do not overlap. Simply increase the FIBER OFFSET, the X-START and the X-END fields until they do not overlap. You might need to uncheck the PORTRAIT checkbox. Increasing the values by 1000 per attempt typically yields the best results.

22- Overwriting patches has been enabled. Conflicting patches will no longer be left in the database

Known Issues:

1- Opening a large 'Poles' list in OSP InSight while connected to an Oracle database can be slow. For example, with about 8000 records, a pole list can take up to 50 seconds to open

2- When a Pole Height is input in the pole editor, and then the units are changed, the program automatically attempts to convert the distance to an equal distance in the new unit. Sometimes that conversion is off by a little bit.

-Resolution: when changing the Pole Height units in the Pole editor, manually enter the height after changing the units

3- When mapping large rings, sometimes the ring objects are selected and highlighted, however the view is not moved in order to display the selected objects.

-Resolution: Right-clicking on the ring and mapping it for a second time will typically display in the map window

4- When connected to an Oracle database with OSP InSight, if two users place a building object at the same time and attempt to give them exactly the same name, the application allows it. They will have unique objectid's, but only one building will be marked when mapping from the list.

-Resolution: Delete one of the buildings and re-input it with a different name. In the future avoid giving the same name to building objects

5- When performing a find route function on a route that ends in a different span than the one where it started, notice that on the Assignment tab, in the Span column, it shows the same span for each row, even though it should be displaying different spans

6- Sometimes when inputting data or deleting objects in OSP InSight while connected to an Oracle database, a MapInfo Conflict window will be displayed. We do know some of the causes of these conflicts, but not all of them. One cause is that when you save a MapInfo object as a POLYLINE, Oracle automatically converts it to a LINE, causing a conflict between the local copy of the map tables and the server tables. In that case it does not harm the database either way, so you can simply click OK. when you do receive a MapInfo Resolve Conflicts message, typically the best course of action is to leave the settings that are in the Resolve Conflicts window when it opens, and click OK. If you are receiving that message consistently, or if it is corrupting any data, then it is a good idea to check your Oracle spatial table's primary keys and to call AFO for technical support.

-------------------OSP InSight Pro 5.04 Release Notes---------------------------

6/March/2002

Errors Resolved:

-'Locked by user 'Admin' on machine 'xxxx'' error

-Find Route function would report a zero distance for spans after a patch

-Duct, Superduct, Innerduct saving issues

-'Select Today's Date' would close current editor, open Splice Key/Termination editor

-Duct Bank Taper report had some data in incorrect columns

-Splice schematic displayed incorrectly for enclosures with more than 7 cables

-The spreadsheet would not complete for enclosures related to poles

-If you cancelled a Ductbank midsheath, it would still cut the duct

-InSight no longer allows one port (in a fiber panel) to be patched to many

-InSight can now resolve the Oracle service name with multiple versions of Oracle on a system

-Resetting the 'defaults' for editors uses correct data types and acceptable input

Known Issues:

1- The 'OPTICALLENGTH' column in the 'Installed Cable Span List' actually contains the Physical Length of the cable span, rather than the optical length

2- If you have a cable span associated with several segments of duct bank/innerduct, and then midsheath the cable span, it does not update the duct bank associations.

-Resolution: The innerduct/cable span association will have to be updated manually

3- In the Edit/Options menu, on the defaults tab, if you have '--use last input' selected for the installcompany, installday, installmonth, or installyear on Enclosures, you receive an error when inputting or modifying enclosures stating that 'key column information is insufficient...'

-Resolution: Do not use '--use last input' as the default for the Enclosure installcompany, installday, installmonth, or installyear fields

4- You might receive a mapclick error the first time you attempt to add a frame to a segment of cable in certain databases

-Resolution: Select 'Yes' on each of the series of error messages, and you shouldn't receive that message any further

5- STILL A KNOWN ISSUE: Often, when you right click on the map or treeview displaying a drop down menu, then a left click on any toolbar, the application will shut down instantly

-Resolution: We know that this error is irritating and are working towards it's resolution. It is caused by third party software, over which we do not have complete control, so we appreciate your patience until it is resolved. Thank you

-------------------OSP InSight Pro 5.03 Release Notes---------------------------

10/December/2001

New Features:

-When labeling a cable with the OSP InSight GetInfo tool, the 'Cable Segment' section can now be set to not display

-Ring captures can now be modified, rather than having to delete and recreate them

Errors Resolved:

-Delete a Frame, it would not remove the corresponding frame entry from related span's object lists

-Create a new database , start the identifier with a number, upon loading the database you received an error

-Map a document from the relations Window, a message box 'No Records!' appeared

-Draw a cable in an Oracle database with no nodes (one straight piece), perform a mid-sheath, the lines were being changed to polylines, disallowing midsheaths

-Labeling a frame with OSP InSight GetInfo tool would produce an error when any field used in the frame editor, and the hardware materials editor, was chosen to be labeled

-The 'Use MapInfo Length' setting in the cable editor would be selected by default, causing data loss if total distances were input without sequentials

-The 'Use MapInfo Length' setting in the cable editor would not be saved when changed

-Export the results of the 'Installed Material/Hardware...' report, some fields were repeated in the report, others were left out.

-Change a group name for terminations, and the path did not change for OTDR traces. It had to be changed manually in the database.

Known Issues:

1- If a building is input, using an apostrophe in the name, attempting to delete the building will cause an error

-Resolution: Avoid apostrophes in building names.

2- When a default is set for the comments field in the cable editor, that same default is placed in the segment as well as the span comments field

-Resolution: Avoid setting a default for the comments field or correct the default manually

3- Often, when you right click on the map or treeview displaying a drop down menu, then a left click on any toolbar, the application will shut down instantly

-Resolution: Avoid selecting any toolbars or menus if you have a right-click menu displayed

4- If a cable is drawn from frame to frame, and the fibers are patched to other fibers in the same span in such a way that it creates a loop, performing a 'find route' or taper report on these fibers will be caught in a continuous loop

-Resolution: Avoid terminating cables that are directly frame to frame into a collapsed loop

5- If a taper report is run then minimized, and the fiber panel is then opened, and the taper is maximized, the data will be lost in the taper.

-Resolution: Avoid minimizing the taper report when you are planning to open the fiber panel

6- When entering decimal losses in the fiber panel, the decimal places will be lost upon exiting the panel, because the field is defined as a long integer in the MS Access database.

-Resolution: Open the *.ntk file in MS Access, open the 'pwr' table in design mode, and change the 'loss' field from a long integer to a double

7- Automatic building placement function to reflect current lat/long values functioned incorrectly.

-Resolution: Function disabled

8- When adding a path for an OTDR Trace file in the Fiber Panel, the path field will not accept more than fifty characters.

-Resolution: Open the database in Microsoft Access, open the OTDR table in design view, and change the Path variable's Field Size from 50 to 250. Save the changes. Then open the calc.mdb database (located in your \OSP InSight\Pro 5.0\ directory -- unless you have Access '97 you will have to convert it to an MS Access 2000 database). Open the OTDR table in design view, and change the path variable's Field Size from 50 to 250. Save the changes (you will then have to convert the database back to the prior MS Access version).

9- In the enclosure editor, if "Today's Date" is selected, sometimes the splice key will open up.

Resolution: When "Today's Date" is needed, make sure the mouse cursor is not over the splice key button.

10- When splitting a piece of conduit with an access point, only one side of the newly separated duct will be updated.

Resolution: Open the editor for the duct that did not update, and update it manually.

11- Perform a taper report on multiple selections (for example: select 3-4 and hit add, then select 11-12 hit add) it will only show the details for the last cable entry.

Resolution: Only run a taper on one selection of cables at a time.

12- 'Locked by User Admin' error received after using the 'Re-Calc Total Length' function in the cable editor several times.

Resolution: If received, restart InSight.

-------------------OSP InSight Pro 5.02 Release Notes---------------------------

19/September/2001

New Features:

-Cable editor enhancements with Re-calc MapInfo distances

-Can customize Thematic mapping styles

-List mapping enhancements

-Duct Bank midsheath tool

-Splitter option in splice key

-Date field enhancements

-Auto relocate placeobjects when Lat & Long are updated

-Auto update Lat & Long When placeobjects are moved

Errors Resolved:

-Thematic mapping issues: Styles, and Legend

-Ring editor and Highlight issues

-Duct bank issues: field values, superduct and innerduct issues, select item,

copy superduct,

-List mapping errors

-Pole Symbol style error

-Get Info tool error

-Red MapInfo label tool error

-Work order report error

-Locateid field labeling error

-Plant drawing path update

-InSight toolbar closing issue

-Document Relationship editor without records error

-Could not attach documents to poles, ductbank, rings

-Taper Report summary error, without running report

-Sequentials errors in cable editor

-Titlebar error on Windows 2000 at 'No database open' screen

-Backgrounds could not be .tab files when using Oracle database

-Deleting from lists, the MapInfo object was deleted before confirmation

-Region Query from lists

-Couldn't label with enclosure id

-Switched Latitude & Longitude values

-Crystal Reports vs. Windows NT errors

-Termination status error in fiber panel

-Work order error

Known Issues:

1- Error 'Number 91 (Object variable or With block variable not set)' received when trying to print from lists or from certain reports when connecting to an Oracle database

-Resolution: Contact your database administrator for instructions on creating an Oracle ODBC data source. This will resolve the error.

2- After creating a new database, if you attempt to map objects from the lists before setting up the labeling options, you will receive an error indicating that the item cannot be found in the collection, etc.

-Resolution: Go to the Options menu, Labeling, and configure and apply the labeling options for each object. You will now be able to map from the lists.

3- Creating a database with a file identifier that begins with a number will cause an error when attempting to load the database.

-Resolution: Use file identifiers that do not begin with numbers.

4- Right click on the map or treeview, then click on the toolbar, OSP will shut down.

-Resolution: Avoid clicking on the toolbars when right click menu's are open.

5- InSight function of moving buildings to current lat/lon settings is inaccurate.

-Resolution: Avoid using the autoplacement function.

6- After running a Taper Report, minimizing the Taper window, opening a Fiber Panel, then maximizing the Taper window, all Taper data will be lost.

-Resolution: Avoid minimizing the Taper window when opening a Fiber Panel.

7- The First time an Oracle Database is Loaded, it loads as "Read Only".

-Resolution: Close Network and reload it.