I might have seen this before. I am assuming this is not a
problem with connecting to your DB because you are passing
your DB to the rpt seperately beforehand, and this error
makes no sense, right?
I had a case where I would get a "Login failed" error like
this and it was because I had changed my dataset and the
report was not aware of the change (e.g. change the name
of a field in the dataset that you are using in the
report, and the report blows up because it can no longer
find the field it wants). The dataset in the report and
the dataset in your app get out of synch. This would not
have been so bad if the error message was meaningful. They
really need to update this error message...
Try updating your dataset in your report. I think you
click on it then right click and refresh or something like
that - cannot remember exactly. Or maybe go to the
database view where you see your dataset or whatever.
Sometimes Crystal run from within VS .NET will not pickup
changes to datasets correctly. You have to close the whole
solution after making changes to your dataset, then open
up visual studio again and find your rpt and then try to
refresh your dataset inside your report.
Hope that helps.
>-----Original Message-----
>Help....
>
>I've created an ADO.NET dataset in Visual Studio (a web
>project). I build the project and then try to create a
>Crystal Report using the dataset.
>
>When I try to use the ADO.NET dataset in Crystal Report
>(selected from Project Data) by double clicking the
>dataset name (yes, it does at least show up) I get a
>consistent error: Logon failed. Details: Object reference
>not set to an instance of an object.
>
>I've tried running a repair installation on VS, I've
>researched Crystal knowledge base, nothing.
>
>Thanks,
>Bob
>.
>
|
Similar Threads
