This is driving me insane. I am trying to get a basic Report to show with Report Viewer but cant get the DataSet to show in the Website Data Source window no matter what I do.
I created a dataset..picked the proc I want, etc. without any problems. I added my RDLC and tried adding a table that I can bind data to but the Windows that contains the Data Sources is empty.
Im using VS 2008. Is there anything im doing wrong? Ive followed some tutorials but cant get further due to this issue.
Ok..figured it out after wasting 1 day on it.
As I said i am running VS 2008 and what I did was remove all the DLL references one by one until the window populated with some datasources. I found out a reference to Entity Spaces cause the problem. So I create the reports and when im down add back the reference. A pain but it now works.
Jeeesh.
Related
I have been struggling with this issue for two years now. My problems are happening in Visual Studio 2013 (not a web server).
Occasionally, I have to take an RDLC file that was created by someone else and make changes to it. Using VS, I create an XSD file for the dataset, then replace the DataSource and DataSet in the RDLC so that the report now points to the tableadapter(s) in the XSD.
Often when I try to view the report in the ReportViewer form, the Report Data Source and Data Source Instance are blank. I've tried Rebind Data Sources, and I've cleaned and rebuilt the project, but I can't get the data source to show up. Sometimes the report will have a subreport, and that data source will be available if I choose that RDLC.
I'm a third party developer -- I'm not editing (and cannot edit) aspx files; just the reports. I've tried editing the code in Form.vb manually to insert the TableAdapter, but it hasn't worked, and I don't really know what I'm doing there -- I have some object-oriented programming experience, but not much.
What can I do to make the data source available to the report viewer and/or bind it to the RDLC? Any suggestions are appreciated. Please let me know if there's any particular code it would be useful to share.
Thank you.
I ended up doing the following, which solved the problem in this case. Not sure it's a solution that will work in all situations like this.
I replaced the opening Report tag in the XML of the RDLC with this:
<Report xmlns="http://schemas.microsoft.com/sqlserver/reporting/2008/01/reportdefinition" xmlns:rd="http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">
I removed the <ReportSections> and <ReportSection> tags, as they are not supported by the 2008 schema. I didn't remove anything that was between the tags.
After making these changes, the data source became available to the form, and I was able to preview the report.
I am new in vb.net programming. Am facing a problem in database handling. Am using oledb to deal with database, which is MS Access in my project. I am dealing with queries at the time. Now the problem is that my queries are working well on vb form but are not affecting the actual database. For example, when am adding a record, it displays 'record added successfully', the message I have used for my conformation, but the actual database is not displaying the record I just entered and even got the above conformation message as well. I have checked query in sql editor too, its doing well. I have checked locals in vb debug mode, all are containing correct values.
Am not getting what's the reason behind that. Why it is displaying the success message but not modifying the actual database. Same is the case when am firing delete query, till now. I have not tried Update query yet.
Technology - Visual Basic.net with MS Access
Am using Access 2007 and Visual Studio 2013
Please Help by your suggestions
Do the controls on your form have the correct control source, i.e. the database table/query from and to which it should be reading and writing to?
Basically the problem was the gap between my understanding and .Net's working.
Here is the solution.
You can include database in two ways:
1.Either importing it directly to your project from the place, for example using drag and drop, or some other such method.
2.Or, by including it via using wizard.
But, the difference lies in connection string you use in your project, if you give absolute path of database, then you will directly see the alterations in database you have done using your application, even in testing and debugging mode via IDE.
connection.ConnectionString = "Provider=Microsoft.ACE.OLEDB.12.0;Data Source=C:\xyz.accdb"
But if you are using connection string provide by wizard, for example,
connection.ConnectionString = "Provider=Microsoft.ACE.OLEDB.12.0;Data Source=|DataDirectory|\xyz.accdb"
what the IDE will be doing is whenever you will be running project for debugging or testing, every time, it will copy the actual database, with its contents as well, in /bin/Debug folder. So, the changes you are performing will only be visible to that copy, not the actual file. So, if you want to verify with the database, like in our case, check the copy of database, which will be present in /bin/Debug folder. You will see the changes there. But, every time you run project for debugging, it will replace that copy with original one.
So, actually I was checking the original database file, not that copy, since the changes were only made to that copy. So that is why I was facing the above problem, not due to any programming fault.
I am getting an error that makes no sense when saving a table created within VS2012, SQL Express 2008 R2.
Item in the Virtualizing TreeView cannot be null
This is a table save not a rebuild, unless that happens anyway. But I do not get this error at any other time, even after creating new web page, or saving changes to an existing page.
Really not sure where to look for the cause. I have not changed any of the pages that use the treeview in over 3 years. They are in a totally different part of the web site.
Any help appreciated.
I also encountered the same problem some time ago and landed here to see not much solution has been provided.
What I found is that, if that instance of VS is closed and a new instance is reopened then that error is getting resolved.
Hi you can go to server explorer in VS and right click on your connection. It will ask you for Database Diagramming select yes for it. Now you will not get this error.
OK, I'm an old dog (slowly) learning new tricks and I need to see the cogs turning in order to understand what's going on.
I've generated an MVC3 app using EF4.1 from an existing database and the list in the MVC3 view (based on a SQL View) shows different results to the SQL View viewed in SQL manager. Specifically, fields from a joined table seem to not get updated between multiple hits on the main table.
The funny thing is: If I capture the sql that intellisense shows for the db.myViewClass.ToList() call and paste that into SQL manager, it gives the right results!
I've also created a mini test app and that works fine. So far I can't see how the test app differs from my main app which fails.
I'm frustrated that I can't step in to the code to see what's happening in db.myViewClass.
Any bright ideas anyone?
Dave.
I'm having this problem:
The SQL Server holds a said value, let's say 990.30, the Reporting Services Report show a different value (948.33) when viewed online, in the brower and a third value (912.22) when the report is exported to Excel.
There are no formulas on Excel, just plain values.
Also, there's no formula on the layout of the report.
The code shows only a simple select that, when run on the SQL Server Management Studio, returns me the original value (990.30).
How on earth shall I start to troubleshoot this ?
I've never heard of this kind of problem before. I would recommend submitting a ticket to Microsoft and provide them with screen shots of the errors, the RDL file, a sample output of the stored procedure, etc.
To troubleshoot this on your own, I would recommend creating a new report that just has a simple table that returns all the details from your stored procedure or query to validate the values are consisten across all interfaces. From there, just start adding on complexity until you get the report to look like it is today.