On Wed, 28 May 2008 07:20:01 -0700, Amanda < XXXX@XXXXX.COM >
I can assure you of one thing: designing your table structures to fit your
form will pretty much guarantee a flawed design.
Designing a relational database is a bit like building a house. The Tables and
their relationships are the foundation; Forms are the doorframes and windows.
You build the foundation FIRST. Data is stored in tables, and only in tables;
a Form is simply a tool to display and edit that data.
If you're using the word "form" in the common sense of a printed document of
fixed format, then I think you really want a Report. Access Forms are for
onscreen interaction with the data; Reports are for printing.
Design your tables based on the logical relationships between the Entities
(real-life people, things, or events) of importance to your application; then
design the forms and reports to fit the logical structure of the data - not
For some tutorials see
Jeff Conrad's resources page:
The Access Web resources page:
A free tutorial written by Crystal (MS Access MVP):
MVP Allen Browne's tutorials:
John W. Vinson [MVP]