data threshold on reports?

My client closed a large amount of jobs in November and cannot generate reports. The error is '#Record_band is too big'.

They are able to use the same report but for a different time period. For example, reports from Jan thru July work.

Is there a setting we can change that will accommodate a larger dataset? 

Thanks!

Tim Albertson
Great Divide IT Consulting LLC
2995 Skyline Blvd.
Suite # 208
Reno, NV 89509
tim@greatdivideit.com
775-229-4415 (direct)
775-636-5047 (mobile)
775-229-4398 (fax)
www.greatdivideit.com

"too big" refers to the actual size of the record band within the report spec, not the number of records associated with it

the same physical report file (rsl) with a code-generated and/or user-generated date range? shouldn't matter

two different saved versions of the same report? one file is damaged, the other is not.. kinda like the report is too big for an 8.5 x 11 page, but within the report design, not the output from the report.. a parameter is out of range

Steven Green
Senior Software Engineer
Paradox Support Specialist DOS/WIN

I can't save the design with a parameter out of range, that's why I suggest damaged file

Steven Green
Senior Software Engineer
Paradox Support Specialist DOS/WIN

So it's possible that a parameter is out of range? Where would we look? 

if it's a damaged report spec file, you can't look.. in theory, you shouldn't be able to open it.. never actually had that happen

if it's damaged, and you can replace it, and everything seems ok, you're fine.. if not, this might be much more complicated.. do you know the name of the file? the extension is .rsl

Steven Green
Senior Software Engineer
Paradox Support Specialist DOS/WIN

I just reviewed with the end user and observed the following:

1. it's a custom report (.rsl) which returns the following error "#Record_Band is too big to fit in report" if the Query (.Qbe) date range is >=01/01/2018, <=01/01/2019
2. When we change the date range to >=01/01/2018, <=07/01/2019 it opens without issue.

The only other new information is that the customer closed a lot of jobs in November. They close jobs in 2 tables (jobs.db, invinfo.db). It won't generate in the reports unless it's closed in both db's. 

This is the first time I have watched this process. A lot of human intervention. High margin for error. 

> A lot of human intervention. High margin for error. 

yes.. welcome to the wonderful world of self-made apps.. I've been cleaning up behind folks for almost 30 years (sigh)

when different query parameters on the same table sometimes work / sometimes fail, it usually just means the indexes for that table are hosed.. only a temporary show-stopper, once you know how to deal with it

Alison said you called last night, I'll try to call you back this afternoon

Steven Green
Senior Software Engineer
Paradox Support Specialist DOS/WIN