SCT_DB V 5.66 Installation Procedure
		-----------------------------------

Version 5.66 of the SCT database Omnis application adds some new
features and fixes several bugs.  The datafile formant is the same as
for version 5.60.

Version 5.60 of the SCT database Omnis application modifies the ITEMS
and TEST_LIMITS tables, so that the datafile needs to be updated as well
as the library.  It contains a cure for a problem that on rare occasions
resulted in corruption of the OWNER field of some records when merging
the local cache to the master server.  It also allows you to make a
quick check on the integrity of assembly records before starting a
merge.

IMPORTANT:  YOU SHOULD INSTALL VERSION 5.60 OR 5.66 BEFORE YOU MERGE
YOUR LOCAL CACHE, OR CONFIRM THAT A SHIPMENT WAS SENT OR RECEIVED.

Updating to version 5.66 from version >= 5.60
----------------------------------------------
To install version 5.66, just unpack the library 'sct_db5_66.lbr' from
the archive and replace your version 5.60 library.  You may wish to
rename the datafile to 'sct_db5_66.df1' so that it gets opened
automatically.

Updating to version 5.66 from version <= 5.52a
----------------------------------------------
If you are starting with version >= 5.40, you may keep your old datafile
(sct_db5_5x.df1).  Make a backup copy before doing the upgrade. You may
wish to rename the datafile to 'sct_db5_66.df1' so that it gets opened
automatically.

When you start up with version 5.66, you will be asked whether or not to
update your local datafile.  If you have made a backup copy, answer
'yes'.  Your datafile will be updated to version 5.60 without needing to
be rebuilt from a skeleton version as in the past.

Updating to version 5.66 from version < 5.40
----------------------------------------------
If you are starting with version < 5.40, you must replace your old
datafile (sct_db5_3x.df1) and rebuild it from a skeleton version.  When
you are prompted for a datafile, select sct_db5_6skeleton.df1, and
follow the prompts.  The process can take a considerable time.

Merging
-------
As soon as you have installed version 5.66 it would be a good idea to do
a normal merge of the local and master databases.  This will first start
the assembly integrity check which will ask you 'Should I attempt to
repair any errors?'.  Answer 'No' for now.

The Integrity check writes a file called 'integrity.txt'. Please send me
a copy of this if any errors are found so that we can decide what to do.

Good luck,
Joe 
<Joe.Foster@man.ac.uk>.