QUICK Screen Occurrence Checking

[Deskin, Bob]

You don't indicate what the file structure is. If you have a repeating
PRIMARY with a LOOKUP NOTON one of the fields, then QUICK should be checking
that field both in the file and in the cluster. The same thing happens if
you have a PRIMARY-DETAIL (or SECONDARY) and one of the fields in the DETAIL
is a LOOKUP NOTON the DETAIL.

The one case where this may be obvious is where you do a LOOKUP NOTON a
REFERENCE file. In this case, if you want to check both the file and the
cluster, you need to make the REFERENCE file OCCUR with the clustered file.
Otherwise QUICK will only check the file and not the cluster.

The above is how things are supposed to work. If you find otherwise, please
show us your code.

Bob Deskin              
PowerHouse Web Product Manager, Application Development Tools, Cognos Inc.
bob.deskin@cognos.com (613) 738-1338 ext 7268 FAX: (613) 727-1178
3755 Riverside Drive P.O. Box 9707 Stn. T, Ottawa ON K1G 4K9 CANADA

-----Original Message-----
From: Carol Kaffenberger [mailto: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



= = = = = = = = = = = = = = = = = = = = = = = = = = = =
Mailing list: powerh-l@lists.swau.edu
Subscribe: "subscribe" in message body to powerh-l-request@lists.swau.edu
Unsubscribe: "unsubscribe" in message body to
powerh-l-request@lists.swau.edu
http://lists.swau.edu/mailman/listinfo/powerh-l
This list is closed, thus to post to the list you must be a subscriber.
This message may contain privileged and/or confidential information.  If you
have received this e-mail in error or are not the intended recipient, you
may not use, copy, disseminate, or distribute it; do not open any
attachments, delete it immediately from your system and notify the sender by
e-mail promptly that you have done so.  Thank You.