DaveyDSmith
Programmer
- Mar 21, 2008
- 19
I have written a fairly complex report with 4 groups and quite a few manual running totals (because Sums & Running Totals would not work on my field choices). Also, there are a number of if/then/else statements. The database is Pervasive SQL v10 & I wrote it in Crystal v2008.
I have tried to run this report on 3 different computers, 2 different databases, and 2 diff operating systems (Vista & XP). On 1 computer, crystal crashes. On 2, I get a runtime error "Microsoft Visual C++ Runtime Library > Runtime Error! Program: ...ects\BusinessObjects Enterprise 12.0\win32_x86\Crw32.exe > abnormal program termination" I am running XP Pro SP3, with 3g of memory and 50+gigs of free hard drive space. When I run the report on a small sample database, it runs fine. The problem occurs on my client's database which is much larger.
I have also removed & reloaded Crystal. I have SP1.
I googled the error & that led me to some registry cleaners, but am not sure I want to do that. Some people think they help & some think perhaps they do more harm than good sometimes.
Since the report runs fine on a small database and will not run on a large database, could I have a "time-out" issue?
One more thing, when I hit OK after entering the parameters, the report is "accessing the database" for about 8 - 9 minutes. The very moment it begins "reading records" that is when it either crashes or throws up the runtime error.
I have tried to run this report on 3 different computers, 2 different databases, and 2 diff operating systems (Vista & XP). On 1 computer, crystal crashes. On 2, I get a runtime error "Microsoft Visual C++ Runtime Library > Runtime Error! Program: ...ects\BusinessObjects Enterprise 12.0\win32_x86\Crw32.exe > abnormal program termination" I am running XP Pro SP3, with 3g of memory and 50+gigs of free hard drive space. When I run the report on a small sample database, it runs fine. The problem occurs on my client's database which is much larger.
I have also removed & reloaded Crystal. I have SP1.
I googled the error & that led me to some registry cleaners, but am not sure I want to do that. Some people think they help & some think perhaps they do more harm than good sometimes.
Since the report runs fine on a small database and will not run on a large database, could I have a "time-out" issue?
One more thing, when I hit OK after entering the parameters, the report is "accessing the database" for about 8 - 9 minutes. The very moment it begins "reading records" that is when it either crashes or throws up the runtime error.