Too Many Fields Defined?????

[Zach]

When I got to open form A from table A, I recieve an error message saying
"Too Many Fields Defined," and the form will not open. But if I open the form
in design veiw by clicking the design icon it comes up in design and then I
click the view button again and it comes up as the form with the fields
filled in. Can anyone help?

 

[John W. Vinson]

When I got to open form A from table A

I am not sure what you're doing here. You can't "open a form from a table".

What's the table? What's the Recordsource for the form? How are you opening
it?

John W. Vinson [MVP]

 

[Zach]

I have a form that I made in table A. When I open the form, I recieve a
message saying "too many fields defined." But i can open the form in design
view and then switch it to the normal view, but I can't open it without going
into design view.

 

[John W. Vinson]

I have a form that I made in table A.

Again:

This sentence makes no sense to me.

A Table is a data storage object in the Tables collection in Access.

A Form is a *totally different kind* of object.

A form cannot be "in" a table.

A Form can use a Table as a Recordsource, but that's not "in" the table - any
more than the windowframe across from my office is "in" the Owyhee Mountains.

When I open the form, I recieve a
message saying "too many fields defined." But i can open the form in design
view and then switch it to the normal view, but I can't open it without going
into design view.

Please, again... answer the questions in my previous message.

John W. Vinson [MVP]

 

[Pete D.]

http://www.databasedev.co.uk/too_many_fields_defined.html

 

[David W. Fenton]

http://www.databasedev.co.uk/too_many_fields_defined.html

That article makes no sense at all. Changing the properties of a
field in a table does *not* increment the field counter.

And this error is most often encountered in *forms* where you've
deleted and pasted a bunch of controls, such that you quickly reach
the 700-odd limit on controls. Compacting does *not* reset the
counter for forms -- the only way to reset it is to start a new
form, or to export/import using the undocumented
Application.SaveAsText/LoadFromtext commands.

I've been programming in Access as part of my full-time job since
1996 and have not even once encountered this error, so I would think
that it indicates a design error somewhere along the line.

 

[Pete D.]

Well I ran into it when importing and making many changes to the fields such
as adding and deleting especially using old flat files with way to many
fields. In the end all I could do was to get rid of it was recreate the
table and append the records to it. It occurs with queries, table changes.

http://support.microsoft.com/kb/198504/en-us

 

[John W. Vinson]

Well I ran into it when importing and making many changes to the fields such
as adding and deleting especially using old flat files with way to many
fields. In the end all I could do was to get rid of it was recreate the
table and append the records to it. It occurs with queries, table changes.

http://support.microsoft.com/kb/198504/en-us

IME these are both problems, in different circumstances. David's quite right
that there is a limit on the number of controls (not fields) on a form;
there's an independent limit on the number of fields in a table or query.

The latter can be cured by compacting; the former cannot. The form must be
rebuilt (though you can copy and paste controls from the old form).

John W. Vinson [MVP]

 

[Pete D.]

It is such a good thing that you have guys like me that can really screw up
access and find those errors you experts would never find. Pete :~)

 

[David W. Fenton]

Well I ran into it when importing and making many changes to the
fields such as adding and deleting especially using old flat files
with way to many fields. In the end all I could do was to get rid
of it was recreate the table and append the records to it. It
occurs with queries, table changes.

http://support.microsoft.com/kb/198504/en-us

OK. I never would have encountered this because I wouldn't think of
defining a table with more than, say 50 fields. And I compact often
during design stages, so I'd likely not run onto it at all, even
when I had something close to 255 fields.

 

[Pete D.]

That's okay, I won't tell you how much of your code/hints have made me look
good. Thanks, Duff

 

[Zach]

alright I created a form that usind table A as a record source. when i go to
open the form i receive an error message saying that i have too many fields
defind how can i fix this

It is such a good thing that you have guys like me that can really screw up
access and find those errors you experts would never find. Pete :~)