subtract or scaning

[Duane Pederson]

Morning

I have a table with names, info, etc., linked to many other tables, one being a table of one to many of late & absents ( date, reason, ID #). I have reports of students and their dates of being late and / or absent.

I would like to make a report of students who were not absent throughout the year.

It looks as though I can use the subtract operation and make a table of those ID's who didn't have an absent day and then link this result table back to the primary to report on those who weren't absent.

Or the Scanning function may do it right in the report detail filter!

Can someone shed some light on this?

Thanks

Duane

[martinwcole]

RE: subtract or scaning

I believe scanning returns a logical value.

I use it to check for child records in onrowdoubleclick in embedded browses to deny the code if there are no child records

you can say
parent=customers
child=hearing aids
form(or report) is open on that set

if scanning("hearing aids") 'found some children
'code for event
else
end
end if

or I can say
if .not. scanning("hearing aids") ' didn't find any
end
end if
'code for event

[forskare]

RE: subtract or scaning

Duane,

Hey, it's 2:30 am and I'm wide awake. UGH!!! But...........I assume the table with the names is the parent table and the table containing the *absents* is a child table, linked 1:m to the names table.

Assuming you record a T or Y in the absent field in the child table if a child is absent, using a report, couldn't you set up an expression in the Report Detail that will show all names (parent table) where the absent field is:
is blank or the field is empty.

That's what I would try for a start.

kenn

[Tom Cone Jr]

RE: subtract or scaning

Duane,

Hey, it's 3:30 am. what am I doing out of bed?

It's not clear how you can distinguish a record of an absence from a record of a late arrival. Assuming you have a way to do that, then here's a brute force approach you might try.

1) unmark all the name records

2) invert the set, make the child table the parent, and the former parent becomes the child, linked one to one

3) run a query against the new parent table to find only the absentee records

4) mark each corresponding name record... i.e. mark only the name records in the current query list of absentee records

5) close the set, and open the original set, run your report but filter it so that only unmarked names are included.

6) to be tidy, remember to unmark all name records when finished.

This approach assumes that you only have records for the current student year in your tables...

The problem you're facing is how to identify things that 'aren't there'. You've recorded absences... and now you want to list the ones that have no absences... What I'm recommending is that you 'mark' the ones that had absences... and then run your report filtered for those who are 'not' marked.

If you put your lates in one table and your arrivals in a second table I think things would be easier. You could then use the exist() function to determine which name records don't have linked absentee records... You can't do that now because someone might have been late a few times, but never absent. Their name record would have one or more linked child records (because of the lates) but they were never absent.

Now back to bed.

-- tom

[Thomas Henkel]

RE: subtract or scaning

Couldn't you just put together another set of just student records to "absent" child records. (there MUST be a way of identifying them) The it is just a matter of using the .not.scanning to see those that have no absenses.

[Thomas Henkel]

RE: subtract or scaning

by the way,
you guys definitely stay up way too late at night.

[Duane Pederson]

RE: subtract or scaning

Afternoon (already)

Thanks for the replies
Making a new traditional set for the report and using the .not.scanning("absentees") worked just fine.
Using the original set, the scanning function was also picking up records from other one to many links in the set.
Making up the new set works just fine for finding the non absent/late students. Using a filter in the new set link properties to only use the absent/late field = "absent" kicks out the late kids from the reporting system.

I think all is well (for now).

Thanks
Duane