J
James Hamersly via AccessMonster.com
I am relatively new to Access and am having a subreport problem that I
can't seem to get a handle on. When I open the "main" report, the query
indicator moves from left to right and says Formatting Page, press Ctrl-
Break. The hourglass stays on for a long time and I eventually have to
press Ctrl-Break to discontinue the process.
The "main" report has three subreports imbedded in the report body and the
first subreport is the one that's creating these problems. If I delete it,
the "main" report runs fine. I can run the subreport by itself and it runs
quickly and completely. The subreport returns about a million matching
records, but does so pretty quickly. The table bring reported on is linked
to a SQL Server database with index built over the matching columns.
As stated earlier, when run by itself the subreport runs fine. I have
written a query that links the data in the "main" report to the subreport
and displays the query data. There are pound sign characters(#) in the
data, but the rest of the data looks fine.
Does anyone have any clues as to what may be going on? I suspect the # in
the data is getting confused as a date parameter or something and is
getting lost. Is this reasonable? If so, is there a kind of REPLACE
function like SQL offers to convert # to blank?
Thank you, in advance, for any tips or help you may be able to provide.
James Hamersly
can't seem to get a handle on. When I open the "main" report, the query
indicator moves from left to right and says Formatting Page, press Ctrl-
Break. The hourglass stays on for a long time and I eventually have to
press Ctrl-Break to discontinue the process.
The "main" report has three subreports imbedded in the report body and the
first subreport is the one that's creating these problems. If I delete it,
the "main" report runs fine. I can run the subreport by itself and it runs
quickly and completely. The subreport returns about a million matching
records, but does so pretty quickly. The table bring reported on is linked
to a SQL Server database with index built over the matching columns.
As stated earlier, when run by itself the subreport runs fine. I have
written a query that links the data in the "main" report to the subreport
and displays the query data. There are pound sign characters(#) in the
data, but the rest of the data looks fine.
Does anyone have any clues as to what may be going on? I suspect the # in
the data is getting confused as a date parameter or something and is
getting lost. Is this reasonable? If so, is there a kind of REPLACE
function like SQL offers to convert # to blank?
Thank you, in advance, for any tips or help you may be able to provide.
James Hamersly