I am creating some simple reports for a client but as usual I have it a snag.

Part of the questionnaire has a section for the callers behaviour. This is a checkbox field and it can have multiple checks. So the caller could be calm, or calm/frieghtened along with various other choices.

The report is a subSum on Behaviour but how can I break a multi checked field into individual counts. Although it is one record I need a count for each behaviour check.

I am thinking that it will have to be some kind of a portal or even a CDML solution but thought I should check with the FM-borg, to see if I can keep it a report solution.

Subsummary reports can't really work or make sense unless the field you're summarizing on has only one value per record.

You are encountering a common problem in using checkboxes: it often turns out that a better design choice would have been to make separate fields for each of the checkbox values. This makes it easy to total them. So, you can either Find the records for one value, then assign them all to a new field, Find the next group and repeat etc. Or... if you're attached to your checkbox field as is, you can make a calculated field for each value:

CalmCalc = If (PatternCount(Behaviour, "calm"), 1, "")

You need a separate calculated field for each checkbox value.

Once that's done, just use summary fields, total of CalmCalc, total of FearCalc, etc.

You want to have a total for each behaviour being checked ?

Use global fields set to the values of your Value list (g_calm = "calm", and g_calm/frieghtened = "g_calm/frieghtened"), then you could use the self-relationships g_calm::behaviour and g_calm/frieghtened::behaviour,...

Then your calcs would use these relationship for countCalm = count(selfjoinoncalm:behaviour)...

These counts could take place in the report.

This doesn't allow you to break each "behaviour" checked, as you would need one record per value checked to get a sub-summary.

I think you would need a separate file (sort of line items). Depending on the numbers of datas entered, you would :

- use checkbox in portals

- script an export records to that file

Your sub-summary report would use this line item file.

Hope that make sense...

I think I have found a solution... If i create a repeating field calculation that breaks each checked item into a repeating field, then I can have a report file that will import and burst all repeating field into a separate record. (i am very excited). Now here come the challenge. I have to think of a clean calc that will separate each checked item. Here I go... so if anyone has some suggestions please post.

No need for repeating fields. You do need to control the user's navigation.

The check boxes enter into a global field. Upon moving to the next question, the user runs a script which parses the selected items and creates a related record for each one.

I have attached a file that parses a field. It's not quite what you need because it uses the parsed values to create find requests but the modifications to change it a minimal.

parse.fp5.zip