Richard is exactly right - put a breakpoint on the first line in the method, and single step through the code. At each point, look at the appropriate variables and see which of them is wrong. You can then try to work back to where that wrong value came from, or at least give us better information on the actual problem.
Normally, an exception holds a good level of detail - including the line number that the error occurred on. This can help - but only if you tell us what the error message is exactly, and which line it appears on!
If you get an email telling you that you can catch Swine Flu from tinned pork then just delete it. It's Spam.
Last Visit: 31-Dec-99 18:00 Last Update: 29-Jul-16 10:15