layout, summary questions

[bwork]

this is a post from the portal thread as well.

I am redoing the database, making one table that has all the discrepancies. There are 13 different discrepancies that can be chosen. Dependant on which one is chosen, there can be different variables. I believe I can accomplish this by making different layouts wtih the fields that I want. I don't know how to generate a summary report that would list all discrepancies for a certain date and then list the appropriate sub fields. The problem I see is that since it is all one table, I can't specify out which fields I want at a certain time. I hope someone can help with this and give me some insight. Thanks in advance

[Ender]

Can you give examples of the "different variables"?

[bwork]

QNS (lab, spec #, amount)

Missing (lab, reason, TAT affected, comments)

Empty (lab, originating dept)

etc. Each one has different pieces of information that is required.

Thanks

[Ender]

If the sub-summary is in a layout based on the Discrepancy table, then the sub-summary should break by Date and Discrepancy Type. These other fields will go in the Body part.

Now, because you've got different fields you want to display, depending on the discrepancy type, this makes it a little more work. If possible, different discrepancy types should re-use the same fields (Comments in one would be the same as Notes in another.) It's not clear from your example how much of this will be possible.

One way to deal with these different fields is to simply list them all. Those that aren't needed would remain empty for some discrepancy types. If you think you won't have space for this, then you could consider one of these methods:

1. Layering mutually exclusive fields on top of one another in the Body part.

2. Using calcs to display each column, based on the Discrepancy Type. The "Lab" might be the first column which is common to all types, then the second column would be calculated:

case(Discrepancy Type = "QNS"; spec #;

Discrepancy Type = "Missing"; Reason;

Discrepancy Type = "Empty"; Originating Dept)

The labels could be calculated in a similar manner, and displayed in the Sub-Summary by Discrepancy Type part.

[RalphL]

Start out making your list list layout body (record) 13 lines long. In the first line place the fields for QNS, in the second place the fields for Missing, in the third line place the fields for Empty, etc. Make a global text field for each discrepancies that will serve as a title strip for each one, i.e., for QNS make it lab spec # amount.

Now move the second line on top of the first line, then the third line on top of them, etc, until ypu have only one line. Reduce the body to 1 line. Create a calculated text field = Case ( discrepancy = "QNS"; gTitle strip QNS; discrepancy = "Missing"; gTitle strip Missing; etc) Put this in a subsummarty part above the body.

[comment]

Perhaps 2 additional calc fields should be enough - see attached.

variableReport.fp7.zip

[bwork]

thank you everybody. The latest seems the easiest. i am intrigued about the others and want to learn those options as well. I will continue to play with this. Again, thank you.

Brandon

[bwork]

Followup question.

In the variable report that you sent me. You had a radio button field that didn't display the radio buttons. I was wondering how this was done.

[comment]

I am not sure I understand your question.

A field is a field, it is not DEFINED as a 'radio button field'.

When you place a field on a layout, you have the option to FORMAT it as a radio button set. That means:

a) the user can only input values by selecting from a pre-defined value list;

: if the field contains a value that is not in the associated list - the field's content will not be diplayed.

The same field on another (or even the same) layout, can be formatted in another way, and the entry options/display will change accordingly. But the actual content of the field is always the same.

[bwork]

Maybe I am not explaining what I am trying to say. In the variable report example database that you uploaded you placed a field on the database that was a radio button set using values from the list Type. Instead of having Radio Buttons attached to the field as usual, you had created buttons that performed a script. I was wondering how you created a Radio Button Set, that didn't display the buttons. You also have the same field name elsewhere formatted as a Popup List.

[comment]

The field (or rather the instance of the field that is formatted as radio buttons) does display the buttons - but the border width is set to 0, so only the inner portion of the selected button is seen.

The field is overlayed by two circle-shaped buttons, with script attached. The script toggles the buttons AND goes to the appropriate layout. The field itself is formatted to NOT allow entry - so basically it is only there for display.

Go to layout mode and pull it apart to see for yourself. Turn on View/Show/Buttons, and move the field aside to see the overlay buttons.

[bwork]

very cool, I see it now. That's very interesting.

[bwork]

I have tried your method and I am running into a conflict. I can get it to work, however, i have to click on one of the buttons twice to make it work, any suggestions.

Brandon

[comment]

Try being more specific?