I am wondering whether there's a practical way around problems implementing two features in a database I'm developing:

(1) My database has data with names like workshop, series, program, topic, etc., but some users might want to call these entities by different names, e.g., they might think of a workshop as a session. I'd like to allow them to set these program-defined names to names of their own choosing, but many buttons on my layout incorporate these names (sometimes they line up side-by-side along a row). Is there a way to get the width of buttons to expand or shrink dynamically according to the content? On the face of it, this would appear impossible, and the idea of using some large one-size-size-fits-all width would lead to very unattractive layouts. So I will likely keep all of the names as set by the program while allowing for substitution of user-defined names when, e.g., the program produces pdf printouts or sends emails out. But if there is an elegant way to incorporate the name changes into my layouts, I would be very interested to know.

(2) Some users might not use a certain type of data at all, and so I plan to create alternative layouts that do not incorporate them. But if there are n variables for which one wants to provide an option of including or not incorporating the variable, one must produce 2**n layouts. Again, it would seem that there is no elegant solution, but if anyone has any tricks for avoiding rapidly proliferating layouts, please do let me know.

Thanks,

Jerry

You could use field validation and/or script triggers or even (dare I say) training to prevent button labels that are too long.

You could also use conditional formatting on the buttons so that if Length(label) > 20 for example, the font size is smaller. Still won't look ideal, but might help.

For hiding/showing objects, you could try hidden tabs. Set the tab and line width to 0.

Thanks.

For hiding/showing objects, you could try hidden tabs. Set the tab and line width to 0.

Sorry, where does one set "tab" to zero?

In the tab control setup dialog, set the tab width to "fixed width of:" and then enter 0 pixels.

Also, the justification has to not be "full."

And, be sure the tab object doesn't have embossed or other effects.

The idea is that you give each tab an object name and then you navigate to the desired tab using scripts. The user only sees the tab they're on.

In the tab control setup dialog, set the tab width to "fixed width of:" and then enter 0 pixels.

Also, the justification has to not be "full."

And, be sure the tab object doesn't have embossed or other effects.

The idea is that you give each tab an object name and then you navigate to the desired tab using scripts. The user only sees the tab they're on.

I see. That's a nice trick. But one must still put together 2**n very similar tabs. I guess I am hoping for some element of flexibility in designing layouts that can't exist within the current conceptual framework, because, for one thing, layouts would no longer be wysiwig.