Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community

At 23 JUL 1998 10:06:48PM Peter Richards wrote:

Using OI 3.2 and Revelation Reporter 3.2

Part of the dictionary for table DONORS is:

DONOR_NUMBER

PROJECT

LAST_DONATION_DATE

DONOR_NAME

The Revelation Reporter query states WITH PROJECT=CODE1" AND

WITH LAST_DONATION_DATE ]= "1-JAN-96"

The reporter displays the results as:

248 Fred Bloggs 1/12/98 CODE4

		11/8/95		CODE1
		2/23/94		CODE3

The third column is LAST_DONATION_DATE and the last column is

PROJECT. As you can see, DONOR_NUMBER (key) 248 should not have

been selected as the CODE1 project was prior to 1-JAN-96.

Obviously the key 248 was selected because of the date 1/12/98, (another project). I understand how the key item (248) was returned from the query, as OI doesn't view key selection on a "corresponding MV" basis, in the manner that AREV does, however the LAST_DONATION_DATE MV Options are set to:

* Treat as multiple records

* Return only values that match criteria

as are the MV options for column PROJECT ?

I have even tried putting the LIMIT clause in the Rev Reporter

query specifications, but errors were found in the syntax. Also, I have searched through the information on RR for MV reporting. One article:

] Subject: Reporter scrambles null MV fields

] Category: Reporter Specific

] Author: Lewis Richmond

] Date: 04/09/97 02:17 PM

] We have found that Reporter cannot handle multi-valued fields where ] some of the multi-values are null.

Therefore, I have checked all the data and ensured that there are no null values. Is there a patch for this, or a later version of RR than 3.2 ?

Peter

View this thread on the forum...

  • third_party_content/community/commentary/forums_nonworks/3f35ed76ea2908f68525664b000b9c3e.txt
  • Last modified: 2023/12/28 07:40
  • by 127.0.0.1