Bhawawawa - Too many Fields Defined

[Becca]

Hi

I have just finished formatting a tremendous report in my DB to circumvent the old clunky one used in Excel. Unfortunately, it now tells me...

! Too many fields defined!

Apparently according to the little paper clip, 255 is the maximum in my report.. which sux, pardon the french. Any ideas about the way to get around it. The group footer sum fields are the ones who pushed me over the edge, as they are made up of 120 fields apiece. I need this level of detail however, and I would hate to cull it too much.

ANyone know of a nifty way to get around this?

Thanks

 

[RichMorrison]

If someond handed me a report with 255 fields, I would say that report really really sux.

IMO, you should redesign the report or split it into two or more.

RichM

 

[vortex]

TransferSpreadsheet - "too many fields defined" error

I don't know if this will help, but I had the same problem trying to export an access query into an excel spreadsheet using TransferSpreadsheet. I was getting the same message "Too many fields defined", but I was only using about 12 fields. Access Help said to compact the database, which I did, and the problem still occurred. Finally I found out the real problem was my query name had spaces and hyphens in it. Once I removed the spaces and the hyphens from the query name (in access) then the problem was solved.
Hope that this helps somebody out there because it was driving me crazy.
Thanks.

 

[Pat Hartman]

Thanks for sharing vortex.

Many strange and not so wonderful problems are caused by defining objects with embedded spaces and/or special characters in their names.

Rid all of your names of embedded spaces and special characters and make sure that you are not using function names such as Date() and Time(), property names such as Name or any other reserved words.