Thanks Dave...Here's the scenario:
I want to create a Parent field of "Site" and a Child field of "Building" so that when the "Site" is chosen an appropriate list of buildings at that site is available in the "Building" field.
This data isn't setup anywhere, nor does it need to be retrieved from other locations. Do I really need to setup a DB to make this work? It seems an over-complicated way of making the fields I want.
If so, that's fine - any basic instruction on it? The stuff available in help demonstrates more complicated use of the field.