VB6 and Crystal Reports

[vlogan]

I am utilizing VB6.0 and Crystal Reports 9.
I have several external reports which I call from VB. On some reports when I run only that report and then exit the application I receive the following error:

The instruction at "0x760817db" referenced memory at "0x760817db". The memory could not be "read". Click OK to terminate the program.

I am closing out each report call exactly the same way, and I make sure that the objects are set to nothing when I exit. This only happens on some reports and does not happen if I run more than one report when the application is open.

Any ideas?

[Hack]

Welcome to the forums.

Does it always happen to the exact same reports?

[vlogan]

Yes, always the same reports. But if I run the same report twice in a row without leaving the application the problem does NOT occur.

[Hack]

Are these reports being run locally or off of a network file server?

[vlogan]

Locally

[Hack]

Locally

Is this the only machine that runs this application with the reports? Have you tried it on others?

[vlogan]

On all machines except my main development box.

I have also copied the application to another development box and the compiled version of the code exhibits the same problem, but in the IDE of VB6 the application does NOT fail.

[Hack]

I know this is going to sound like an odd question, but do these reports have really long names?

I ask this because, since I am at a loss as to what to do next, I Googled your error message, and I found this page on MSDN Support what states this error can occur if you are attempting to programmatically reach a web site with a really long name.

I know this is Crystal related, but it did state that the problem occurs with XP so I thought I would grasp at the straw.

[vlogan]

The average file name is only 8 characters (i.e., crTDBD.rpt).

I just checked and I am running with the latest Crystal Reports updates on my systems.

This is one of those more annoying than catastrophic problems....

I keep thinking that I have a memory leak issue, but the error message seems to indicate otherwise.

Thanks for all of your help.....

[vlogan]

I just found another person who has had the same problem back in Feb 2005. I emailed him to see if he found a solution.


http://www.codecomments.com/archive3...-2-404643.html

[Hack]

I just found another person who has had the same problem back in Feb 2005. I emailed him to see if he found a solution.


http://www.codecomments.com/archive3...-2-404643.html

This is a very odd problem so if you do arrive at a solution, please post it in the event others face a similiar situation.

[vlogan]

Unfortunately the gentleman I emailed has not responded, so this remains an open issue. In the event I find the solution I will certainly post it.

Thanks for all of your help, past and future....

Verne

[vlogan]

My contact in England got back with me...He said they never found a solution to the problem, and are now developing in C#.

Since the problem is not catastrophic to us I will probably just live with it until we also "upgrade" to C# or VB.NET.

Thanks everyone.....

[the_chad]

Hi VB6 Fans. I'm currently using Visual Basic 6.0 (sp6) and Crystal Reports v9. Just a while ago I was suffering the same issue with my report form (the one with the viewer9 control). It showed the report perfectly for the first time, but it just crashed every time I tried to show the report (any report)for the second time. The fix for this is to install the Crystal Reports 9 Service Pack 6: Download the SP6 for Crystal Reports 9 Here

It worked for me.

Best Regards,

The Chad.