>Thank you again Mr. Vinson...I have a few more questons
>I have been studying relational database design for
>access 2002 and its sinking in but I only have one table
>and a bunch of fields I get no help from the table or
>performance analyzer..I know i need to create a primary
>key and break some of these fields into smaller
>tables ...I am not sure how to....am I allowed to email
>you my existing table that i have created and also a copy
>of the 3 forms i have that i am creating from .... there
>are alot of field on these 3 forms....
>Hope to hear from you soon thanks again
I'm sorry - I'm a self-employed consultant, volunteering (what's
become a bit too much of) my time on these newsgroups. I'd only be
able to whip your database into shape on a for-fee consulting basis.
Perhaps what you could do is to start a new thread in this newsgroup;
describe the nature of the data you are trying to manage and perhaps
the list of fields that you currently have (with explanations if the
fieldnames are not self-explanatory). Just to reemphasize: starting
your design with Forms IS A BAD APPROACH, and will pretty much
guarantee a non-normalized design! Design your table logic *first*,
and then design forms to mediate between that logical structure and
the visual needs of your users.
In a nutshell, each Table should contain the information for one type
of Entity - real-life person, thing, or event. If your current single
table contains (say) information about widgets, and experiments on
widgets, and results of those experiments you might have three tables:
widgets, experiments, and results.