>> The transfer process in a real-life upgrade is not always a
>> straight forward process - since you must ensure that new
>> fields are completed appropriately and any change to
>> constraints is appropriately managed during transfer.
> ATM, If there are additional fields/etc on the new database,
> i'm enforcing the new data via BEFORE INSERT triggers that
> provide default values. This is completely different to the
> triggers that i wanted to be disabled per the original
> question. Those triggers are mostly AFTER
> INSERT/UPDATE/DELETE ones.

As long as you are aware of the issue. In my upgrade process
all the triggers are disabled (or not defined), and so no
validation/assignment occurs - hence I must take care of it
during the transfer. I prefer it this way - it allows new
fields to be initialised in a different manner to what may be
required once the the fields are in use.

--
Geoff Worboys
Telesis Computing