By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
434,930 Members | 1,383 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 434,930 IT Pros & Developers. It's quick & easy.

Large Report - "too many fields defined" issue

P: 16
I have compiled data from 13 tables, one for each month of the year that hold 45 fields each, and another for employee information, that holds 16 fields. The database is intended to record hours and special pay withholdings.

I split up the report into First Half and Second Half, as the paper version we use currently does.

My report First Half let me create control boxes for each field I wanted to include, however, when I try printing or previewing, the "too many fields defined" error shows up. Is the limit only 255 for a report?
Dec 27 '06 #1
Share this Question
Share on Google+
3 Replies


P: 16
Maybe I need to give you all more information?

Within each Month's table, I have data to cover up to 3 biweekly pay periods each month. There will not always be 3 pay periods in a month, in fact it's quite rare, however, I know of no way to enable myself to eliminate the third pay period when it goes unneeded other than just to make the control invisible, which leaves my field count on the report for the full year at 286.

The need for the third pay period depends on what year it is, and where we are in a 28-year cycle of pay dates. For instance, in 2006, the third pay period was in December and July. in 07, it will be September and December, 08 May and November... and so forth.

I have tried an alternate database setup that was based upon each pay period individually, not each month... and I get stuck on all the math involved.

Any advice at all would be graciously received.
Dec 28 '06 #2

NeoPa
Expert Mod 15k+
P: 31,492
It may not be easy but trying to use a database in a way that it isn't designed to work (storing similar data in multiple tables) will (has already) lead you into trouble. Months should be stored together in one table but with data in each record that determines which month it pertains to.
This may well be a side issue if your report exceeds the control limit. There's no easy way to handle that. I don't see the requirement of your report layout changing just because the data is or isn't stored correctly. You will probably have to be more 'creative' in finding a solution to this problem.
I'm sorry this isn't more helpful.
Dec 30 '06 #3

MMcCarthy
Expert Mod 10K+
P: 14,534
I have compiled data from 13 tables, one for each month of the year that hold 45 fields each, and another for employee information, that holds 16 fields. The database is intended to record hours and special pay withholdings.

I split up the report into First Half and Second Half, as the paper version we use currently does.

My report First Half let me create control boxes for each field I wanted to include, however, when I try printing or previewing, the "too many fields defined" error shows up. Is the limit only 255 for a report?
You could try using a subreport for the second half

Mary
Jan 1 '07 #4

Post your reply

Sign in to post your reply or Sign up for a free account.