No Duplicate in Quick

[Peter Bateman]

Brian:

I take your comments as compliments. Thank you.

As to how I got to the solution which Georgia has implemented.


There are a few things that we want to achieve when we are
doing software maintenance.

1) Address the underlying issue. In Georgia's case, users were
   duplicating previous values with the duplication shortcut key
   instead of entering correct data. However, in some cases duplicates
   of previous values were correct. Users don't intentionally mess up,  but
   if the can go wrong without warning they will.
.
2) Minimise the impact of the changes on the rest of the system.
   We could for example 'hide' the duplicate key in the QKGO
   and then program for '_' in the input procedure for every field
   on every screen that we want to allow the shortcut on. Needless,
   to say nobody would want to do this just so that the users would
   be force to enter something ( which could be the previous values )
   into two fields on one screen.

3) Minimise the impact of the changes on the users.
   We could for example 'hide’ the duplicate key in the QKGO
   and then put the DUPLICATE option on every field on every screen
   that we want duplicate allowed on. Now not only is this a lot of
   work but the users would have to learn a new way of entering data.
   It would also invalidate any QKIN files that use '_'.

So with these 3 objectives in mind I came up the solution of warning
the users if a critical field has been duplicated either by using the
shortcut or by entering the same value over again.

Regards,
Peter Bateman

_________________________________________________________________
Powerful Parental Controls Let your child discover the best the Internet has 
to offer.  
http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=http://hotmail.com/enca&HL=Market_MSNIS_Taglines 
  Start enjoying all the benefits of MSN® Premium right now and get the 
first two months FREE*.