-
Note: I am posting this in both the General and Database forums.
When I ran my Crystal Report (the source of the data is a SQL Server stored proc) out of VB, I get no results.
OK, to see what's going on, I ran the query in SQL Server analyzer, and lo and behold, there is a bug in the s.p. that causes the s.p. from completing (turns out a division by zero error was occurring in some cases). But this is not a problem, I can fix it.
The problem/question is that in the VB Sub that is executing my Crystal Report, there is an error-handler, so I would expect an error to be thrown if Crystal had a problem running the report. But no error is thrown; the report runs and produces 0 records (no output).
How do I get the error to be thrown by VB?
-
Why not
Execute the SP from VB in an ADO command to return the recordset.
Test the recordset for a record count and then pass it to the report.
