Hello, I am currently developing a database using fm pro 13 and i need a calculation field that writes a paragraph using related record values

 

In my case: I have a table called event related to a table called transfusion in a one:many relationship.

I have a portal on the event layout that has the field

 

transfusion::Blood product, transfusion::Dose, etc

 

The blood product can be RBCs, platelets, albumin and/or IVIG

 

So each record in transfusion will have a blood product and other information.

 

I have a layout that prints a form for the medical daycare unit. I want this form to display the information from transfusion in a coherent fashion.

 

For example, if transfusion::Blood product = "RBC" then "Please give the following blood product: RBC" and dose

and if another record related to the event contains platelets then the platelet info will show as well.

 

I was able to perform the function using a checkbox or a repeating field but I find using a related table makes things look much better and organized. 

 

Can anyone help me with this. If you need more info please let me know

 

thank you

One approach:

 

base your report on a Transfusions list layout; this would also allow you to easily group and summarize, and you could use the same layout to report by date range, Event record(s) or other criteria.

 

Another one:

 

pull in a list into the Events table.

 

• create a calculation field in the Transfusion table that calculates the complete string you want to have displayed per transfusion record, based on the values for fields like bloodProduct etc.

• create your list from the Events context by using List() with your calculated field, e.g. List ( Transfusions::cCompleteTransfusionMessage ).

 

Note for this second approach that if you only need this list when reporting, you wouldn't necessarily have to create a dedicated calculation field in Events; pull in the list in the course of your report script and place it into a global field or a merge object/variable (or whatever fits the way you've set up your report).

One approach:

 

base your report on a Transfusions list layout; this would also allow you to easily group and summarize, and you could use the same layout to report by date range, Event record(s) or other criteria.

 

Another one:

 

pull in a list into the Events table.

 

• create a calculation field in the Transfusion table that calculates the complete string you want to have displayed per transfusion record, based on the values for fields like bloodProduct etc.

• create your list from the Events context by using List() with your calculated field, e.g. List ( Transfusions::cCompleteTransfusionMessage ).

 

Note for this second approach that if you only need this list when reporting, you wouldn't necessarily have to create a dedicated calculation field in Events; pull in the list in the course of your report script and place it into a global field or a merge object/variable (or whatever fits the way you've set up your report).

This is perfect!! thank you very much!