EMu 1.0.500

Release Date: 9 June 2000

Requirements

New Features

  • A new reporting facility has been incorporated into EMu. Users can create reports from within the Windows interface. A list of fields to include in a report can now be selected. The new reporting system is extensible allowing new reporters to be "hooked in" as required. Reporting formats supplied include XML, CSV and ODBC. Report viewers supported include Crystal Reports, Microsoft Word, Microsoft Excel, XML viewer and standard Windows file associations.
  • Two new privileges control access to the reporting system. daReport is required by all users who are allowed to produce reports. daDesign allows users to create new reports.
  • Report files (e.g. Crystal Reports .rpt files) are now stored on the KE EMu server. Reports can now be share amongst all users without the need to copy the report to each client machine.
  • For EMu systems that support multiple data languages, reports can now be produced in any single language or all languages.
  • The standard TModuleFrm class has been split into two classes. A base TDataFrm class contains only the Admin tab without any legacy data. The TModuleFrm class adds legacy data and the Notes and Multimedia tabs. Using TDataFrm it is possible to build interfaces to tables that do not require multimedia support (e.g. audit databases, registry, etc).
  • Support for Virtual Reference Columns has now been added. It is now possible to display "reverse attachments" in a module (e.g. a list of Events for a given catalogue record). You can also query via virtual reference columns.
  • The Summary Data field can now be searched. A query field has been added to the Admin tab.
  • A new module interface has been built for the EMu Registry. Users with sufficient privileges can now modify the registry directly.
  • Module interfaces have been built for all audit databases (Condition Check, Internal Movements and Valuations). It is now possible to perform ad-hoc queries on audit trails and produce tailored reports.
  • The EMu Web interface now displays thumbnail images of catalogue, parties and taxonomy records when showing summaries.
  • The Ditto... command has been modified to use not only the last record inserted, but to also use the last record edited.
  • A Printer Setup...command has been added to the File menu allowing users to change the default printer. The Crystal Reports viewer has been altered to print to the default printer.
  • The ServerMediaPath registry entry has been superseded by the ServerPath registry entry. ServerPath defines the directory in which EMu has been installed on the server machine. ServerMediaPath defaults to ServerPath/multimedia, but can still be set to override the default value.
  • The multimedia Title field on the Multimedia query tab can now be used to perform attachment queries (with the Multimedia Repository).
  • A new KETextList components has been created to hold string lists. The component supports inheritance and can be used in conjunction with the TMultiLang component to provide language specific error messages.
  • The base Valuation, Condition Check and Internal Movement tabs have been altered to include audit trails on the tab. The Illumination information has been moved from the Condition tab onto its own Illumination tab.
  • Reverse attachment tabs for Events, Loans, Movements and Conservation have been included in the base catalogue module.
  • Reverse attachment tabs have now been added to all modules.
  • A new tab switching facility is available where registry entries are used to control the switching. See the EMu Registry web pages for details.
  • The Crystal Viewer supplied with EMu has been upgraded to Crystal Reports 8.0. French support for Version 8.0 has also been added.
  • Numerous site specific reports added to the Art Gallery of South Australia release of EMu (Gallery).
  • The Command Centre has been added to the list of modules visited by entering CTRL + TAB.
  • A new Attachments... command is available on the View menu. Selecting the command shows tabs for all modules that have reverse links to the current record. New options are available on the Display tab of the Options dialog. These options control how reverse references are displayed.
  • The order that EMu uses to find where Texpress is installed has been changed. It now looks in:
    ~emu/client/texpress/6.2
    ~emu/client/texpress
    ~emu/texpress/6.2
    ~emu/texpress
    ~texpress/6.2
    ~texpress

    in that order. It is now possible to have different Texpress licences for each EMu client installed.

