AccessViolationException occurs while setting data source to a datatable

Question

Dear All,
I have recently encountered problem while generating Crystal Report (version 11.5) in my VB.NET project and see if you can help to provide a solution for that. In particular, the following access violation exception occurs when setting data source of a report object to a datatable:
"Attempted to read or write protected memory. This is often an indication that other memory is corrupt."
Then if i press F10 to step over in VS2008, the exception won't occur again and the report can be printed successfully with data from datatable. So it does not fail all the time but only the first time...
My code is rather simple and it looks something like this where ds is declared as a dataset filled with data:
Dim crApp As CRAXDDRT.Application
Dim crRpt As CRAXDDRT.Report
crApp = New CRAXDDRT.Application
crRpt = New CRAXDDRT.Report
crRpt = crApp.OpenReport("C:\some.rpt")
crRpt.DisplayProgressDialog = False
crRpt.DiscardSavedData()
crRpt.Database.Tables(1).SetDataSource(ds.Tables(0), 3)  <--- exception occurs at this line
crRpt.PrintOut(False)
Also, from the exception details, the problem appears to be thrown from the driver crdb_adoplus.dll which I have installed the latest version (11.5.11.1470) with CR XI R2 SP5.
Kindly reply if you know what's going on... Thx!
Stephen

Answer 1

Hi Stephen,
As I said, craxddrt, embeddable designer control, is not for your use other than designing reports within the .NET IDE. You CAN NOT distribute this dll and it's dependencies. You are NOT licensed to use use it in a runtime application.
As you say it may possibly work but it is not supported other than designing reports in the IDE and again you are NOT licensed to distribute it.
Next issue is the RDC ( Either craxdrt.dll or craxddrt.dll ) in version XI R2 ( 11.5 ) is still supported but again only supported in Visual Basic 6. The RDC is COM and was never designed to work in .NET.
COM and .NET are two completely separate code streams, there is no direct convert from the RDC to .NET. Same functional API's but completely different way of implimenting them.
For more info on how to use and for sample applications click on this link:
http://www.sdn.sap.com/irj/boc/samples?rid=/webcontent/uuid/80774579-b086-2b10-db91-ed58c4dda375 [original link is broken]
So even though it may be partially working there is no point in continuing this post concerning the RDC, it's simply not supported for what you are doing and you are not licensed to deploy it.
Thanks again
Don