ChristianWhite
Programmer
A user can "dial up" a Crystal report, of perhaps twenty, from my ASP.
I'm having trouble with a report I'm trying to add to the selections.
The report runs fine in CR Developer.
I copied the report from an ASP application that ran it in IE without problem.
My application is also designed for viewing in IE, and runs the report fine with data selections that generate an instance of this report not exceeding about 15 pages.
My application has a problem, however: Each time I try, via the ASP, to select the report, IE reports it has encountered a problem and needs to close, showing the box offering to send an error report.
Message box:
IEXPLORER.EXE--Application Error
The instruction at "0x60024325" referenced memory at "0x0000000c". The memory
could not be "read".
I ran the report on a different workstation, got the same error. On a third workstation, I got an error on the same selection, but without the "send an error report?" box; instead, the Crystal viewer came up empty. I forgot to check IE version, but we're all on the same flash here.
Concluding the report's volume is too much would seem consistent with the error appearing only after the report exceeds about 15 pages. Also, I read on the Microsoft site that a message about referencing memory at 0x0000000c meant an attempt to access memory beyond the limits of a stack.
However, why is the other application able to run this report at any length?
Could my application be too bulky? Where could I find the evidence?
Better yet, how could I get this thing to WORK ?
Any input appreciated.
Christian
I use: Windows 2000; SQL Server; Crystal Reports 8.5; IE 6
More information about Windows stop messages (e.g., memory could not be read) at
I'm having trouble with a report I'm trying to add to the selections.
The report runs fine in CR Developer.
I copied the report from an ASP application that ran it in IE without problem.
My application is also designed for viewing in IE, and runs the report fine with data selections that generate an instance of this report not exceeding about 15 pages.
My application has a problem, however: Each time I try, via the ASP, to select the report, IE reports it has encountered a problem and needs to close, showing the box offering to send an error report.
Message box:
IEXPLORER.EXE--Application Error
The instruction at "0x60024325" referenced memory at "0x0000000c". The memory
could not be "read".
I ran the report on a different workstation, got the same error. On a third workstation, I got an error on the same selection, but without the "send an error report?" box; instead, the Crystal viewer came up empty. I forgot to check IE version, but we're all on the same flash here.
Concluding the report's volume is too much would seem consistent with the error appearing only after the report exceeds about 15 pages. Also, I read on the Microsoft site that a message about referencing memory at 0x0000000c meant an attempt to access memory beyond the limits of a stack.
However, why is the other application able to run this report at any length?
Could my application be too bulky? Where could I find the evidence?
Better yet, how could I get this thing to WORK ?
Any input appreciated.
Christian
I use: Windows 2000; SQL Server; Crystal Reports 8.5; IE 6
More information about Windows stop messages (e.g., memory could not be read) at