S
Steve
Hi,
I have a large report running on my Access 2000 database that calls a stored
procedure from our SQL Server. After making some recent amendments, I've
started to get a 'Too many fields defined' error when I try to run it.
There are only around 90 fields that are generated by the stored procedure &
in total just 226 text boxes / labels on the report (although most of these
contain IIf statements) so I'm within the 255 maximum. I've tried compacting
the database and copying the fields to a new report but don't seem to be
able to fix things. I'm starting to think that I may be around the '754
controls & sections' that I can add 'over the lifetime of the report' (some
of the textboxes have numbers in the 700's). Any ideas as to how I can
tackle this ? I thought that copying the fields to a new report was meant to
solve the majority of these problems - has anyone any experience with this ?
Thanks
Steve
I have a large report running on my Access 2000 database that calls a stored
procedure from our SQL Server. After making some recent amendments, I've
started to get a 'Too many fields defined' error when I try to run it.
There are only around 90 fields that are generated by the stored procedure &
in total just 226 text boxes / labels on the report (although most of these
contain IIf statements) so I'm within the 255 maximum. I've tried compacting
the database and copying the fields to a new report but don't seem to be
able to fix things. I'm starting to think that I may be around the '754
controls & sections' that I can add 'over the lifetime of the report' (some
of the textboxes have numbers in the 700's). Any ideas as to how I can
tackle this ? I thought that copying the fields to a new report was meant to
solve the majority of these problems - has anyone any experience with this ?
Thanks
Steve