Bugs Fixed

  • When loading a default value into a field that has focus the default value is now loaded correctly.
  • The New... button on the ditto selection form did not do anything. The button now launches a copy of the module so the user can select a ditto record.
  • The standard EMu cron file (.crontab) has been placed in etc/crontab. UWIN uses the file .crontab to store its own local entries. The file local/etc/crontab replaces the cron override file .crontab-local.
  • The Refresh... command could cause the Texpress server to crash. This has now been fixed.
  • Shortcut keys (up, down and leading letters) can now be used in comboboxes before the list is displayed.
  • When upgrading EMu, the emuinstall script now updates the html tree (via emuhtmlupdate) with any local pages.
  • When using hierarchies as part of a query, the correct subset of values is now displayed, rather than the complete list of values.
  • The EMu caching code has been updated to check modified times as well as file sizes to determine whether the cache entry is up to date.
  • The View Attachments button is now disabled if there are no attachments to be viewed.
  • There is no way to specify a command to translate a text file that is already in the right format (e.g. HTML file). A new registry entry of Convert|type|Command|None simply uses the input file as the translated text file without launching any filter process.
  • If the configuration file (etc/config) if EMUHTMLSERVERS was set to 0, a web server would still be started.
  • If you have more than 36 tabs the Tabs Menu showed incorrect shortcuts.
  • When performing a Ditto All command, mandatory fields were checked. This means you could not ditto an invalid record. Mandatory checking is now disabled when performing a Ditto All.
  • The Ok button on the replace dialog box would not be enabled if entries for the Find Text edit box were selected from a lookup table.
  • Under certain circumstances multi-level sorts would not sort records correctly.
  • If an attachment query is performed (i.e. via just entering terms) and their are no matches in the referenced database, then all records are returned from the reference database.
  • TexAPI error handling is not thread safe. It was possible to get the error Error: No Error when saving, reporting and performing other thread based functions. TexAPI 2.4.003 is now thread safe for error handling.
  • In an effort to rationalise registry names the |TableAccess| entry as been renamed to |Table Access| and |Access| has been renamed to |Column Access|.
  • A query of the form ^"phrase" or "phrase"$ would not be evaluated. The EMu query parser now generates the correct search statement for these types of queries.
  • When using the Refresh... command to update records where only the virtual reference fields have been modified (e.g. a location history record has been added), the record would not refresh correctly. Updates on virtual reference fields now refresh correctly.
  • Running reports where the Windows machine is configured to run in French, resulted in the reporting ODBC drivers failing to initialise. The problem is that French settings use a "," as the decimal character. The text ODBC schema.ini file now indicates that at "." is the correct decimal character. Note this means the windows locale settings must also use "." as the decimal delimiter.
  • If a control with associated buttons (view, attach, delete, attach, lookup) was hidden the associated buttons were displayed. The buttons are now hidden.
  • The Ditto command will generate an error the first time it is selected if a control does not have focus. The command is now disabled until a control has focus.

Upgrade Notes

There are three step involved in upgrading from a pre build 500 release (including the 500 Beta release) of EMu to a post 500 build. These steps are:

  1. Upgrade the server databases and registry to be consistent with release 500 requirements. To effect the upgrade:
    • Log in to the EMu server as emu.
    • Enter client client (where client is the client to be upgraded).
    • Enter cd utils
    • Enter sh upgrade-1-0-500
    • If the upgrade script produces a segmentation violation when running try ksh upgrade-1-0-500. The script contains long lines that cause problems with some Bourne shell implementations.
    • The client will now be upgraded. A number of files are created as the upgrade proceeds. The results of each database upgrade are placed in dbname.reloaddata where dbname is the name of the database modified. Any rejected records will be noted in these files.
  2. The switching tabs mechanism has changed in release 500. All switching tabs are controlled by the EMu Registry. The upgrade program will modify all defaultTabs registry entries, but will not update catalogue specific Tabs|Type entries. The upgrade programs will place these entries in the file ~emu/client/work/tabs.old. These entries must be upgraded by hand. See the EMu Registry web pages for details.
  3. A new reporting facility is provided in release 500. Unfortunately all old style reports cannot be upgraded. Each report needs to be updated and registered via the new reporting interface.
  4. The port numbers assigned to clients have changed. The default EMu setup allows server connections on one port (emu) and web connections on one other port (emuweb). The name of the client has been removed from the service name for default installations (when the primary client is being installed). See the EMu Installation service notes for details.

Once the upgrade is complete and you are satisfied that everything is working correctly, the upgrade log files can be removed:

  1. Log in to the EMu server as emu.
  2. Enter client client (where client is the client upgraded).
  3. Enter cd work
  4. Enter rm -f *.reloaddata *.old