QUICK Screen Occurrence Checking

[Pickering, John (NORBORD)]

Carol

The behaviour you are describing is generated when you use the "lookup
noton" option on the field statement. Here's a quickie screen which will
demonstrate what you're after. In this case po-no is a key in the table
po-headers. 

>screen carol
>file po-headers primary occurs 6
>cluster occurs with po-headers
>field po-no lookup noton po-headers
>cluster
>go

Regards,
John Pickering
Toronto

> -----Original Message-----
> From:	Carol Kaffenberger [SMTP:kaffenbe@karmanos.org]
> Sent:	Friday, October 12, 2001 12:14 PM
> To:	powerh-l@lists.swau.edu
> Subject:	QUICK Screen Occurrence Checking
> 
> I'm having trouble with a QUICK screen that is allowing
> duplicate values to be entered for a field.  The logic works
> fine if the value is already updated in the file--the
> duplicate value is trapped.  The problem occurs when the
> value is added more than once on the same screen and that
> value does not exist in the file.
> 
> For example:
> 
> 
>       City#             City
> Name                                Zip
> 
> 01 1005 820200 ALLEN PARK                   02
> 48101              This value already exists in the file
> 
> 03 48222              This value does not exist in the file
> 
> 04 48222              This value does not exist in the file
> 
> 05
> 
> 06
> 
> I have other programs that trap this situation and give the
> message "This is the same key/index value as occurrence
> (03)".  I would like the same thing to happen here, but I
> have no idea what makes QUICK do this (because it is
> definitely not something we are coding).
> 
> Can someone explain how this works.
> 
> Thanks.
> 
> (MPE/ix 6.0, PH 8.39.C)
> 
> --
> Carol Kaffenberger
> Karmanos Cancer Institute
> Detroit, Michigan
>