I need to quickly build a report. In VS 2010 when I'm adding new item in the 'Reporting' brach there are 3 items:
Report Wizard;
Report;
and
Crystal Report
I tried to play with the first one - couldn't find a way to get the data through existing entity model. Also I stupidly confused what's the real difference between 'Report' and 'crystal Report'?
Could you guys point me out at some walkthrough tutorial or something about how to build a simple report using these things?
Thank you.
Here's the Microsoft link regarding the wizard:
http://msdn.microsoft.com/en-us/library/bb558709.aspx
One is a Reporting Services report and the other is Crystal Reports. Two completely different models.
Related
How do I generate a Database diagram in Visual Studio Code automatically without having to actually create the tables one by one?If that's not possible what other app can I use for this?I'm a Mac user, so it would be helpful for any recommendations for apps that can do it automatically.
I use DataGrip on daily basis and it has the functionality that you want.
https://www.jetbrains.com/datagrip/
Main issue is the license cost, but you have 30 days trial or you can apply for student license if you're gonna use for academic purposes. It does have Mac support
You can check their documentation for it. https://www.jetbrains.com/help/datagrip/creating-diagrams.html
Good morning fellow stack overflow people, I have a question that sounds like the start of something from the daily wtf.
The company that I work for is not so much sacred of new technology they just seem to let things slip, you know the type, “It worked 5/6+ years ago so I don’t see why we should change it”
Despite this I have managed by hook or by crook to get an installation of SQL server 2008R2 to develop on which has the reporting services. Excellent I think, I can finally start moving some of the access applications to VB.net and use SSRS to provide some embedded reports, everyone is happy.
But not so fast, it turns out the standard build of desktop here only has .net1.1. I have managed to dust off a copy of visual studio 2003 (The last edition that could target 1.1) and built a few little tests to check DB connectivity. The problem I am having is the report viewer control is only available in .net2.0 and above.
So what options do I have for displaying my SSRS reports in a VB.net1.1 thick client application?
Before anyone asks the following options are out
Going anything web based (Farrrrrrrrrr too modern for the company + no web server)
Upgrading to a version of .net released after George Bush the 2nd lost an election but still became president
Changing jobs
Sorry for the long question but I thought some background would help
I would go for a browser control but I think they only started including that in 2.0. But I think you can still do something like that in 1.1 (it has been to long to be sure).
I think if you install SSRS on the sqlserver you could turn on IIS on that server and then use that to make your reports and show them in the browser control.
SSRS (I'm pretty sure it came out somewhere around 2005) is not old enough to have many other options.
If you work with VB.NET 1.1 all the time then it is strange question. How did you program in it before?
Use any available dataview control (I already do not remember - DataGrid, DataList, Repeater) from .NET1.1. There is nothing in ReportViewer that could not be done before its appearance, in .NET1.1.
What is the problem?
Update:
I remember seeing code projects reproducing ReportViewer in .NET1.1 few years ago though I cannot find it now. Anyway, it seems to me the problem of just reading .NET1.1 docs and searching internet.
Sorry if this is a blunt statement but sometimes, you've got to bite the bullet and do the right thin.
If you really want to use reports and you've found the minimum version of the .NET framework is 2.0 then go ahead, find an internet connection somewhere and upgrade the computers.
If you can't do that, forget about it and go back to your VB6 or whatever you're using. Besides, .NET Framework 2.0 sp1 is less than 30MB. If you can't find a decent internet connection (either at your workplace or somewhere else) to download it then you might as well abandon it.
And I'll add as well. VS2003 IS OLD! Get yourself minimum VS2005, even if it's Express edition, it's good enough and stop whining.
Someone had the same question back in Feb. Maybe this might send you down the right path:
Using SSRS in ASP.NET 1.1
Simply put: I have a database design in my head and I now want to use Visual Studio 2010 to create a WPF application. Key is to use the VS2010 tools to take much as possible manual work out of my hands.
The database engine is SQLite
ORM probably through DBLINQ
Use of LINQ
The application can create new, empty database instances
Easily maintainable (changes in data model possible)
Questions
How do I start designing the database model (visually) in Visual Studio 2010? Should this be an xsd? Do I do this in a separate project?
Next, how can I make the most use of VS2010 code generation tools to generate a Data Access Layer?
I suppose the Data Access Layer will be added as a Data Source (in another project?) and from there it's a rather generic data binding solution?
I tried finding clear examples of this but it's a jungle out there, the hunt for a solution is NOT converging to one clear method.
Update
So I decided to use ADO.NET entity framework, DBLINQ is out of the picture. I downloaded and installed the System.Data.SQLite ADO.NET provider which integrates with VS2010. From the VS2010 Server Explorer one can create and design a new database but it could be done with a standalone tool for SQLite as well. I then created a new WPF application project, and in the solution explorer added an ADO.NET Entity Data Model, which automatically generates an edmx with C# code (which is the Data Access Layer) from the already created database file. WAF (waf.codeplex.com) seems like a good idea to implement the rest but plain LINQ to SQL will do. This (click here) is also a very helpful question on stackoverflow.
Kay,
Please consider using ADO .NET Framework. It's supported by VS 2010 and LINQ (quick article).
There is one thing you must know before designing your architecture. BLL (Business Logic Layer) is a layer of logic specific for a particular data usage, hence cannot be generated automatically by (whatever you will use) framework. I guess you had Data Access Layer in mind - don't worry about that - if you're going to use ADO .NET and LINQ to Entities, DAL will be generated for you automatically. LINQ to Entities together with ADO .NET Framework are powerful set of tools which should 100% cover your needs. Additional info about LINQ to Entities.
Please feel free to ask if you have any questions.
I have an WPF application for 60 users tops.
Some of they are cashier users, and I use RDLC reports to show customer orders.
The problem is, users are telling that application is getting slow or hanging.
This WPF application uses most up-to-date Enterprise Library. Connection pooling is handled by default, there's no customization.
RDLC files use dataset XSD files. XSD files use database stored procedures to select data.
On xsd files used by RDCL I have something like:
Data Source=Junior-PC;Initial Catalog=FoodAndBeverage;Persist Security Info=True;User ID=sa;Password=mypass
On c# code-behind, the static connection string:
Data Source=Junior-PC;Initial Catalog=FoodAnBeverage;User ID=sa;Password=mypass;Connection Timeout=4
Every 30 seconds I also have a DispatcherTimer to check if Database Server IP is found.
Anyone having similar problems regarding this slow WPF application issue using RDLC? Would it be a problem with WindowsFormsHost getting slow, which shows RDLC reports?
What could I do to speed up?
While I was looking for a solution of another problem of reportviewer (rdlc), I've seen a remark of Brian Hartman, that the report viewer 2010 has a fix for some memory issues. Googling about memory leaks showed me among others this post:
http://social.msdn.microsoft.com/forums/en-US/vsreportcontrols/thread/d21f8b56-3123-4aff-bf84-9cce727bc2ce
Please note that using ReportViewer 2010 has currently some compatibility-problems (and a new rdlc-format). Test it before using.
In my project i have used WPF and am following MVVM pattern. So i have a report module in my project and the reports are just plain reports. So i would like to know should i use SQL Reporting Service 2005 to create reports and then use report viewer as client or should i go for WPf Fixed Document Control- Document viewer.
Can anyone please tell me which of these will be easier to integrate with my project.
Please reply
Thanks
Sharath
WPF Document (Fixed or Flow)
Pros:
Easier to integrate. All is included in regular WPF
Native
More control on the output
Cons:
Must program a lot for a multi-page report
Must program a lot for headers, footes, groups, etc.
SQL Reporting Services
Pros:
Mature tools
Interoperable with other solutions (IE asp.net)
Groups, totals, page headers, graphics built in
Cons:
Not native, must use a embedded windows form control
Must deploy the reporting service runtime separately (not good for click-once apps)
Hard to integrate to your business objects