Too Many Fields

MarcusAntonius

Registered User.
Local time
Today, 11:14
Joined
Jul 13, 2004
Messages
37
I'm trying to create a form from two tables but it errors out with: The wizard is unable to create your form or report because you chose too many fields; please try again with fewer fields.

However, I can't reduce the number of fields and it's not because I don't want to. Is there another way around this?
 
To make a form from 2 tables is best to use a query.

Michael
 
As in create a query and then create a form based on the query? That still gives me the same error.

It needs to be a form since it's for data entry and I don't want users trying to do it using the datasheet view.
 
Are you trying make a form from 2 tables?

If so, using a query is probably the best way to go.
It shouldn't give you an error.

If you want post your db and I'll take a look at it for you.

Michael
 
Are you trying make a form from 2 tables?

If so, using a query is probably the best way to go.
It shouldn't give you an error.

If you want post your db and I'll take a look at it for you.



Yes, from two tables.

Perhaps it's a bug of some sort in access whereby there's a limit on the number of fields that be used in a form. (I'm using access 2002/sp3)

Unfortunately I can't post the DB.
 
I think I'm having this same problem, except, when I create the form using the wizard, the form in form view is completely blank (only background is seen). The datasheet view is fine though.

When I use the wizard and select only a few fields from each of my 3 tables, it looks and works perfectly; however, when I add all fields, it goes blank. I'm having a hard time figuring it out as well.

Have you figured it out?
 
I think there's a limit to the number of fields you can have, so just try adding a few more each time and see where you get to.

Not sure why it goes blank though, I didn't experience that problem since it just wouldn't let me create the form due to the excessive number of fields.
 
I just encountered this problem. I have 25 columns.
It worked when I limited the number of columns for the report. Not sure. I guess its a bug in access. Has anyone else encountered this issue.?
 

Users who are viewing this thread

Back
Top Bottom