M
Mishanya
I have report consisting of 20 subreports:
1) 13 single subreports of wich
2) 7 have charts (pies) and supporting information as sub-subreports.
All the sub- and sub-subreports as well as the charts are based on queries,
3 have DLast and DFirst domain aggregate functions, 2 have subqueries, 1 is
based on Union query. No other VB.
The charts were initially built in forms then copy-pasted to reports and
linked by ClientID parameter in WHERE clause to the main report.
The report runs instantly and smoothly, with only here-and-there delays
while formatting pagebreaks.
After splitting the DB into BE and FE, while both the files are still in one
directory in my computer, runnung the report causes 3048 error, ending up
with 6 first non-chart subreports and blank pages for the rest and at times
even crashes Access alltogether.
Every subreport including those with charts still run succesfullly while
executed alone.
The whole report, executed when all other application' forms are closed,
complete the run with fewer 3048 errors and shows all but the charts reports.
By elimination and counting the number of the error boxes appearances, I've
definetly concluded that the error is caused by the charts.
Tried to split the main report in two (10 subreports each) and to run
separatly - succesfully, although, I can't be sure it'll still be so when BE
and FE separated to different computers. Anyway, splitting the main report is
not convinient, as all the data in it is coherent and needed combined.
What can I do to help Access run the main report in splitted DB? Why it does
not now - I don't have some 250-tables-300-forms-400 reports with tens of
thousands of records. Just 25 queries with 7 charts dealing with 150-200
records nested in one. How can splitting have so drastical effect even though
both the files are still in the same hard disc?
1) 13 single subreports of wich
2) 7 have charts (pies) and supporting information as sub-subreports.
All the sub- and sub-subreports as well as the charts are based on queries,
3 have DLast and DFirst domain aggregate functions, 2 have subqueries, 1 is
based on Union query. No other VB.
The charts were initially built in forms then copy-pasted to reports and
linked by ClientID parameter in WHERE clause to the main report.
The report runs instantly and smoothly, with only here-and-there delays
while formatting pagebreaks.
After splitting the DB into BE and FE, while both the files are still in one
directory in my computer, runnung the report causes 3048 error, ending up
with 6 first non-chart subreports and blank pages for the rest and at times
even crashes Access alltogether.
Every subreport including those with charts still run succesfullly while
executed alone.
The whole report, executed when all other application' forms are closed,
complete the run with fewer 3048 errors and shows all but the charts reports.
By elimination and counting the number of the error boxes appearances, I've
definetly concluded that the error is caused by the charts.
Tried to split the main report in two (10 subreports each) and to run
separatly - succesfully, although, I can't be sure it'll still be so when BE
and FE separated to different computers. Anyway, splitting the main report is
not convinient, as all the data in it is coherent and needed combined.
What can I do to help Access run the main report in splitted DB? Why it does
not now - I don't have some 250-tables-300-forms-400 reports with tens of
thousands of records. Just 25 queries with 7 charts dealing with 150-200
records nested in one. How can splitting have so drastical effect even though
both the files are still in the same hard disc?