It might be that I am wrong here and there is a properly set DataSet even at that point, and the issue happens a little later in the viewer. You could put a breakpoint there and see if this is true (where SetDataSource is used). The error message usually would indicate that the DataSet (DataTable in this case) is not set at the time it is used in the report object. Short guess add this to your app.config file:
Of note, at this time SAP does not support VS 2017, and there is possibility that has something to do with this, but I've seen similar messages even back in VS 2010 so here goes. This might not be an complete "answer" since you're still troubleshooting, and asking for help, but its too long for a comment. There is no operation related with on x86. It succeeds onĬ:\Windows\assembly\GAC_MSIL\CrystalDecisions.Web\.0_692fbea5521e1304\Īnd then two BUFFER OVERFLOW occurs on this same file. Process Monitor shows that my program performs CreateFile operation on following filesĬ:\WINDOWS\Microsoft.Net\assembly\GAC_64\CrystalDecisions.Web\v4.0_.0_692fbea5521e1304\Ĭ:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\CrystalDecisions.Web\v4.0_.0_692fbea5521e1304\Ĭ:\WINDOWS\Microsoft.Net\assembly\GAC\CrystalDecisions.Web\v4.0_.0_692fbea5521e1304\Ĭ:\WINDOWS\assembly\GAC_64\CrystalDecisions.Web\.0_692fbea5521e1304\Īll fails with PATH NOT FOUND Result. (saved the datatables in xml and both files are exactly the same). Source Code for showing the report is c = newĬ() Ĭ.FileName = System.IO.Path.Combine(Root_Path,Ĭ.SetParameterValue("prmSystemDate", Current_Date) įrmReportViewer v = new frmReportViewer() Īnd frmReportViewer FormLoad is private void frmReportViewer_Load(object sender, EventArgs e)
Using Visual Studio 2017 Community (tried VS 2015).Application Target Framework 4.6.2 (i even tried it on 4.0 but same error).Installed Crystal Reports Tried installing 13.0.20(latest) and restarting PC but didn't work.64 bit is required because loading data on one of the screen causes a memory issue - so it can't work on 32 bit. My reports work fine on a 32 bit machine but won't open on 64 bit.
0 kommentar(er)
