RE: Putting a display file into production.

["Chris Bipes" <chris.bipes@xxxxxxxxxxxxxxx>]

We use versioning.  That is Application X with Display file zerba1 get a
new version of the display file called zerba2.  Once the new display
file is created in the save library as zerba1, the application get the
name of the display file changed to zerba2 and compiled.  You have to
change the application to use the new/modified/deleted stuff in the
display file so why not rename the display file?

Christopher Bipes
Information Services Director
CrossCheck, Inc.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
jmichael.smith@xxxxxxxxxxx
Sent: Thursday, May 10, 2007 8:42 AM
To: midrange-l@xxxxxxxxxxxx
Subject: RE: Putting a display file into production.

Yes, the potential exists to duplicate all display files.

I have found that display files follow the 80/20 rule.  Users normally
are in a few screens 80% of the time, normally these are the ones that
"can not wait" for a modification to be promoted.  Duplicate only those
that meet this criteria(or come to meet this critera).