on 03-29-2011 5:07 PM
Hello,
I'm getting the below error when a report has an internal error. I can duplicate this error by trying to convert a bad date within a report. Instead of the viewer letting me know there's a bad date, it will throw an unhanded exception:
error:
"Value cannot be null. Parameter name: window"
I have a Visual Studio 2010 WPF project using the WPF Viewer and I updated to Service Pack 1 for Crystal 2008 for VS2010 and I'm still having the issue.
I understand there's an issue with a report but if an end user gets this error, they will have no idea why.
Any ideas?
Thanks,
Tyler
Try - Catch?
Check to see that the date is correct before trying to convert it?
- Ludek
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I´m getting exactly the same problem in one of my projects. i´m passing a few parameters but no parameter named window and the report got no parameter window either. Anyone got a clue?????
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi all,
I find reason and solution on WPF Crystal Reports exception: Value cannot be null. Parameter name: window.|WPF exception: Value cannot be null. Parameter name: window - SOLUTION;
Thanks.
Martin
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.