لطفا منتظر باشید ...
Summary
This author tries to refrain from bold, sweeping statements about personal topics, but in this case, though, I'll make an exception. I don't know about you, but I sure did learn something:
If the Crystal Reports 8.5 report you are working from is using up-to-date database access methods, there aren't really any problems with the connectivity - despite many rumors to the contrary.
Once you save a Crystal Reports 8.5 report in Visual Basic .NET, you can no longer open it in Crystal 8.5.
Think objects. Crystal files, like DataSets, become objects in the world of .NET. Understanding that conceptually will give a programmer a much greater understanding of how to manipulate third-party structures like Crystal Reports.
The Upgrade Wizard, while a file tool, probably isn't worth the effort for programs using the Crystal Reports Designer. Export the reports, and recode the application by hand. It will turn out much cleaner, and simpler.
There are a number of articles recommended for further reading on this topic.
.NET VB Migration tool does not convert DSR files to RPT files http://support.crystaldecisions.com/library/kbase/articles/c2010234.asp
Saving an existing report causes the .NET Report Designer to close unexpectedly http://support.crystaldecisions.com/library/kbase/articles/c2010272.asp
Changes to a Version 6 Report with saved data may not save correctly in VB .NET http://support.crystaldecisions.com/library/kbase/articles/c2010273.asp
Err Msg: "Crystal Dictionary not supported in this version" in .NET Designer http://support.crystaldecisions.com/library/kbase/articles/c2010338.asp
Err Msg: "Invalid report version" when opening a .NET report in CR 8.x http://support.crystaldecisions.com/library/kbase/articles/c2010775.asp
Err Msg: "Query engine error" when connecting to AS400 via OLE DB in VS .NET http://support.crystaldecisions.com/library/kbase/articles/c2011092.asp
After spending a little more time with the product, you might note that accessing reports via ASP.NET rather that in a Windows Application causes a few more data problems than encountered in this appendix.In working with clients on the issue of converting Crystal Reports 8.5 reports to a .NET environment, the general consensus is that conversion is good, but the creation of a reporting system with the .NET Framework, or use of Crystal Enterprise, is even better.
