want to see a grown man cry..errors after changing framework 4.0 to 3.5
Long story short a few weeks ago my pc crashed and I lost my entire project. I have spent every spare minute getting back to where I left off.
I the last 2 days I have been working on crystal report using project datasets. I was running into an issue and it was suggested I change my framework version to 3.5 which I did. Now I have over 100 errors. Most appear to be related to table adapters or table adapter managers.
Is there anyway to recover from that?
Thanks
LB
Re: want to see a grown man cry..errors after changing framework 4.0 to 3.5
Re: want to see a grown man cry..errors after changing framework 4.0 to 3.5
That was my first thought. I changed it back to 4.0 and actually have a few more errors.
Seems like that is my mo...2 steps forward 3 back.
It looks like my only recourse is to start the project over AGAIN.
LB
Re: want to see a grown man cry..errors after changing framework 4.0 to 3.5
Maybe if you were to actually describe the errors rather than just say that they exist, then we may be able to determine the cause. That said, you could simply delete the whole typed DataSet and create a new one.
Re: want to see a grown man cry..errors after changing framework 4.0 to 3.5
Sorry Jm
I am not allowed to visit forums on my work computer. I'm posting using my cell phone.
I am getting errors like.
TableAdapterManager is not a member of RAUAcctfileDataSetTableAdapters
Or
Type RiscApplUtility.RAUAcctfileDataSetTableAdapters.TableAdapterManager is not defined.
I basically see an error like that for every dataset.
Thanks
LB
Re: want to see a grown man cry..errors after changing framework 4.0 to 3.5
You could have a look in the DataSet code file and see if there is indeed a TableAdapterManager class definition in there. As I said though, deleting the DataSet and generating a new one should probably do the trick. As long as you haven't done significant customisation in the DataSet designer, it should be very quick.
Re: want to see a grown man cry..errors after changing framework 4.0 to 3.5
I was able to get my datasets working again.
I followed the instructions in this guide:
Crystal Reports for Visual Studio .NET - Walkthrough - Reporting Off ADO.NET Datasets
So I created my report in designer using the same dataset I used on my form that contains the crystal report viewer that is using my report in question. Just to make it simple I only have a heading and a couple fields on my report.
I run my app and open my report, it has the data I am looking for, however its in a column format with the fields all bunched up, and it does not display my heading I added.
I did verify in my Crystal Report Viewer that I have the correct report selected.
Am I missing something when using a Project Dataset verse using an OLE dataset?
Here is the code behind my form with the crystal report viewer
Imports System.Data.OleDb
Imports CrystalDecisions.Shared
Imports CrystalDecisions.CrystalReports.Engine
Public Class IssueTrackerDetailRpt
Inherits System.Windows.Forms.Form
Protected Friend idToOpen1 As Integer
Public opener As Form
Friend Sub New(ByVal goBackTo As Form)
Me.InitializeComponent()
opener = goBackTo
End Sub
'################################################################
''CR Variable
Dim crReportDocument As CrystalReport1
''ADO.NET Variables
Dim adoOleDbConnection As OleDbConnection
Dim adoOleDbDataAdapter As OleDbDataAdapter
Dim dataSet As DataSet
'#######################################################################
Private Sub IssueTrackerDetailRpt_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load
Dim connectionString As String = ""
connectionString = "Provider=SQLOLEDB;"
connectionString += "Server=1234567;Database=FES Issue Tracking;"
connectionString += "User ID=user;Password=password"
''Create and open a connection using the connection string
adoOleDbConnection = New OleDbConnection(connectionString)
''Build a SQL statement to query the datasource
Dim sqlString As String = ""
sqlString = "SELECT Issues.ID, Issues.Title, Issues.Description, Issues.DueDate," & _
" Issues.Comments, Issues.OpenedDate, Issues.ProjectNumber, Issues.ClosedDate," & _
" Issues.CRNumber, Issues.Scripts, Issues.CorrectiveAction, Status.Status," & _
" MsgSpec.MsgSpec, IssueCausedBy.IssueCausedBy AS CausedBy, Releases.Release," & _
" Contacts.FullName AS AssignedTo, Contacts_1.FullName AS OpenedBy, Category.Category," & _
" Priority.Priority " & _
" FROM Issues " & _
" INNER JOIN Status ON Issues.Status = Status.ID INNER JOIN" & _
" MsgSpec ON Issues.MsgSpec = MsgSpec.ID INNER JOIN" & _
" IssueCausedBy ON Issues.IssueCausedBy = IssueCausedBy.ID INNER JOIN" & _
" Releases ON Issues.EstFixRelease = Releases.ID INNER JOIN" & _
" Contacts ON Issues.AssignedTo = Contacts.ID INNER JOIN" & _
" Contacts AS Contacts_1 ON Issues.OpenedBy = Contacts_1.ID INNER JOIN" & _
" Category ON Issues.Category = Category.ID INNER JOIN" & _
" Priority ON Issues.Priority = Priority.PriorityID" & _
" WHERE Issues.ID = " & idToOpen1 & ""
''Retrieve the data using the SQL statement and existing connection
adoOleDbDataAdapter = New OleDbDataAdapter(sqlString, adoOleDbConnection)
''Create a instance of a Dataset
dataSet = New DataSet()
''Fill the dataset with the data retrieved. The name of the table
''in the dataset must be the same as the table name in the report.
adoOleDbDataAdapter.Fill(dataSet, "issues")
''Create an instance of the strongly-typed report object
crReportDocument = New CrystalReport1()
''Pass the populated dataset to the report
crReportDocument.SetDataSource(dataSet)
''Set the viewer to the report object to be previewed.
CrystalReportViewer1.ReportSource = crReportDocument
End Sub