I just moved a desktop application developed on ms access 2003 to a c# version using crystal reports for reporting. Is there a way for me to move the existing numerous reports from ms access 2003 to crystal reports? talking in terms of the reports design view since they will all remain the same instead of recreating them in crystal reports all over again.
No, this isn't possible to do. You will have to rewrite each report from scratch.
If there is no particular reason why you must use Crystal Reports take a look at SSRS instead. You can import Access Reports to SSRS.
Related
I am using SSRS 2005 in an old project, it has been working perfect with ReportViewer in local mode for many years, but recently I encountered an exception while exporting the excel report. ".xls" file has a max rows limit (65536), I decide to upgrade the SSRS to a higher version.
Since many years past, there generated thousands of reports, the report definitions were saved as XML in the database. I tried to load the old report definition with ReportViewer 2010 (SQL Server 2008 r2), but failed.
After some research, I know it is easily to convert RDL 2005 to RDL 2010 by opening the report in Visual Studio, it did work as expected.
Is there a library or command line tool to convert RDL 2005 to RDL 2010?
I decided to rewrite the logic creating SSRS Report, basically it is translating business logic to a xml string.
BTW, I got this repository: dynamic-rdlc, it is much easier.
I am using Report Builder 3.0 in order to connect to SSRS report server http://mosaic.catex.com/reportserver.
Is there a way to use Power BI to connect to SSRS report server instead?
Thanks
Answering the question that was originally asked: there's no way to connect Power BI Desktop to SSRS Report Server. Power BI Report Server is another matter, but your question predates its release so that is very unlikely to be what you're asking about.
Power BI Desktop (which I presume you mean when you say Power BI) and Report Builder (pictured in your question) are different tools used to build different types of reports. There's no overlap between them and they're not interchangeable.
There's also no way to use an SSRS report as a data source in Power BI (as Alan mentions), though I wouldn't recommend doing this even if it were possible. In SSRS 2016, there is a way to pin SSRS report elements to a Power BI dashboard (as Snowlockk mentions), but I'm not sure that's what you meant by "dashboard" in your comment. The functionality is somewhat limited too (since you need to be running SSRS 2016, and you can only pin chart/gauge/map/picture elements).
When asking if something can be done, it's always helpful to say exactly what you're trying to accomplish just in case it can't be done the way you're asking about, but it can be done another way.
Not sure if this is the correct place to ask, so if not, please direct me accordingly.
I would like to know what the best process would be to change VBA generated excel reports into SSRS reports.
A bit of background, I work for a client who have been generating weekly, monthly and ad-hoc MS Excel reports via VBA macros. Currently, it was a manual process where they need to specify the report to run by calling a VBA macro function directly within MS Access. This macro would then run through all its underlying macro functions in order to generate the MS Excel report based on predefined configurations.
Since macros have become unsupported from Office 2007 (I think), the client is obligated to completely move away from this way of reporting to a fully automated process.
So, how would I go about interpreting the existing macros and generating the SSRS report accordingly?
If the reports are from Microsoft Access, you can try importing the Access reports into SSRS with the Import Reports from the Solution Explorer window.
You'll probably need to make changes and set the datasources to your new location. I haven't actually done this so I can't say how successful it is.
You can then use the Report Server's subscriptions to run the reports.
https://technet.microsoft.com/en-us/library/ms156375(v=sql.105).aspx
Sorry for being a newbie to SSRS.
My design goal:
Near term: develop - using SSRS - a simple client side (no reporting server!) report - based on MS SQL data tables, and embed it into the .NET WPF client (application)
Long term: for additional reports, hire external SSRS experts, so they will provide the reports developed, and I will integrate them into the same WPF application.
I managed to do 2 things:
Develop a simple report connecting to MS SQL, using Reports Builder 3.0 - as a result, an RDL file was generated (the file contains all the DB connections)
Embed a ReportViewer WinForms control into the WPF application.
Unfortunately, I wasn't able to load the report I developed, into the application.
I understood from articles on the new that RDL is not designed to support client-side execution (without a server), and RDLC should be used instead. However, I wasn't able to figure out how to conver the report to RDLC, using the Reports Builder - it does not give me an option to save in a different format.
I would appreciate any hint from the experienced people on how to accomplish my goal.
Specifically, should I use RDLC, and if positive - what's the way to get the report in this format?
Thanks
Max
I would recommend using Visual Studio when creating RDLC reports that will be embedded within an application and run in "Local" mode, and using either Microsoft Report Builder or Visual Studio to create RDL reports that will run in "Server" mode within SSRS.
A RDLC report would be created within a WPF Visual Studio project be simply creating a new Report.
A RDL report would be created within a Reports Server project when using Visual Studio.
Alternatively, it appears you could simply rename the file from RDL to RDLC if you don't mind manually correcting the Data Source information in the report definition file: http://msdn.microsoft.com/en-us/library/ms252109(v=vs.120).aspx.
I can't believe this - I just starting developing an SSRS report, using a SQL 2008 Report Server project in VS 2008. When I try to render the report in the VS 2008 ReportViewer control, I get this error
The report definition is not valid. Details: The report definition has an
invalid target namespace
'http://schemas.microsoft.com/sqlserver/reporting/2008/01/reportdefinition'
which cannot be upgraded."
I understand the error, and it has been well-documented all over the web over the past year and a half or so, but can it be that there is still no way of viewing these reports in the latest ReportViewer control? In other words, all these announcements from last year that MS would release an updated ReportViewer control in Q1 of 2009 that can render SSRS 2008 reports were wrong?
The only workaround is to install SQL Server 2005 RS? How have others solved this? Switch to VS 2010? Can I register the 2010 ReportViewer control with my VS2008 project, and is that going to solve the problem? So many questions, but no answers ...
Unfortunately, that is indeed the truth :-(
See Bill Vaughn's Retraction: The ReportViewer Control Does NOT Support SQL Server 2008 RDL in Local Mode for more details.
Hard to believe - but true :-( Let's hope it'll be better in Reporting Services for SQL Server 2010 - eerrghh... 2008 R2 :-)
Marc