Thank you for your very definitive response. You have made it very clear by reiterating my findings that, even though the compatibility issue has been resolved in version 14 of crviewer.dll, there is no intention on the company's part to support any type of licensing agreement which will make available these files for developer access. Though I have been able to ascertain and rectify the source of the error, you have adamantly stated the solution is beyond what the company is willing to license.
As to your question below:
"Even if you are able to make this work, how do you plan on deploying the runtime now? There is no MSM or MSI that includes the above file (not for version 13 and higher anyhow)"
I have been able to make this work, and I have found your posting here: http://scn.sap.com/message/10814217 where you stated:
" CRVS2010 is essentially equivalent to CR 2011"
and I was curious if this included the crviewer.dll above version 11.5. I have not looked into this yet. Our application uses both VB and .NET. The VB app was written first, and it was later expanded by .NET. This one out-of-memory error is the only thing standing in the way of our application working on Windows 7 64-bit. I have tried many ways to solve it with the current 11.5 SDK, even with the assistance of Microsoft. The answer was stumbled upon when the wrong version of Crystal Reports was installed in an attempt to replicate the issue. I'm sure you can imagine my frustration in finding that the later versions of the crviewer.dll will solve this issue I've spent many, many days trying to debug, only to be thwarted by licensing support when I finally found a solution.
Unfortunately, the solutions on your blog do not pertain to my issue. I am unsure how to proceed to debug the out-of-memory error, because I have no way of stepping into the crviewer.dll to find the point where it is happening. I only know that it happens when I have an Crystal ActiveX Report Viewer in my form and is thrown upon the form initializing. When I remove the viewer, the error goes away. I know it works when I run using Visual Studio's VSHOST and does not work without it.
We have no intention of contravening our license agreement. I was simply asking if there was anything we can do to make this work within the scope of the agreements. Even better, I was asking if you are familiar with the resolution to this out-of-memory issue, or how to debug such issue, as the issue is resolved in later versions of the file.
Thank you,
Zachary