too many fields for report but not for query

  • Thread starter Thread starter MikeHatton
  • Start date Start date
M

MikeHatton

I have a query which contains approximatly 200 fields, the data come
from two tables (1 to 1 relationship) each table contains 200 + fields
The query works fine, However when I use the query as the source for
report I get 'too many fields' error...
I know the limit is 255 fields in either a table or a query and bot
tables and the final query have less fields than this..
I cannot reduce the amount of data that is required, and I do no
realistically want to use dlookups for each field on the report.
Is there a simple solution or a quick fix
 
Ok further information..I have realised that 5 of the output fields ar
drawn from about 20 other fields that are not included in the query.
meaning that the total fields comming out of the query is less than 20
but the number of fields required by the query exceeds 255.. it seem
that this is fine for a query on its own but not for a report that i
built on this query..

my first trial workaround/solution was to create a make table query an
base the report on that temporary table.. I considered this to be les
than adequate, so pushed on..

I discovered to my surprise that if I include a groupby on each fiel
the report is perfectly happy with the query...

I cannot see why this would be the case unless the report is using it
own query engine for simple queries, and by using groupby the report i
forced to use the 'normal'(Presumably Jet) query engine...

can anyone shed any light on this?

I am running Office97-SR2 on Win2k
(I also have Office XP Installed)

for the time being I am happy to leave the groupby in place as it is
tidy enough solution if a little excessive on processing... however
would still be interested in knowing why and whether there may be
fix...

Mike..
 
Back
Top