Query too large

[Guest]

I am trying to create a form using more than one table so I tried to first
create a query consisting of the tables. My hope was to use the query to
design my form. I am getting a query error message: "Too many fields
defined". Please offer suggestions. Thanks in advance.

 

[Jeff Boyce]

Derek

One suggestion might be that you have too many fields in your query. You
didn't mention how many you have...

Good luck

Jeff Boyce
<Access MVP>

 

[Immanuel Sibero]

Derek,

How many fields? Are your tables normalized?

Immanuel Sibero

 

[John Vinson]

I am trying to create a form using more than one table so I tried to first
create a query consisting of the tables. My hope was to use the query to
design my form. I am getting a query error message: "Too many fields
defined". Please offer suggestions. Thanks in advance.

You're limited to an (absurdly enormous) 255 fields - are you pushing
or exceeding this limit!? What's the nature of your tables?

John W. Vinson[MVP]

 

[Joseph Meehan]

I am trying to create a form using more than one table so I tried to
first create a query consisting of the tables. My hope was to use the
query to design my form. I am getting a query error message: "Too
many fields defined". Please offer suggestions. Thanks in advance.

That would tend to indicate you have 256 or more fields. That
generally means you have a bad table design.

Is it possible that you have a group of tables with like data, say one
table for January and one for February etc.?

 

[Guest]

I am new to Access and have only taken one class so far (and work schedule
does not allow for another right now)... the rest I have been trying to
figure out myself - so I'm sure some things I do may be redundant as you
suggest. Can you direct me to an area online that would instruct me how to
remove redundancy, but at the same time collect similar information as unique
data. For example, several of my fields collect lab results for the same
test but on different days, so they need to be entered as such. Again,
thanks.

 

[John Vinson]

For example, several of my fields collect lab results for the same
test but on different days, so they need to be entered as such.

"Fields are expensive, records are cheap" is a good tagline to
remember for cases like this.

If you have a one (test) to many (results for that test) relationship,
the proper way to do it is to use TWO TABLES: one describing the test
(without any results, but with a unique TestID), related one-to-many
to a table with fields for the TestID, the TestDate, and the result on
that day. This table grows "down" not across - you add a new RECORD
for each day's testing, not a new field.

This is a general principle that applies all over Access.

John W. Vinson[MVP]

 

[Guest]

John, thanks you VERY much. I think this is the solution I was looking for.