♤ 2001/7/10(화) 13:19 afm11_Readme.Doc (39KB, DN:2142) |
 아키버스 최신 버전 설치안내서 ReadMe.Doc Release Notes for ARCHIBUS/FM Version 11 01.09.1999 / 09.25.2000 This file includes the release overview, system requirements, installation notes, known limitations, and general information not available at the time the documentation went to press. System Requirements Minimum: · Pentium PC, 133 Mhz or faster · 32MB RAM or more · 800x600 SVGA display or better · Windows 95B, Windows 98, Windows NT Service Pack 3 or later, Windows 2000 · 100 MB free Hard Disk space · AutoCAD R14 or AutoCAD 2000 (for Overlay users only) Recommended: · Pentium PC, 200 Mhz or faster · 92MB RAM or more · 1024x768 or higher resolution display ARCHIBUS/FM works with the following databases: · Sybase SQL Server 5.5 and Adaptive Server Anywhere 6.0, 7.0 · Microsoft SQL Server 7.0 SP1 · Oracle 7.3, 8 Installation To install ARCHIBUS/FM 11: · Backup. Back up your ARCHIBUS/FM project directories, as well as any custom views or database schema files you might have. · Uninstall. You do not need to uninstall previous versions of ARCHIBUS/FM 10, as Version 10 and Version 11 can run on the same machine. However, if you have a previous version of ARCHIBUS/FM 11, uninstall it using these steps: · Use the Add/Remove Programs options from the Control Panel to remove the ARCHIBUS/FM 11 application. Answer "Yes" to the prompts to delete shared files -- these files are older versions of the ARCHIBUS ActiveX FM Objects. · Restart the machine. · Use the Windows Explorer to delete remaining files in your \afm11 directory tree (as the uninstall from the Control Panel will not delete any read-only files, files that were in use during the uninstallation process, or files that were created after the program was installed). You may wish to keep your project preferences (.apj) files, your project folders, and any custom view (.avw) or script (.abs) files that are in this directory tree. · Setup. Run the Setup.Exe routine on the CD-ROM. The setup program will prompt you for your license disk. The setup program will then ask you to restart your computer before running ARCHIBUS/FM 11. Please see the appropriate server manual -- ARCHIBUS/FM for Oracle, ARCHIBUS/FM for Microsoft SQL Server, or ARCHIBUS/FM for Sybase -- for installation instructions. See also the TroubleShooting.Doc file for additional release notes. Version 11 Revision 3 Release Notes Version 11 Revision 3 contains the following major additions. Please also refer to the RevisionHistory.Doc file for more detailed information on changes to the program. · AutoCAD 2000 Support within ARCHIBUS/FM. The ARCHIBUS/FM drawing editor now reads and writes AutoCAD 2000 drawings directly. AutoCAD R14 format is also still supported. This feature comes from a new drawing component that is supplied by Autodesk and that is based on the same technology that is in AutoCAD 2000 itself. To have AutoCAD 2000 support within ARCHIBUS/FM you must have a new license file for Version 11.3. ARCHIBUS, Inc. issues an updated license file to any site that has a license for the ARCHIBUS/FM Overlay for AutoCAD 2000. · ARCHIBUS/FM Drawing Speed. Drawing operations within the ARCHIBUS/FM drawing editor -- such as creating assets, cataloging a layer, or populating -- give better progress feedback and are twice as fast as they were within Version 11.2. (For comparison, the ARCHIBUS/FM Overlay for AutoCAD is five times as fast as 11.3 at these operations; so those with heavy drafting needs will still wish to use the Overlay.) · Drawing List command. There is now a Delete button on the drawing list. You can use this to remove a drawing from the list of drawings in the project and, if desired, to delete the associated drawing file as well. Version 11 Revision 2 Release Notes Version 11 Revision 2 contains the following major additions. Please also refer to the RevisionHistory.Doc file for more detailed information on changes to the program. · ARCHIBUS/FM for MS SQL Server. MS SQL Server support requires Version 11 Revision 2 or later. · ARCHIBUS/FM Overlay for AutoCAD 2000. AutoCAD 2000 support also requires Version 11 Revision 2 or later. · ARCHIBUS/FM for Oracle 8. Version 11 Revision 2 has been verified against both Oracle 7.3 and Oracle 8. · Sybase Adaptive Server Anywhere 6.0 for Single-User versions. The single-user version now installs Adaptive Server Anywhere 6.0 rather than SQL Anywhere 5.5 for the Single-User (Runtime) version. · ARCHIBUS/FM Update Project Wizard. With V11.2, the application control program ships with the Update Project Wizard, a utility that can migrate ARCHIBUS/FM data and schema between projects -- regardless of whether those projects are on Sybase Adaptive Server Anywhere 6.0, Oracle 7.3, Oracle 8, or MS SQL Server 7.0. · Cascading Updates and Deletes. The application control program handle cascading updates for Oracle and MS SQL Server databases. This eliminates the need for custom schemas to maintain a complex set of triggers for cascading changes. The updates are made using bulk statements executed on the server so that performance is not affected. ARCHIBUS/FM Program Usage Notes This section aims to clarify several aspects of the program. Even if you are familiar with a previous version of ARCHIBUS/FM, please review these usage notes. General Notes · Process Toolbars. If you are using an 800x600 display, and if you have your Show Explorer Tabs set to "Show All Tabs", you should use only one row of command toolbars so that the complete process toolbars display. To turn off the second line of toolbars, right-click over any toolbar, and clear the checkmark next to that toolbar's name. If you have a custom EIS with large images and would prefer not to turn off toolbars, use the 'Scale Image' option for your images rather than the 'Centered' option to have them scale to fit the available area. · Windows Explorer Associations. If you double-click on an ARCHIBUS/FM file (e.g. an .abs, .eis, .apj, or .avw file) in the Windows Explorer or on a desktop shortcut, or if you drag-and-drop it onto ARCHIBUS/FM, the program will load that file. If you wish to edit the file instead, use the right click menu on that file and use the Edit option. If you wish to change the association, use the View/Options command on the Windows Explorer. · Adding to the Hotlist. On the ARCHIBUS/FM Explorer Hotlist, the Add Item and Item Properties commands are changed slightly from the documentation. The "Close" button replaces both the "OK" and "Cancel" buttons. To add an item, use the "Add" button and then the "Close" button. To change an item, use the "Update" button and then the "Close" button. · Navigator Context Help. When invoking help on the Navigator using the context menu, remember the help topic loaded will be for the item beneath the tip of the arrow cursor -- not the center of the cursor. As the cursor is larger than the text of the Navigator, this is sometimes confusing. Using Grid Windows · Entering Date and Time Values. If your Control Panel's Regional Settings use a four-digit date (e.g. 1995), you must enter all four digits for the date to be recorded. If your Control Panel specifies a two-digit date (e.g. 95), you only need two digits for the date to be recorded. If you are unsure of your Date style, you can always double-click on any date field and enter dates via the calendar control. Similarly, the time fields are controlled by the Time Style specified by your Regional Settings; for instance, if your Time Style includes a seconds or AM or PM designation, your time values must be entered in this same format in order to be recorded. The grid will require as many parts of the Time Style as specified in the Control Panel setting. For instance, if your time style is 'HH:mm', the grid will require only that a twenty-four hour time and the minutes, but no seconds be entered. · International Number Format. All numeric values in ARCHIBUS/FM use the decimal and group separators specified in the "Number" tab of the Windows Control Panel, rather than the "Currency" tab. If you make a selection from the "Regional Settings" tab (e.g. for French), these values will be set for you. They will take effect the next time you start ARCHIBUS/FM. · Export. Please note that the Export command is subject to the limitations of the Microsoft ODBC drivers and of the destination file format. For instance, you cannot export all fields of the Employee table to .Dbf format, because on one of the field names ("Image") dBase holds as a reserved word. You cannot export certain Comment fields to text format, because they are too long for the text format driver. As dBase uses only ten characters to identify field names, if you have longer field names which begin identically, you cannot export both fields at the same time to .Dbf format. As a working method, if you have trouble exporting a table, try eliminating fields from the export until it succeeds. Please also refer to the Afm_Abs.Txt file for more hints on using Import and Export. · Import, Export, and the Update Project Wizard. If you have used the Update Project Wizard, and you directed all output to an SQL script file, you may find that the Import and Export commands have no apparent effect. The reason is that the output is still directed to the script file. Clear this setting by removing the Echo SQL Statements To Script File? preference in the Internal section of the Afm11.Ini file, located in you Windows system directory. · Auto-Commits. MS SQL Server and Oracle versions auto-commit their changes, as otherwise, the database drivers leave the tables locked. As such, you cannot undo database actions. Using Report Windows · Default Printer. If your report windows do not appear, verify that you have a default printer installed, as the report windows need information from the print driver as to how large to display text. If you do not have a printer, you may wish to install the "Generic/Text Only" driver as a default. · Printing to Files. You may wish to print ARCHIBUS/FM reports to a file. This is particularly useful for sites that use the Adobe Distiller to convert PostScript ARCHIBUS/FM output into Adobe .Pdf files that can be distributed electronically. If your printer driver supports printing to a file, a "Print to file" toggle will appear on the Print dialog box. For some network printer drivers, this toggle may appear but will be inaccurate, since the network printer will not be able to place a file on your local hard drive: the driver will hang and with it the ARCHIBUS/FM application. To avoid this problem, use the Windows Settings/Printers/Add Printer to add a local printer that uses the same driver. When printing as a local printer, the driver will prompt for the name of the file to print to. · Report Page Width. V11 uses a WYSIWYG report preview mode. Unlike V10, this means that fields that do not fit on your page are not seen by default. If you wish to see all fields of data for a view, use the Reports tab of the Preferences dialog to turn Width Clipping off. So that as many fields appear as possible, the default Page Orientation is "Landscape." To change your Page Orientation, change this setting in the Reports tab of the Preferences dialog. To reduce the number of fields in a report, use the Select Fields command. · Report Page Size. To set the report page size to large sizes (e.g. 11x17, 22x34, etc.), you need to use File/Print Setup to choose a printer that can draw this size page (e.g. the Phantom AutoCAD OLE/ADI Printer). You need a printer configured because with the new print-preview style of report viewing, the program must ask the current printer how large each style of text will be when actually printed, as the screen and the printer font sizes are different. Using Drawing Windows · Auto-Infer. If you use the Auto-Infer drawing preference and you use the Insert Asset command, please notice that the asset does auto-infer its room location; however, the room value only will show in the grid after you use the Grid/Requery command. · Number. Please notice that if you use the Number command to number a series of rooms, you must press the escape key (Esc) to end the command. Making other menu selections, such as Undo, will not end the command. In ARCHIBUS/FM, if you use the Attach to Record option, Number will replace the existing record; if used in the Overlay, it will link to the existing record. · Explode. In ARCHIBUS/FM 11, the Explode command does not let you explode blocks into entities or polylines into lines if those blocks or polylines are on an asset layer. This is because you should only use whole blocks and polylines for asset symbols. · Copying and Pasting Blocks. If you use the Copy and Paste command to move block insertions from one drawing to another, you will get a warning if the destination drawing does not have that block definition loaded. You can load that definition using the Insert Block command, and then Paste. · External References. This version of ARCHIBUS/FM does support AutoCAD external references. Early beta versions did not. ARCHIBUS/FM Overlay for AutoCAD Usage Notes · AutoCAD 2000 and MDI. Under AutoCAD 2000, the ARCHIBUS/FM Overlay starts in a single-document mode rather than multiple-document (MDI) mode. To work with MDI mode type "AfmUnload"; invoke the the AutoCAD Options command, and use the System tab to turn off Single Drawing Compatibility mode; then open and work with multiple drawings. If you wish to work on your assets again, close all but one drawing, and type "Afm" to reload the Overlay. · AutoCAD 2000 and AutoCAD R14 Files. If you save a drawing from AutoCAD 2000, AutoCAD 2000i, or ARCHIBUS/FM 11.3 and then load it in AutoCAD R14; you will see a message stating that there are several proxy objects that will not display. Press OK to ignore this message. These are administrative objects that AutoCAD 2000 adds to preserve round-trip information. They do not affect the performance or display of the drawing file in AutoCAD R14. Autodesk is aware that this message comes up, and considers it to be by design. · AutoCAD 2000 and Web Central. If you will be generating .Dwf files from AutoCAD 2000 for use with ARCHIBUS/FM Web Central, be certain to use the "Custom" installation for AutoCAD 2000 and specify that the Internet Utilities should be installed with AutoCAD 2000. Otherwise, the Internet drawing publishing features of Web Central will not run. · Using Cut, Copy, and Paste. When you cut and paste a set of asset symbols inside AutoCAD, please notice that AutoCAD pastes the assets as one block. If you explode the block, you will be able to work with the individual asset symbols with the ARCHIBUS/FM Overlay. · Number. If you use the Number command to number Room asset symbols on one drawing, and then you open another drawing, be certain to use the Set Defaults button to verify that your Building Code and Floor Code defaults are appropriate for that second drawing, as the defaults established for the first drawing will be carried over to the second drawing. ARCHIBUS/FM Modules Usage Notes · Hoteling Book Rooms Action. Under Sybase, the Show Available Rooms dialog of the Book Rooms view works in conjunction with any Room Standard specified in order to list only those Buildings and Floors that have at least the specified number of vacant rooms of the specified Room Standard. Due to differences in SQL language syntax, under Oracle this Room Standard filter is not applied. However, with both databases the Room ellipsis (...) list button does limit the list of rooms to only those of the specified Room Standard type. · Hoteling Unassigned Vacancies. Under Sybase, the Room table's Unassigned Vacancies field of the Book Rooms view shows the standard employee headcount for a room of that standard type, minus the permanently assigned employees, and minus the number of employees currently hoteled in that room for the specified date range. Due to differences in SQL language syntax, under Oracle this field does not subtract the number of currently hoteled employees. However, the number of currently hoteled employees is displayed in the grid holding the assigned Room Percentages table (displayed beneath the Rooms grid) so that you can see the number of hoteling vacancies. · Editing the Schema Database. Authoring users who are changing the Schema database should use the New Project command to create an .apj file that loads the schema database and creates the ODBC entries for the schema. Remember to change the Database Folder value to your \afm11\schema folder location and remember to turn off the Create Database toggle. Once you have established this project entry, you can connect to your schema database by using the Open Project command from the menu, by using the Projects tab of the ARCHIBUS/FM Explorer, or by using the Open Schema task from the Navigator. Microsoft SQL Server Usage Notes If you use ARCHIBUS/FM with the Microsoft SQL Server database, please be aware of the following usage notes. · Cascading Updates. If you have problems creating, updating, or deleting assets or records; check that the value of the Use ARCHIBUS/FM Function for Cascade Schema Preference is set to "Yes". This preference controls whether ARCHIBUS/FM cascades changes from one table, such as the Buildings table to dependent tables, such as the floors table. The preference is accessible from the Navigator in the \System\Schema\Control\Schema Preferences view. If you change this preference, use Reset Schema or reload the project to have it take effect. · MS SQL Column-Format Grid. If you update a record in a column format grid (e.g. a two column grid), the grid will requery when you use the Prev or Next keys to step off the record. This is necessary to refresh the data buffered for the grid. · Delete Table Command. If you delete a table that has child records, you will get an SQL error since the records are deleted in bulk, and the bulk change does not cascade. · Replace Column. You should use the Replace Column command only in views that do not contain a standards table. Known Limitations of this Version The following are known issues with the current version. · Drawing Focus. If you load a drawing view that contains view actions, you must select the grid window, then the drawing window, before using the toolbar buttons for the drawing commands. The reason for this is that the view action menu has captured the input focus. This is not an issue on the Essential Process Toolbars, which do not use the view action menu. · Blocks and Entity Selection. Due to a limitation in the underlying OEM component, this version cannot use blocks which contain text entities. Also due to a limitation in the component's display list, if you move the first entity in the drawing, you may see a "phantom" copy left behind. Regenerate the drawing to clear this phantom. · Background Color. You cannot set your background color to white, as this is not allowed with the current version of the Autodesk OEM component. The documentation should not mention this drawing preference. · Large Image Files in EIS. On Windows 98, using large images files (e.g. 1MB) can freeze the program. These are typically large .Bmp files mapped to a smaller area of the screen. If you encounter this issue, consider converting the files to the more compact .Gif format. This issue also applies to large .Bmp files used as report logo images. This is a problem with a licensed image component, and cannot be resolved by ARCHIBUS, Inc. directly. · Report Logos. On Windows 98, if you use your own report logo graphic, you must use only a small number of colors (e.g. 16) in the logo file. Larger number of colors can cause report views to freeze the program. This is a problem with a licensed image component, and cannot be resolved by ARCHIBUS, Inc. directly. · Show Explorer Tabs Preference. If you set this preference to "EIS Tab Only" and then change it back to "Show All Tabs", you must restart ARCHIBUS/FM in order for the change to take effect. · Set Field Widths. To keep these settings font independent, the program stores field widths as a number of average character widths in the current font. The conversion to the values in the Set Field Widths dialog is consistent, but not always intuitive. These values and behavior are exactly as they were in Version 10. · Select Fields. Under Windows 95 and 98, if you turn on many more fields than can be displayed on the visible page size you have chosen, the fields will wrap and overlap. Should this happen, turn off several fields. · Statistics in Multiple Table-Groups. If you define a view that uses statistics on two different table-groups, and the statistics are on fields that line up one beneath each other, their Overall Total values will overlap on your report. The work around is to use the Select Fields command to change the order of the fields so that they do not line up one beneath each other. · AutoCAD Convert Command. You must thaw all layers with polylines before using the AutoCAD CONVERT command; otherwise AutoCAD terminates. This is an AutoCAD issue: you will see the same behavior without the ARCHIBUS/FM Overlay loaded. This is important for sites using the room trial features of the Strategic Master Planning module, which requires that polylines be converted before use. · Lease Chargeback Agreements. For lease costs that are not of the type All-None-Bill Direct, the Lease Chargeback Agreements will not take effect. Please note that the regular lease costing, lease chargeback, rollups, etc. are unaffected by this issue; only those Leases for which you have defined a Lease Chargeback Agreement can be affected by this issue. · Auto-Commit Specific Tables. This schema preference works as designed and does in fact commit the records after every change; however, the "Commit" command will still be enabled on the File menu, even after the program has performed an "auto-commit". There is no harm in using the menu command to manually commit your changes, but it is not necessary. Also, when you load a new view, the program may still ask you if it should commit your changes. You can answer either Yes or No to this prompt, either way your changes are already "auto-committed." If you do not wish to see this prompt, set your the Auto-Commit View Preference back to "Yes," its default setting. · Update Project Wizard. If you have an Oracle destination database, if you are writing your changes to a .Sql script file rather than executing them directly, and if you have an autonumbered table that does not yet exist in the destination database; the wizard will print an error and stop. To continue, apply the .Sql script file to the destionation database, and re-run the wizard. Corrections to Documentation · Strategic Master Planning Book. In the first printing of this book (document number AFM11_SMP_1.00), the "Departments" and "Department Level Program" tasks referenced on page 30 present the Space Budget Items table; accordingly, the images on page 31 and 32 should show the Space Budget Items table instead of the Space Budget Items table assigned to the Departments table. Also, in the second image on page 39, the Room Standard field should have SQM or SQFT as its value to illustrate that Example 4 uses the Area Standard method. Also, Example 2 on page 35 should instruct you to run the "Standards" or "Standards Level Program" task. · ARCHIBUS/FM Overlay for AutoCAD book. In the first printing of this book (document number AFM11_OV_1.00), page 70 incorrectly states that uncataloging removes the extended entity data (table name, primary key, and standard) from an asset symbol. This is not the case; the drawing entity retains its attached xdata. Running Asset Explode removes the entity xdata. · ARCHIBUS/FM for Sybase Book. You no longer need to use the Sy55To60.Abs BasicScript to update your databases for Adaptive Server Anywhere, as that is the new default distribution format for the schema.db and hq.db files. If you do use this script to update another SQL Anywhere 5.5. database, restart the ARCHIBUS/FM program before reconnecting to the newly updated database. Should you be using ARCHIBUS/FM with Sybase SQL Anywhere, copy the schema55.db and hq55.db files over the schema.db and hq.db files. The ARCHIBUS/FM for Sybase book lists the location for the multi-user client files as \Afm11\Wsql. These files are now installed to \Afm11\DbClient. The ARCHIBUS/FM Setup.Exe program automatically updates your Sybase ASA Multi-User Client and the Sybase ASA ODBC Driver preferences to account for this change when you install ARCHIBUS/FM. · System Management Help. You should use the Update Project Wizard in place of the Update Project and Update Schema commands. Please refer to the online System Management Help for more details. Version 10 Compatibility · V10 Compatible. V11 can work on any V10 database or drawings without your needing to change the V10 database or drawings in any way. · V10 HQ Project Preserved. The V11 setup.exe installs a new \afm11\projects\hq sample project, even if you already have an \afm10\samples\hq sample project. · V10 Schema Database Preserved. The V11 setup.exe installs a new schema database in \afm11\schema. Therefore, you don't overwrite the version 10 schema database (located in \afm10\schema) when installing version 11. Version 10 BasicScript Compatibility · Type-Checked Scripts. Any Version 10 script that uses OPTION EXPLICIT for clean type checking (as recommended by the ARCHIBUS/FM Customization manual) will load unchanged in Version 11. If you did not use OPTION EXPLICIT, you can still load your script files in Version 11. You may need to declare forward references to functions (i.e. calls to functions that appear later in the script file). · 16-Bit DLL Calls. Some rare scripts, such as those that call Windows API functions, call 16-bit DLL files (e.g. User.Dll). These must change to use 32-bit DLLs (e.g. User32.Dll). Please refer to sup.abs for an example of starting the help system by means of this kind of DLL call. · Redeclaring the "Main" Statement. You cannot redeclare "Main", e.g. "Declare Sub Main()". If you need to call the main function, use a stub to call the functionality. Please see Process.Eis for an example of such a stub. · Using the "Set" Statement. Any statement you have in the form " · The "InStr" Function. In v10, the "start" parameter was optional for the function InStr( start, search, find [,compare] ). In V11 the "start" parameter is required if you also include the compare parameter; otherwise you will get a type mismatch error. The start parameter should be 1 in most cases. The compare parameter is still optional. · The "PromptVal" Function. When using the Avw.PromptVal function, specifying a fixed array as the owner key values -- e.g. "Dim OwnerKeys$(0)" -- will cause an error in V11, which catches your attempt to redimension a fixed-size array. Instead, use "Dim OwnerKeys$()" · The "Menu" Function. Calls to the Menu() and MenuItemEnabled() functions are not supported, as these use Windows 3.1 protocols not supported with Win32 menus. Refer to the AfmMenu() and AfmMenuItemEnabled() commands documented in \afm11\doc\afm_abs.txt. These functions duplicate this functionality for specific ARCHIBUS/FM commands. · The "Msg" Reserved Word. The token "Msg" is now a reserved word and cannot be used as a variable name. Rename any variables called "Msg" to another name, e.g. "sMsg". · Combined MsgBox Constants. Using logical "&" to combine MsgBox constants was treated as logical "Or" in V10, but is correctly treated as "And" in V11. For instance, MsgBox "Continue?", ebYesNo & ebQuestion, "Message Title" will show the Yes and No buttons in V10, but only the OK button in V11. Using "Or" instead will give the V10 behavior, which is most likely what was intended. · Short-Date Formats. The Version 11 installation automatically adjusts the Windows short date format to use a four-digit year. This is not necessary for the ARCHIBUS/FM schema, but is necessary for any custom schemas that use date manipulations that use the short date format, e.g. 'strDate = Format$(ISOtoBasic(prompt_min_date), "Short Date")'. If your Windows short date format is two digits, statements like the preceding one will strip off any century specification. To avoid this issue altogether, custom schemas should use statements of the form 'strDate = Format$(ISOtoBasic(prompt_min_date),WindowShortDateWithFourDigitYear)'. Revision History for ARCHIBUS/FM 11 Please refer to the \Afm11\Doc\RevisionHistory.Doc file for a list of additions and changes made between ARCHIBUS/FM 10 and ARCHIBUS/FM 11. The ARCHIBUS/FM software is Copyright 1984-2000, ARCHIBUS, Inc. All Rights Reserved. Portions of the software are copyrighted (C) 1992-1996 Summit Software company. ARCHIBUS/FM is Powered with Autodesk TechnologyTM and portions of the software are (C) 1992-2000 Autodesk, Inc. Some Illustrations Copyright 1998. TASK FORCE Clip Art. Used with permission. {\rtf1\ansi\deff0\deflang1033{\fonttbl{\f0\froman\fprq2 Times New Roman;}{\f1\fswiss\fprq2 Arial;}{\f2\fnil\fcharset2 Symbol;}} {\colortbl ;\red0\green0\blue0;\red0\green0\blue255;} \viewkind4\uc1\pard\f0\fs20\par \b ReadMe.Doc\par Release Notes for ARCHIBUS/FM Version 11 \par 01.09.1999 / 09.25.2000\par \b0\par This file includes the release overview, system requirements, installation notes, known limitations, and general information not available at the time the documentation went to press.\par \par \par \ul\b\fs28 System Requirements\ulnone\b0\fs20\par \par Minimum:\par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360 Pentium PC, 133 Mhz or faster\par {\pntext\f2\'B7\tab}32MB RAM or more \par {\pntext\f2\'B7\tab}800x600 SVGA display or better \par {\pntext\f2\'B7\tab}Windows 95B, Windows 98, Windows NT Service Pack 3 or later, Windows 2000\par {\pntext\f2\'B7\tab}100 MB free Hard Disk space\par {\pntext\f2\'B7\tab}AutoCAD R14 or AutoCAD 2000 (for Overlay users only)\par \pard\par Recommended:\par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360 Pentium PC, 200 Mhz or faster\par {\pntext\f2\'B7\tab}92MB RAM or more \par {\pntext\f2\'B7\tab}1024x768 or higher resolution display\par \pard\par ARCHIBUS/FM works with the following databases:\par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360 Sybase SQL Server 5.5 and Adaptive Server Anywhere 6.0, 7.0 \par {\pntext\f2\'B7\tab}Microsoft SQL Server 7.0 SP1\par {\pntext\f2\'B7\tab}Oracle 7.3, 8\par \pard\par \par \cf1\ul\b\fs28 Installation\par \ulnone\b0\fs20\par To install ARCHIBUS/FM 11:\fs24\par \b\par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360\i\fs20 Backup\b0\i0 . Back up your ARCHIBUS/FM project directories, as well as any custom views or database schema files you might have.\par \pard\par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360\b\i Uninstall\b0\i0 . You do not need to uninstall previous versions of ARCHIBUS/FM 10, as Version 10 and Version 11 can run on the same machine. However, if you have a previous version of ARCHIBUS/FM 11, uninstall it using these steps:\par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent374{\pntxtb\'B7}}\fi-374\li720 Use the Add/Remove Programs options from the Control Panel to remove the ARCHIBUS/FM 11 application. Answer "Yes" to the prompts to delete shared files -- these files are older versions of the ARCHIBUS ActiveX FM Objects. \par {\pntext\f2\'B7\tab}Restart the machine.\par {\pntext\f2\'B7\tab}Use the Windows Explorer to delete remaining files in your \\afm11 directory tree (as the uninstall from the Control Panel will not delete any read-only files, files that were in use during the uninstallation process, or files that were created after the program was installed). You may wish to keep your project preferences (.apj) files, your project folders, and any custom view (.avw) or script (.abs) files that are in this directory tree.\par \pard\par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360\b\i Setup\fs24 .\i0 \b0\fs20 Run the Setup.Exe routine on the CD-ROM. The setup program will prompt you for your license disk. The setup program will then ask you to restart your computer before running ARCHIBUS/FM 11.\par \pard\li360\b\i\fs24\par \pard\cf0\b0\i0\fs20 Please see the appropriate server manual -- ARCHIBUS/FM for Oracle, ARCHIBUS/FM for Microsoft SQL Server, or ARCHIBUS/FM for Sybase -- for installation instructions. See also the \i TroubleShooting.Doc\i0 file for additional release notes.\par \par \cf1\b\i\fs24\par \ul\i0\fs28 Version 11 Revision 3 Release Notes\ulnone\i\fs24\par \pard\li360\b0\i0\par \pard\fs20 Version 11 Revision 3 contains the following major additions. Please also refer to the RevisionHistory.Doc file for more detailed information on changes to the program.\par \par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360\tx360\b\i AutoCAD 2000 Support within ARCHIBUS/FM\b0\i0 . The ARCHIBUS/FM drawing editor now reads and writes AutoCAD 2000 drawings directly. AutoCAD R14 format is also still supported. This feature comes from a new drawing component that is supplied by Autodesk and that is based on the same technology that is in AutoCAD 2000 itself. To have AutoCAD 2000 support within ARCHIBUS/FM you must have a new license file for Version 11.3. ARCHIBUS, Inc. issues an updated license file to any site that has a license for the ARCHIBUS/FM Overlay for AutoCAD 2000.\par \pard\b\i\par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360 ARCHIBUS/FM Drawing Speed. \b0\i0 Drawing operations within the ARCHIBUS/FM drawing editor -- such as creating assets, cataloging a layer, or populating -- give better progress feedback and are twice as fast as they were within Version 11.2. (For comparison, the ARCHIBUS/FM Overlay for AutoCAD is five times as fast as 11.3 at these operations; so those with heavy drafting needs will still wish to use the Overlay.)\par \pard\b\i\par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360 Drawing List command. \b0\i0 There is now a Delete button on the drawing list. You can use this to remove a drawing from the list of drawings in the project and, if desired, to delete the associated drawing file as well. \b\i\fs24\par \pard\par \pard\li360\par \pard\ul\i0\fs28 Version 11 Revision 2 Release Notes\par \par \ulnone\b0\fs20 Version 11 Revision 2 contains the following major additions. Please also refer to the RevisionHistory.Doc file for more detailed information on changes to the program.\b\par \b0\par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360\tx360\b\i ARCHIBUS/FM for MS SQL Server\b0\i0 . MS SQL Server support requires Version 11 Revision 2 or later.\par \pard\par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360\tx360\b\i ARCHIBUS/FM Overlay for AutoCAD 2000\b0\i0 . AutoCAD 2000 support also requires Version 11 Revision 2 or later.\par \pard\b\i\par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360 ARCHIBUS/FM for Oracle 8\b0\i0 . Version 11 Revision 2 has been verified against both Oracle 7.3 and Oracle 8. \par \pard\par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360\tx360\b\i Sybase Adaptive Server Anywhere 6.0 for Single-User versions\b0\i0 . The single-user version now installs Adaptive Server Anywhere 6.0 rather than SQL Anywhere 5.5 for the Single-User (Runtime) version.\par \pard\par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360\b\i ARCHIBUS/FM Update Project Wizard\b0\i0 . With V11.2, the application control program ships with the Update Project Wizard, a utility that can migrate ARCHIBUS/FM data and schema between projects -- regardless of whether those projects are on Sybase Adaptive Server Anywhere 6.0, Oracle 7.3, Oracle 8, or MS SQL Server 7.0.\par \pard\b\i\par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360 Cascading Updates and Deletes\b0\i0 . The application control program handle cascading updates for Oracle and MS SQL Server databases. This eliminates the need for custom schemas to maintain a complex set of triggers for cascading changes. The updates are made using bulk statements executed on the server so that performance is not affected.\par \pard\par \cf2\par \cf1\ul\b\fs28 ARCHIBUS/FM Program Usage Notes\par \par \ulnone\b0\fs20 This section aims to clarify several aspects of the program. Even if you are familiar with a previous version of ARCHIBUS/FM, please review these usage notes.\par \ul\b\fs28\par \ulnone\fs24 General Notes\b0\fs20\par \ul\b\fs28\par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360\ulnone\i\fs20 Process Toolbars\b0\i0 . If you are using an 800x600 display, and if you have your Show Explorer Tabs set to "Show All Tabs", you should use only one row of command toolbars so that the complete process toolbars display. To turn off the second line of toolbars, right-click over any toolbar, and clear the checkmark next to that toolbar's name. If you have a custom EIS with large images and would prefer not to turn off toolbars, use the 'Scale Image' option for your images rather than the 'Centered' option to have them scale to fit the available area.\par \pard\par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360\b\i Windows Explorer Associations\b0\i0 . If you double-click on an ARCHIBUS/FM file (e.g. an .abs, .eis, .apj, or .avw file) in the Windows Explorer or on a desktop shortcut, or if you drag-and-drop it onto ARCHIBUS/FM, the program will load that file. If you wish to edit the file instead, use the right click menu on that file and use the Edit option. If you wish to change the association, use the View/Options command on the Windows Explorer.\par \pard\par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360\b\i Adding to the Hotlist\b0\i0 . On the ARCHIBUS/FM Explorer Hotlist, the Add Item and Item Properties commands are changed slightly from the documentation. The "Close" button replaces both the "OK" and "Cancel" buttons. To add an item, use the "Add" button and then the "Close" button. To change an item, use the "Update" button and then the "Close" button.\par \pard\par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360\b\i Navigator Context Help\b0\i0 . When invoking help on the Navigator using the context menu, remember the help topic loaded will be for the item beneath the tip of the arrow cursor -- not the center of the cursor. As the cursor is larger than the text of the Navigator, this is sometimes confusing.\par \pard\par \par \b\fs24 Using Grid Windows\b0\fs20\par \par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360\b\i Entering Date and Time Values\b0\i0 . If your Control Panel's Regional Settings use a four-digit date (e.g. 1995), you must enter all four digits for the date to be recorded. If your Control Panel specifies a two-digit date (e.g. 95), you only need two digits for the date to be recorded. If you are unsure of your Date style, you can always double-click on any date field and enter dates via the calendar control. Similarly, the time fields are controlled by the Time Style specified by your Regional Settings; for instance, if your Time Style includes a seconds or AM or PM designation, your time values must be entered in this same format in order to be recorded. The grid will require as many parts of the Time Style as specified in the Control Panel setting. For instance, if your time style is 'HH:mm', the grid will require only that a twenty-four hour time and the minutes, but no seconds be entered.\par \pard\par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360\b\i International Number Forma\b0\i0 t. All numeric values in ARCHIBUS/FM use the decimal and group separators specified in the "Number" tab of the Windows Control Panel, rather than the "Currency" tab. If you make a selection from the "Regional Settings" tab (e.g. for French), these values will be set for you. They will take effect the next time you start ARCHIBUS/FM.\par \pard\par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360\b\i Export\b0\i0 . Please note that the Export command is subject to the limitations of the Microsoft ODBC drivers and of the destination file format. For instance, you cannot export all fields of the Employee table to .Dbf format, because on one of the field names ("Image") dBase holds as a reserved word. You cannot export certain Comment fields to text format, because they are too long for the text format driver. As dBase uses only ten characters to identify field names, if you have longer field names which begin identically, you cannot export both fields at the same time to .Dbf format. As a working method, if you have trouble exporting a table, try eliminating fields from the export until it succeeds. Please also refer to the Afm_Abs.Txt file for more hints on using Import and Export.\par \pard\par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360\b\i Import, Export, and the Update Project Wizard\b0\i0 . If you have used the Update Project Wizard, and you directed all output to an SQL script file, you may find that the Import and Export commands have no apparent effect. The reason is that the output is still directed to the script file. Clear this setting by removing the Echo SQL Statements To Script File? preference in the Internal section of the Afm11.Ini file, located in you Windows system directory.\par \pard\par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360\b\i Auto-Commits\b0\i0 . MS SQL Server and Oracle versions auto-commit their changes, as otherwise, the database drivers leave the tables locked. As such, you cannot undo database actions.\par \pard\par \b\fs24 Using Report Windows\b0\fs20\par \par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360\b\i Default Printer\b0\i0 . If your report windows do not appear, verify that you have a default printer installed, as the report windows need information from the print driver as to how large to display text. If you do not have a printer, you may wish to install the "Generic/Text Only" driver as a default.\par \pard\par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360\b\i Printing to Files\b0\i0 . You may wish to print ARCHIBUS/FM reports to a file. This is particularly useful for sites that use the Adobe Distiller to convert PostScript ARCHIBUS/FM output into Adobe .Pdf files that can be distributed electronically. If your printer driver supports printing to a file, a "Print to file" toggle will appear on the Print dialog box. For some network printer drivers, this toggle may appear but will be inaccurate, since the network printer will not be able to place a file on your local hard drive: the driver will hang and with it the ARCHIBUS/FM application. To avoid this problem, use the Windows Settings/Printers/Add Printer to add a \i local\i0 printer that uses the same driver. When printing as a local printer, the driver will prompt for the name of the file to print to.\par \pard\par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360\b\i Report Page Width\b0\i0 . V11 uses a WYSIWYG report preview mode. Unlike V10, this means that fields that do not fit on your page are not seen by default. If you wish to see all fields of data for a view, use the Reports tab of the Preferences dialog to turn Width Clipping off. So that as many fields appear as possible, the default Page Orientation is "Landscape." To change your Page Orientation, change this setting in the Reports tab of the Preferences dialog. To reduce the number of fields in a report, use the Select Fields command.\par \pard\par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360\b\i Report Page Size\b0\i0 . To set the report page size to large sizes (e.g. 11x17, 22x34, etc.), you need to use File/Print Setup to choose a printer that can draw this size page (e.g. the Phantom AutoCAD OLE/ADI Printer). You need a printer configured because with the new print-preview style of report viewing, the program must ask the current printer how large each style of text will be when actually printed, as the screen and the printer font sizes are different.\par \pard\par \b\fs24 Using Drawing Windows\b0\fs20\par \par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360\b\i Auto-Infer\b0\i0 . If you use the Auto-Infer drawing preference and you use the Insert Asset command, please notice that the asset does auto-infer its room location; however, the room value only will show in the grid after you use the Grid/Requery command.\par \pard\par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360\b\i Number\b0\i0 . Please notice that if you use the Number command to number a series of rooms, you must press the escape key (Esc) to end the command. Making other menu selections, such as Undo, will not end the command. In ARCHIBUS/FM, if you use the Attach to Record option, Number will replace the existing record; if used in the Overlay, it will link to the existing record.\par \pard\par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360\b\i Explode\b0\i0 . In ARCHIBUS/FM 11, the Explode command does not let you explode blocks into entities or polylines into lines if those blocks or polylines are on an asset layer. This is because you should only use whole blocks and polylines for asset symbols.\par \pard\par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360\b\i Copying and Pasting Blocks\b0\i0 . If you use the Copy and Paste command to move block insertions from one drawing to another, you will get a warning if the destination drawing does not have that block definition loaded. You can load that definition using the Insert Block command, and then Paste.\par \pard\par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360\b\i External References\b0\i0 . This version of ARCHIBUS/FM \i does\i0 support AutoCAD external references. Early beta versions did not. \par \pard\par \par \ul\b\fs28 ARCHIBUS/FM Overlay for AutoCAD Usage Notes \ulnone\b0\fs20\par \par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360\b\i AutoCAD 2000 and MDI\b0\i0 . Under AutoCAD 2000, the ARCHIBUS/FM Overlay starts in a single-document mode rather than multiple-document (MDI) mode. To work with MDI mode type "AfmUnload"; invoke the the AutoCAD Options command, and use the System tab to turn off Single Drawing Compatibility mode; then open and work with multiple drawings. If you wish to work on your assets again, close all but one drawing, and type "Afm" to reload the Overlay.\par \pard\par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360\b\i AutoCAD 2000 and AutoCAD R14 Files\b0\i0 . If you save a drawing from AutoCAD 2000, AutoCAD 2000i, or ARCHIBUS/FM 11.3 and then load it in AutoCAD R14; you will see a message stating that there are several proxy objects that will not display. Press OK to ignore this message. These are administrative objects that AutoCAD 2000 adds to preserve round-trip information. They do not affect the performance or display of the drawing file in AutoCAD R14. Autodesk is aware that this message comes up, and considers it to be by design.\par \pard\par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360\b\i AutoCAD 2000 and Web Central\b0\i0 . If you will be generating .Dwf files from AutoCAD 2000 for use with ARCHIBUS/FM Web Central, be certain to use the "Custom" installation for AutoCAD 2000 and specify that the Internet Utilities should be installed with AutoCAD 2000. Otherwise, the Internet drawing publishing features of Web Central will not run.\par \pard\par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360\b\i Using Cut, Copy, and Paste\b0\i0 . When you cut and paste a set of asset symbols inside AutoCAD, please notice that AutoCAD pastes the assets as one block. If you explode the block, you will be able to work with the individual asset symbols with the ARCHIBUS/FM Overlay.\par \pard\par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360\b\i Number. \b0\i0 If you use the Number command to number Room asset symbols on one drawing, and then you open another drawing, be certain to use the Set Defaults button to verify that your Building Code and Floor Code defaults are appropriate for that second drawing, as the defaults established for the first drawing will be carried over to the second drawing.\par \pard\par \par \ul\b\fs28 ARCHIBUS/FM Modules Usage Notes \ulnone\b0\fs20\par \par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360\b\i Hoteling Book Rooms Action\b0\i0 . Under Sybase, the Show Available Rooms dialog of the Book Rooms view works in conjunction with any Room Standard specified in order to list only those Buildings and Floors that have at least the specified number of vacant rooms of the specified Room Standard. Due to differences in SQL language syntax, under Oracle this Room Standard filter is not applied. However, with both databases the Room ellipsis (...) list button does limit the list of rooms to only those of the specified Room Standard type.\par \pard\fi-360\li360\par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360\b\i Hoteling Unassigned Vacancies\b0\i0 . Under Sybase, the Room table's Unassigned Vacancies field of the Book Rooms view shows the standard employee headcount for a room of that standard type, minus the permanently assigned employees, and minus the number of employees currently hoteled in that room for the specified date range. Due to differences in SQL language syntax, under Oracle this field does not subtract the number of currently hoteled employees. However, the number of currently hoteled employees is displayed in the grid holding the assigned Room Percentages table (displayed beneath the Rooms grid) so that you can see the number of hoteling vacancies.\par \pard\par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360\b\i Editing the Schema Database\b0\i0 . Authoring users who are changing the Schema database should use the New Project command to create an .apj file that loads the schema database and creates the ODBC entries for the schema. Remember to change the Database Folder value to your \\afm11\\schema folder location and remember to turn off the Create Database toggle. Once you have established this project entry, you can connect to your schema database by using the Open Project command from the menu, by using the Projects tab of the ARCHIBUS/FM Explorer, or by using the Open Schema task from the Navigator.\par \pard\cf2\par \par \cf1\ul\b\fs28 Microsoft SQL Server Usage Notes\par \par \ulnone\b0\fs20 If you use ARCHIBUS/FM with the Microsoft SQL Server database, please be aware of the following usage notes.\par \par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360\b\i Cascading Updates\b0\i0 . If you have problems creating, updating, or deleting assets or records; check that the value of the Use ARCHIBUS/FM Function for Cascade Schema Preference is set to "Yes". This preference controls whether ARCHIBUS/FM cascades changes from one table, such as the Buildings table to dependent tables, such as the floors table. The preference is accessible from the Navigator in the \\System\\Schema\\Control\\Schema Preferences view. If you change this preference, use Reset Schema or reload the project to have it take effect.\par \pard\par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360\b\i MS SQL Column-Format Grid\b0\i0 . If you update a record in a column format grid (e.g. a two column grid), the grid will requery when you use the Prev or Next keys to step off the record. This is necessary to refresh the data buffered for the grid. \par \pard\par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360\b\i Delete Table Command\b0\i0 . If you delete a table that has child records, you will get an SQL error since the records are deleted in bulk, and the bulk change does not cascade.\par \pard\b\i\par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360 Replace Column. \b0\i0 You should use the Replace Column command only in views that do not contain a standards table.\par \pard\par \cf2\par \cf1\ul\b\fs28 Known Limitations of this Version\par \ulnone\b0\fs20\par The following are known issues with the current version.\par \par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360\b\i Drawing Focus\b0\i0 . If you load a drawing view that contains view actions, you must select the grid window, then the drawing window, before using the toolbar buttons for the drawing commands. The reason for this is that the view action menu has captured the input focus. This is not an issue on the Essential Process Toolbars, which do not use the view action menu.\par \pard\par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360\b\i Blocks and Entity Selection\b0\i0 . Due to a limitation in the underlying OEM component, this version cannot use blocks which contain text entities. Also due to a limitation in the component's display list, if you move the first entity in the drawing, you may see a "phantom" copy left behind. Regenerate the drawing to clear this phantom. \par \pard\par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360\b\i Background Color\b0\i0 . You cannot set your background color to white, as this is not allowed with the current version of the Autodesk OEM component. The documentation should not mention this drawing preference.\par \pard\par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360\b\i Large Image Files in EIS\b0\i0 . On Windows 98, using large images files (e.g. 1MB) can freeze the program. These are typically large .Bmp files mapped to a smaller area of the screen. If you encounter this issue, consider converting the files to the more compact .Gif format. This issue also applies to large .Bmp files used as report logo images. This is a problem with a licensed image component, and cannot be resolved by ARCHIBUS, Inc. directly.\par \pard\par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360\b\i Report Logos\b0\i0 . On Windows 98, if you use your own report logo graphic, you must use only a small number of colors (e.g. 16) in the logo file. Larger number of colors can cause report views to freeze the program. This is a problem with a licensed image component, and cannot be resolved by ARCHIBUS, Inc. directly.\par \pard\par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360\b\i Show Explorer Tabs Preference\b0\i0 . If you set this preference to "EIS Tab Only" and then change it back to "Show All Tabs", you must restart ARCHIBUS/FM in order for the change to take effect.\par \pard\par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360\b\i Set Field Widths\b0\i0 . To keep these settings font independent, the program stores field widths as a number of average character widths in the current font. The conversion to the values in the Set Field Widths dialog is consistent, but not always intuitive. These values and behavior are exactly as they were in Version 10. \par \pard\par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360\b\i Select Fields\b0\i0 . Under Windows 95 and 98, if you turn on many more fields than can be displayed on the visible page size you have chosen, the fields will wrap and overlap. Should this happen, turn off several fields.\par \pard\par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360\b\i Statistics in Multiple Table-Groups\b0\i0 . If you define a view that uses statistics on two different table-groups, and the statistics are on fields that line up one beneath each other, their Overall Total values will overlap on your report. The work around is to use the Select Fields command to change the order of the fields so that they do not line up one beneath each other.\par \pard\par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360\b\i AutoCAD Convert Command\b0\i0 . You must thaw all layers with polylines before using the AutoCAD CONVERT command; otherwise AutoCAD terminates. This is an AutoCAD issue: you will see the same behavior without the ARCHIBUS/FM Overlay loaded. This is important for sites using the room trial features of the Strategic Master Planning module, which requires that polylines be converted before use.\par \pard\par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360\b\i Lease Chargeback Agreement\b0\i0 s. For lease costs that are not of the type All-None-Bill Direct, the Lease Chargeback Agreements will not take effect. Please note that the regular lease costing, lease chargeback, rollups, etc. are unaffected by this issue; only those Leases for which you have defined a Lease Chargeback Agreement can be affected by this issue. \par \pard\par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360\b\i Auto-Commit Specific Tables\b0\i0 . This schema preference works as designed and does in fact commit the records after every change; however, the "Commit" command will still be enabled on the File menu, even after the program has performed an "auto-commit". There is no harm in using the menu command to manually commit your changes, but it is not necessary. Also, when you load a new view, the program may still ask you if it should commit your changes. You can answer either Yes or No to this prompt, either way your changes are already "auto-committed." If you do not wish to see this prompt, set your the Auto-Commit View Preference back to "Yes," its default setting.\par \pard\par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360\b\i Update Project Wizard\b0\i0 . If you have an Oracle destination database, if you are writing your changes to a .Sql script file rather than executing them directly, and if you have an autonumbered table that does not yet exist in the destination database; the wizard will print an error and stop. To continue, apply the .Sql script file to the destionation database, and re-run the wizard.\par \pard\par \ul\b\fs28 Corrections to Documentation\par \pard\tx360\ulnone\b0\fs20\par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360\tx360\b\i Strategic Master Planning Book. \cf0\b0\i0 In the first printing of this book (document number AFM11_SMP_1.00), \cf1 the "Departments" and "Department Level Program" tasks referenced on page 30 present the Space Budget Items table; accordingly, the images on page 31 and 32 should show the Space Budget Items table instead of the Space Budget Items table assigned to the Departments table. Also, in the second image on page 39, the Room Standard field should have SQM or SQFT as its value to illustrate that Example 4 uses the Area Standard method. Also, Example 2 on page 35 should instruct you to run the "Standards" or "Standards Level Program" task.\par \pard\tx360\par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360\tx360\b\i ARCHIBUS/FM Overlay for AutoCAD book. \i0 \cf0\b0\f1 \f0 In the first printing of this book (document number AFM11_OV_1.00), page 70 incorrectly states that uncataloging removes the extended entity data (table name, primary key, and standard) from an asset symbol. This is not the case; the drawing entity retains its attached xdata. Running Asset Explode removes the entity xdata. \cf1\par \pard\b\i\par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360 ARCHIBUS/FM for Sybase Book. \b0\i0 You no longer need to use the Sy55To60.Abs BasicScript to update your databases for Adaptive Server Anywhere, as that is the new default distribution format for the schema.db and hq.db files. If you do use this script to update another SQL Anywhere 5.5. database, restart the ARCHIBUS/FM program before reconnecting to the newly updated database. Should you be using ARCHIBUS/FM with Sybase SQL Anywhere, copy the schema55.db and hq55.db files over the schema.db and hq.db files.\par \pard\li360\par The ARCHIBUS/FM for Sybase book lists the location for the multi-user client files as \\Afm11\\Wsql. These files are now installed to \\Afm11\\DbClient. The ARCHIBUS/FM Setup.Exe program automatically updates your Sybase ASA Multi-User Client and the Sybase ASA ODBC Driver preferences to account for this change when you install ARCHIBUS/FM.\par \pard\b\i\par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360 System Management Help. \b0\i0 You should use the Update Project Wizard in place of the Update Project and Update Schema commands. Please refer to the online System Management Help for more details.\par \pard\b\i\par \par \ul\i0\fs28 Version 10 Compatibility\par \ulnone\b0\fs20\par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360\b\i V10 Compatible\b0\i0 . V11 can work on any V10 database or drawings without your needing to change the V10 database or drawings in any way.\par \pard\par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360\b\i V10 HQ Project Preserved\b0\i0 . The V11 setup.exe installs a new \\afm11\\projects\\hq sample project, even if you already have an \\afm10\\samples\\hq sample project.\par \pard\par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360\b\i V10 Schema Database Preserved\b0\i0 . The V11 setup.exe installs a new schema database in \\afm11\\schema. Therefore, you don't overwrite the version 10 schema database (located in \\afm10\\schema) when installing version 11.\fs24\par \pard\fs20\par \par \pard\fi-360\li360\ul\b\fs28 Version 10 BasicScript Compatibility\ulnone\b0\i\fs20\par \par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360\b Type-Checked Scripts\b0\i0 . Any Version 10 script that uses OPTION EXPLICIT for clean type checking (as recommended by the ARCHIBUS/FM Customization manual) will load unchanged in Version 11. If you did not use OPTION EXPLICIT, you can still load your script files in Version 11. You may need to declare forward references to functions (i.e. calls to functions that appear later in the script file).\par \pard\fi-360\li360\par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360\b\i 16-Bit DLL Calls\b0\i0 . Some rare scripts, such as those that call Windows API functions, call 16-bit DLL files (e.g. User.Dll). These must change to use 32-bit DLLs (e.g. User32.Dll). Please refer to sup.abs for an example of starting the help system by means of this kind of DLL call.\par \pard\fi-360\li360\par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360\b\i Redeclaring the "Main" Statement. \b0\i0 You cannot redeclare "Main", e.g. "Declare Sub Main()". If you need to call the main function, use a stub to call the functionality. Please see Process.Eis for an example of such a stub.\par \pard\fi-360\li360\par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360\b\i Using the "Set" Statement\b0\i0 . Any statement you have in the form " \pard\par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360\b\i The "InStr" Function\b0\i0 . In v10, the "start" parameter was optional for the function InStr( start, search, find [,compare] ). In V11 the "start" parameter is required if you also include the compare parameter; otherwise you will get a type mismatch error. The start parameter should be 1 in most cases. The compare parameter is still optional.\par \pard\fi-360\li360\par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360\b\i The "PromptVal" Function\b0\i0 . When using the Avw.PromptVal function, specifying a fixed array as the owner key values -- e.g. "Dim OwnerKeys$(0)" -- will cause an error in V11, which catches your attempt to redimension a fixed-size array. Instead, use "Dim OwnerKeys$()"\par \pard\fi-360\li360\par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360\b\i The "Menu" Function\b0\i0 . Calls to the Menu() and MenuItemEnabled() functions are not supported, as these use Windows 3.1 protocols not supported with Win32 menus. Refer to the AfmMenu() and AfmMenuItemEnabled() commands documented in \\afm11\\doc\\afm_abs.txt. These functions duplicate this functionality for specific ARCHIBUS/FM commands.\par \pard\fi-360\li360\par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360\b\i The "Msg" Reserved Word\b0\i0 . The token "Msg" is now a reserved word and cannot be used as a variable name. Rename any variables called "Msg" to another name, e.g. "sMsg".\par \pard\fi-360\li360\par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360\b\i Combined MsgBox Constants\b0\i0 . Using logical "&" to combine MsgBox constants was treated as logical "Or" in V10, but is correctly treated as "And" in V11. For instance, MsgBox "Continue?", ebYesNo & ebQuestion, "Message Title" will show the Yes and No buttons in V10, but only the OK button in V11. Using "Or" instead will give the V10 behavior, which is most likely what was intended.\par \pard\fi-360\li360\par \pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent360{\pntxtb\'B7}}\fi-360\li360\b\i Short-Date Formats\b0\i0 . The Version 11 installation automatically adjusts the Windows short date format to use a four-digit year. This is not necessary for the ARCHIBUS/FM schema, but is necessary for any custom schemas that use date manipulations that use the short date format, e.g. 'strDate = Format$(ISOtoBasic(prompt_min_date), "Short Date")'. If your Windows short date format is two digits, statements like the preceding one will strip off any century specification. To avoid this issue altogether, custom schemas should use statements of the form 'strDate = Format$(ISOtoBasic(prompt_min_date),WindowShortDateWithFourDigitYear)'.\par \pard\par \i \ul\b\i0\fs28\par Revision History for ARCHIBUS/FM 11\par \par \ulnone\b0\fs20 Please refer to the \i\\Afm11\\Doc\\RevisionHistory.Doc\b \b0\i0 file for a list of additions and changes made between ARCHIBUS/FM 10 and ARCHIBUS/FM 11.\par \par \par \i\fs18 The ARCHIBUS/FM software is Copyright 1984-2000, ARCHIBUS, Inc. All Rights Reserved.\par Portions of the software are copyrighted (C) 1992-1996 Summit Software company.\par ARCHIBUS/FM is Powered with Autodesk Technology\fs12 TM\fs18 and portions of the software are (C) 1992-2000 Autodesk, Inc.\par Some Illustrations Copyright 1998. TASK FORCE Clip Art. Used with permission.\i0\fs20\par \par \par } |
     |