Nhmiller wrote:
Not automatically. But if you open the form in design view, all should
be(come) clear.
After another hour or so of wasted time, I finally found the icon Field List,
and then it took me 5 minutes to realize I have to click and drag the new field
into the design. I think Microsoft should fire whoever is in charge of their
Help menus -- this instruction is no where to be found. I'm lucky you have
taken the time to answer my questions. Much thanks again.
Should I have said "copy one control, paste it onto the same form, and
change the ControlSource property to the new field"?
To deal with fields not appearing automatically on a form, I went to
great length writing a wizard-like form maintainer. There is an
in-database solution for many of these problems as well:
I realized that a table definition basically is a set of records itself.
In most SQL databases there are system tables that show this
clearly--unfortunately Microsoft decided to include many features to the
design, which calls for a company standard. Not the Codasyl-standard
however. Rant, rant: the system tables in Access cannot be so easily
used. So, I created my own data dictionary tables:
Tables (containing the name of every table)
Columns (containing the name of every field for every table)
and I added Forms (for every form: its recordsource, and if that is a
query, the table it sits upon in the end) and FormControls (every
control in the form)
From these tables, I can create all forms anew, any time I like (which
is especially after I change the table structure). During design phase
this often saved me hours.
On my site (
http://www.heuveltop.nl/BasCB) you can find the Case project
under samples. It contains the basic setup (honestly, I need to review
it, because it was put on the site in 1999 or so, and since then my
insight and knowledge has changed) and maybe it tells you something more.