We've implemented the use of the query governor on our SQL 2000 database for our Crystal report queries. The problem I'm having is trapping the returned error code, before crystal displays an unfriendly .dll error message. When I run a report in designer which is killed by the governor, I get a message complete with the description that explains the error. When I attempt to view a report via the activeX viewer that is killed by the governor, I get a generic .dll error message. The reports all use stored procedures as a data source. Is there a way to trap these error codes in the beforeRecordsRead process and then display a more friendly message to the users?
Thanks in advance for any help here.
Rick
Thanks in advance for any help here.
Rick