Hi,

I recently copied a technique for incorporating GUI elements from a database I inherited that seemed cool but now I'm not so sure.

The Technique: in a table called Preferences there is a container field with repeating values. Each repetition contains a GUI element (e.g. an arrow, a check mark, a delete symbol etc.) The Preferences table is then related to another table via a 'X' (Certesian) join using a gConstant field in the Preferences table and using the ID in the other table.

To use the element on a layout I drag on the container field, choose the repetition number and, voilà, the GUI element is on my layout.

This seemed like a cool, tidy way to work with GUI elements.

The Problem: As my database has grown so has the number of Layouts showing data from different tables. And I'm in a situation now where I have to keep adding Table Occurrences of the Preferences table to each other TO just to get one or two graphics. So my relationship graph is very "busy" with TO's of the Preferences table everywhere.

Maybe I'm just being overly tidy, but this irritates me and makes me suspect there is a better way of doing this. Any ideas?

Thanks,

Pat

Well, globals (fields, calculations and variables) are accessible from anywhere, without a relationship.

comment,

it's a small tip, it's really obvious - duh! - and you've just done me a big favor... many thanks!

p