Creation of a table with 300 fields. How?

[Obatistor]

Hello all! How are you?

I would like to create a table with 300 fields and it is not
possible in a simple way because access doesn't let you create a
database table bigger than 255 fields. Could I do that with a simple
QUERY? Or, if not, how could I do that?

Any help will be appreciated. Thanks for all,
Oscar

[Rick Brandt]

"Obatistor" <ob*******@hotmail.com> wrote in message
news:ec**************************@posting.google.c om...

Hello all! How are you?

I would like to create a table with 300 fields and it is not
possible in a simple way because access doesn't let you create a
database table bigger than 255 fields. Could I do that with a simple
QUERY? Or, if not, how could I do that?

You can't. Queries have the same limit and "needing" to exceed that almost
always means your table structure is not properly designed. Other than
using a properly normalized table schema, the only other work-around is to
spread the fields over multiple tables with 1-to-1 relationships. You
still won't be able to combine them in a query for easy use in forms and
reports though.

--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com

[Fletcher Arnold]

"Obatistor" <ob*******@hotmail.com> wrote in message
news:ec**************************@posting.google.c om...

Hello all! How are you?

I would like to create a table with 300 fields and it is not
possible in a simple way because access doesn't let you create a
database table bigger than 255 fields. Could I do that with a simple
QUERY? Or, if not, how could I do that?

Any help will be appreciated. Thanks for all,
Oscar

In a well-designed database there would never be any need to even approach
the limit of 255 fields per table. Normally when people say they need more,
they actually need a re-think of the table design.
E.g.
Twenty people are going on a diet program for a year and their weights are
recorded daily to monitor the progress. Some people might want to create a
table with fields FirstName, LastName, Dob, Weight1, Weight2, Weight3 ...
Weight356 so that the yearly mesurements could all be stored in one table.
A much better way to do this would be to have 2 tables:
tblPersons: PsnID, PsnFirstName, PsnLastName, PsnDob, etc
tblWeights: WgtID, WgtPsnID, WgtDate, WgtWeight

This has the added advantage that I can continue the trial over as many
years as I want without needing to change my table structure - so all my
forms, reports, code etc still work. If I had a fixed number of rows I
could not do this.

On this basis, can you see how to re-structure your data?

Fletcher