I am designing and devolping a solution... and need some help.

I will have a table with multiple records and would like to count the related records.

example:

(records)

#101, 36"x84" Wood

#102, 36"x84" Wood

#103, 36"x84" Wood

#104, 72"x84" Wood

#105, 72"x84" Wood

#106, 80"x84" Wood

would return a summary as follows

3 ea 36" x 84" Wood

2 ea 72" x 84" Wood

1 ea 80" x 84" Wood

There are endless possibilities of differences.

any thoughts?

Question isn't specific enough...

Are you planning on basing your whole solution on this one table, or are these subgrouped in some way, and if so do you only want to display these summaries for each subgrouping. Further is this to be displayed on a standard layout or in a report?

Thre could be problems using the double-quote and single-quote characters here.

This is one table of many(app28) related by project number. (each record has a project number)

The summaried values would be for just related records.

Hi,

I have the same question. Is there a function that count the related records of a table?

GetRelatedRecordFrom (TableXYZ)?

Thank you

You can use a calculation of Count (Child::PrimaryKey), that is on the parent side to get a count of the related child records.

yes; but there are different types of "children"

I am looking for a way to

Parent A

1ea tommy

2ea pauline

5ea sam

Parent B

6ea Joe

2ea pauline

...etc; there are no constants for children either/

Troy.

I was posting to Nick's question. In your case, if your data is in the format that your first post stated, then I would first create another field that is just a stored calculation of Substitute (mesaurementfield; """; ""). This will get rid of the quote mark. Then create a selfjoin relationship keyed on that new field.

Then you can create a subsummary report grouped on that new field. You can use your original field with the quote in it for display purposes, and a calc using count() or a summary field to display how many there is of each.

What exactly is the problem with using a quote mark in a text field?

Nothing, at all. But just in case somebody misses a quote mark when entering the data, I just thought it was a better choice as a match field to get rid of it instead.

OK, but if you are recommending a sub-summarized report (a recommendation which I would join), why do we need a relationship at all?