I have an access database that I made on my desktop computer at work. I've tried loading the database on my laptop and a different desktop at work, and on both of them the reports are messed up. The reports are too wide and nothing is lined up how it should be. How do I make it so the reports stay the same across all computers?
do they have to be loaded from the database or can the reports be opened separately?
i haven't checked lately but there used to be a 'Snapshot Viewer for Microsoft Access' that was great for viewing reports, even without having Access.
Related
I have several SSRS reports that need to be transferred to another server. Currently, all reports and SSRS reside on the same exact server as SSMS and all databases. I was wondering if there is a simple way to essentially take everything I have on SSRS (All Reports) and transfer them along with their data sources to the new server that I have. I know downloading all reports and uploading them to the new server is an option but I was wondering if their is an easier/more logical way to go about this process. After completion, SSRS and the SQL Server will be on different servers but still able to work together.
I have had really great experiences with an old (2007) program called "SSRS Scripter" (from Jasper Smith). It seems like it has been absorbed into a newer product called SqlServerFineBuild (which I have never used). The original stuff is a little hard to find, but very nice to work-with, imo.
Microsoft also has another product called Reporting Services Migration Tool (free) https://www.microsoft.com/en-us/download/details.aspx?id=29560 It is a command-line util and isn't the easiest or most-helpful. It has a UI-mode, but it isn't very user-friendly.
Both of these will only extract report files and settings from an existing site. You still need to use VStudio (+ reporting add-in) (and then some RS project work/design/config) to re-deploy.
I am looking for a solution for promoting SSRS 2016 Mobile reports and their associated data sets between environments. Given that the link between the mobile report and the Shared Datasets is based on a GUID, I don't believe that it is possible to do this manually. Losing the Dataset breaks the Mobile reports rendering it inoperable - so you can't repoint it manually.
Does anyone know of a tool which may be able to assist?
Thanks
I just answered a similar question: https://stackoverflow.com/a/47405245/2310818. Basically there are PowerShell commands created for downloading and uploading individual items/folders from one server to another server. I think that will help you migrate Mobile Reports across servers.
I have a program that helps salesmen design and price products. The pricing information for the program is held on the server in a SQL database and accessed with a dataset as normal.
My program will therefore run if the user is connected to the network, but when the salesmen go off site (as salesmen are prone to do) they lose access to the database.
The server instance is professional, but the salesmen will only get an express edition. While I can use push replication to send the information from the server to my laptop in SQL Server Management Studio, I have no idea how to make this work across everyone's installations from visual studio.
I'd appreciate any links to articles I should read to learn more as well as any direct solutions.
Many thanks!
Do you only need this princing information (you're writing 'bout one dataset) then one way would be to just save this Dataset (or 2-3 datasets) as XML on the salesmens Laptop. If you have no connection, you read the XML and inform the user, that he's working offline.
Now this only works, if you do not need to write back the data and there are not thousands of records.
I have a large number of reports that only seem to load when working with MS Visual Web Developer Express. When I put application into production, all my reports just spin and then show nothing.
We need a lot more information to give you a good answer. There are many reasons why this could happen. One possibility - the data source is different on the server than on your local PC. Keep in mind - when you deploy a report to a SQL Server Reporting Services server, and you overwrite an existing report, your newly deployed report will keep the old data source of the report you're overwriting; It will not automatically use the datasource you were using on your development machine if it was previously using something else.
Check in profiler if the Database dou think is accessed is accessed by reportserver.
If not check the datasource in http://yourreportserver/reports/
Have you tried running IE8 in compatability mode?
#mike, as you said, while you already check and recheck the data source but still some user can use the report, and some other dont.
Lets have some scenario. User A work on PC A001 can use the report, while user B, work on PC B001 cannot use the report.
Please recheck whether user A still able to use the report in PC B001? if that the case, the problem is in the user right. but if not the problem is in IE/machine configuration.
hope that helps.
I'm working with WinForms a project that has a couple of oddball requirements. This is an existing business system that is installed in numerous locations under a fairly wide variety of environments. Part of this variety is a mixture of SQL Server versions, and--of particular importance--SQL Server Reporting Services versions. Everyone is on at least 2005, but about 50% of our users are on some flavor of 2008.
Unfortunately for me, I need to be able to run a client-side report that's written in 2008-version RDL. I can't modify the report in any substantive way at this point, so rewriting it in 2005-version RDL isn't an option. The catch is that this report (as it's written in 2008) requires the 2008 ReportViewer control. However, the 2008 ReportViewer control cannot connect to 2005 SSRS.
The solution that I've come up with is more than a little hacky, but it will alleviate 90% of the problems introduced. I've left the references pointing to the 2005 version of ReportViewer, and I'm modifying the application configuration on startup to add assembly binding redirection tags moving from version 9.0.0.0 to 10.0.0.0 for ReportViewer.Common and ReportViewer.WinForms if the user's target report server is running 2008.
As twitch-inducing as this solution is, it's working for me. The users running SSRS 2005 can still access their existing reports, just not the new one. The users running SSRS 2008 can access everything. My only problem is that I haven't been able to find a way to refresh the configuration data. I'm updating this info before any of the assemblies are loaded, but calling ConfigurationManager.RefreshSection("runtime") doesn't appear to have any effect. Once the app restarts, the proper assemblies are loaded, but I'd really like to be able to have this change take effect immediately.
Any thoughts on how I can force the runtime to reload the binding redirection information from the App.config file at runtime?
Once the AppDomain is created, the configuration data that affects binding is fixed. Which happens on the default CLR when the primary AD is created, before your code starts running. If you are really desperate then you could create a secondary AppDomain and give it a custom AppDomainSetup with another ConfigurationFile. And loads and run your regular startup code in that AD. Not exactly sure what kind of side effects this might have.