EMu 1.0.412

Release Date: 7 September 1999

New Features

  • TexAPI is now linked statically into emu.exe. There is no need to distribute the TexAPI dll's as part of EMu. All InstallShield configurations have been modified to no longer include these dlls.
  • The Show Attachments facility (Attachments Menu) now uses the same viewing algorithm for displaying attachments as the View Attachments button view.gif. If a module is already being used for viewing attachments it will be used instead of a new form being opened.
  • The New Query... (File->New Query...) command and speed button newquery.gif now clear all query terms when starting a new query. If you want to use the terms from your last query, the Previous Query (File->Previous Query) command is available.
  • Users can now register their own sort orders. The Sort... command (Tools->Sort...) now allows users to not only select pre-defined sort orders, but also define a new sort order and associate a name with it. Users can identify who is allowed to use their new sort order. Note that only the person who creates a sort order may alter it.
  • A new Ad-hoc Sort... command (Tools->Ad-hoc Sort...) and speed button sortasc.gif are now available. A properties dialog is presented containing the sort order of the last Ad-hoc Sort. A user can define a new order without the need to associate a name with the sort.
  • Default values can now be set for Query and Insert modes. New registry entries have been added to support the setting of default values. The registry entries are:

    Group|groupname|Table|tablename|Insert Defaults|defaultsname|values
    Group|groupname|Table|tablename|Query Defaults|defaultsname|values


    where values is of the form:

    colname
    =value;colname=value;...


    Default values have a name associated with them (same as sorts, reports, etc). The reserved name Base Defaults may be used to define default values that apply all the time. These default values are set even if no named defaults are set. To set a named default value  use the registry entries:

    Group|groupname|Table|tablename|Insert Defaults Selected|defaultsname
    Group|groupname|Table|tablename|Query Defaults Selected|defaultsname


    where defaultsname is the named defaults to use (note that Base Defaults are loaded first).
  • A new operational privilege daDefaults is now available. Setting this privilege:  

    Group|groupname|Table|tablename|Operations|...;daDefaults;...


    allows the privileged user to define their own sets of named default values. They can also set security to control who can access the entry.
  • A new set of command are available for handling default values. The Load command (Edit->Default Values->Load) fills in the Query or Insertion form with the current set of default values. The Change... command (Edit->Default Values->Load), which is only available if the user has the daDefaults privilege, shows a list of the named defaults the user can use. The user may select one, which then becomes the new set of default values for the next Query/Insertion. It is also possible to define a new set of default values, by clicking on the New... button on the selection dialog. The Set As Defaults... command (Edit->Default Values->Set As Defaults) uses all the values set in the Query/Insertion form to define a new set of defaults. This provides a fast way of defining new default sets, by simply filling the form with the required values and using Set As Defaults. If some fields should not be used by this command the registry entry:

    Group|groupname|Table|tablename|Insert Defaults|Skip Columns|colname;colname;...


    can be used.

  • The EMu registry has been modified to remove all occurrences of single level default entries (e.g GroupDefault, Table Default, etc). The entries have been split into two levels, with the keyword Default on the second level. Thus GroupDefault becomes Group|Default. Now all registry entries of a given type have the same number of levels, irrespective of whether they are default entries or not.
  • The EMu registry entries for SortDefault and ReportDefault have been replaced with Sort Selected and Report Selected.
  • A new column access privilege, duQuery, is now available. A user must have this privilege in order to be able to change a control associated with a column at query time. It is analogous to requiring duEdit to be able to edit a value. If this privilege is not granted the controls associated with the column will be read-only. Thus it is possible to set a default value for a read-only column at query time and so restrict the search (eg. Object Status=Accessioned, would only find objects that have been accessioned).
  • Two new server side commands. emuregdump allows the contents of the EMu registry to be printed out. Normally the contents would be saved in a file and modified with an editor before being reloaded. emuregload reads a file from stdin and loads it into the registry. The input format is:

    owner:Level1|Level2|Level3|...|value


    where owner is the userid of the person who owns the registry entry.

    Drag and drop facilities have been added to the sort and defaults properties forms. You can drag fields from the top outline control into the list control below. On the security tab you can also drag users/groups from the top names list into the bottom access list. To view a list of users in a group simply double click on the group name in the access list.

Bugs Fixed

  • All server side scripts used to assume that the dbnameopts environment variable could be clobbered. All scripts have now been updated to preserve any dbnameopts settings while the scripts are executing.
  • The read-only versions of Check Boxes and Radio Buttons have been fixed so that users can no longer select them.

Upgrade Notes

  • Since the representation of  default values in the EMu registry has changed it is necessary to upgrade the EMu registry between releases 411 and 412. An upgrade program is provided on the server in the utils directory. To upgrade the registry run:

    regupgrade


    If the upgrade fails a copy of the registry data file is kept in .../data/eregistry/data.save.pid. The upgrade script can be run any number of times. It is designed to only modify entries that need to be refreshed.
  • Pre-412 EMu registries did not support the duQuery access privilege. In order to allow users to use controls at query time it is necessary to add this privilege. If it is not added all controls will be greyed out and cannot be used. To add the new privilege:
      1. Log in to the server as user emu
      2. Run texforms eregistry
      3. Enter dvQuery in the Search All field.
      4. Select Query (Function->Query) to retrieve the required records.
      5. Select Substitute in matching records (Edit->Substitute in matching records).
      6. Move down to the Value field and select Select item (Function->Select item).
      7. Enter existing text: of ^ (the caret character above the 6 key) and press enter.
      8. Enter a replacement text: of duQuery; and press enter.
      9. Choose Yes to confirm the substitution.
      10. Choose No to perform record validation.

 

The Registry is now upgraded. Note you may have to change individual registry entries depending on the access you want to provide to users for controls on the Query form.