Relational Monkey

Thanks, I managed to mock up the basic idea, with 5 columns of data. What is the technique to prevent it breaking, with renames, etc? I think I need to do more research to maximize efficiency in the calculation. The more possible case fields I add, it's gonna let long.

Thank you. Your basic structure is doing what I'm thinking of. I'm going to see if I can refine it into something resembling my idea. Any advice on how to make the choices made in each menu feel sticky until changed would help a lot.

I'm trying to make a way to print a list of a variety of figures (say, 6 fields per line, left to right, in columns) that the user can choose before printing. So, if there are 20 possible fields to choose from, say, you can choose any 6 you want on the list (per line) instead of having to make too many print layouts for different purposes. Obviously, I'm just going for one "column" and can extrapolate the rest, with your help. As for the unstored part of it, it doesn't matter as much if it needs to recalculate on the fly, since I'm only planning on it being used in a print layout, but if there was another way to store the last configuration when the file is opened again (it will be on a hosted server) that would be even better. Thanks again!

Hi. I'm trying to figure out how to make a global menu selection (up in the header) and that selection populates a field with the contents of whichever field was selected in the menu — know what I mean? Sort of like this: Furthermore, I'd like to be able to possibly script this such that the result field in every record in list view gets altered simultaneously by the global selection. I'm unsure whether this is a script-able thing or something else, like a calc. I'm reasonably clever, but I probably need you to spell it out for me. Thanks for your guidance.