Steve

If you have one field for each month, you will have ... a spreadsheet!

If you are unfamiliar with the terms "normalization" and "relational
database design", plan to brush up on these BEFORE you design your table
structure. In fact, plan to brush up anyway ... you will need to evaluate
the responses you get here in light of their suitability to your specific
situation, considering relational database design.

Good luck!

Regards

Jeff Boyce
Microsoft Access MVP

--
Disclaimer: This author may have received products and services mentioned
in this post. Mention and/or description of a product or service herein
does not constitute endorsement thereof.

Any code or psuedocode included in this post is offered "as is", with no
guarantee as to suitability.

You can thank the FTC of the USA for making this disclaimer
possible/necessary.

"Steve D" wrote in message
...
Good Afternoon,
I have a very basic question regarding the organization of my table. I
will have monthly data that will be entered and it will be for various
years.
Is it better to use one field called month and do a crosstab query or
should
I have 12 fields (one for each month)? My thought is that it is cleaner if
each month has its own record but then I will have 12 times the number of
records. Thoughts? Best Practices?
--
Thank You,
Steve