basenine 4/23/2013 4:54:53 AM
Maybe a bad example…😉 It doesn't necessarily have to be a Lookup.. With Lookups, I've gotten into the habit of flagging it as a lookup by naming it New Lookup - xyz… I find it neater and easier to find.
Another example where this comes into play is when there is a Postal Address, Postal City, Postal State, Postal Post Code and a Site Address, Site City, Site State, Site Post Code. You create 2 Formulas to combine the fields as one:
[Full Site Address] (as you can't have [Site Address] again) and [Full Postal Address]. [Full Site Address] looks like this:
[Site Address] & "\n" & List(", ",[Site City], [Site State], [Site Pcode])
In the Form, you Edit the Site Address, Site City, Site State, Site Post Code and View the [Full Site Address]…But you want to View it on the Form labelled as [Site Address]… So you go to the Form Layout and type Site Address in the Alternative Label
Sometimes you might even want two formula Addresses…the second one being [Full Site Address - Linear]:
List(", ",[Site Address], [Site City], [Site State], [Site Pcode])
You still call this Site Address when Viewing the Form and it might be the one you want to use for one of the Records View.
Forms are Dynamic based on Role(), User() etc and [Site Address] may need to be shown in any number of formats. Views, too, can be Role() or User() Dependant…you get the idea.
I'm sure there are other examples. I'll have a think and a look through some of my applications where I know it would be handy.
If it was a simple as just changing the Column Name, why is there an alternative name… Just Sayin'