Re: CASE designer/dictionary copying of model
Date: 9 Sep 1994 09:46:03 -0400
Message-ID: <34pour$ob9_at_andromeda.rutgers.edu>
jjacobs_at_well.sf.ca.us (Jeffrey Jacobs) writes:
>In article <34kssa$3cp_at_sundev.ntrust.org.uk>,
>Simon Holt <holt_at_ntrust.org.uk> wrote:
>>Simon Holt (holt_at_ntrust.org.uk) wrote:
[stuff deleted]
>The second approach is to use the migration facilities to
>export the application and then reload it. The steps involved
>are:
>1. Extract the desired application(s) using the extract
>utility. (These utilites are in the Managment Menu).
>2. Export the extract tables.
>3. Delete the extract tables
>4. Load the resulting .dmp file back in. It will
>warn you that an application of the same name exists
>and force you to rename the new application.
>All of this is described in the Administration manual,
>and the utilities are all in the same menu (whose name
>escapes me, since I only have 5.1.6 loaded).
>This second method also leaves the original application
>unfrozen, and allows parallel development.
Be careful with this if you share elements across applications. I'll give you an example to illustrate:
Application A Application B
Entity EMP Entity PO
Entity SALARY Entity PO ITEMS
Entity EMP (shared from App. A)
If you export Just Application B, case will "create" a new application called "01A" with the EMP Entity in it. Your export file will then contain:
Application 01A (Frozen) Application B
Entity EMP Entity PO
Entity PO ITEMS
Entity EMP (shared from App. 01A)
This can quickly cause a big mess when you bring Application B
back in and rename it. Unhooking the shared EMP Entity from
"01A" and hooking it back up with the EMP Entity from "A"
can cause some strange things to happen. I only tried this
once and ended up reverting to a previous backup.
I know this is off the original topic, but, hey, it can be a problem . . .
Rich Holowczak
Rutgers University
holowcza_at_andromeda.rutgers.edu
Received on Fri Sep 09 1994 - 15:46:03 CEST
