Cystal: "Failed to open a rowset"

[Guest]

I have a Crystal report that, if certain parameters are entered, returns no data. This is fine if I call it from VB6 - it just returns a blank report. However, from VB.Net, it gives me an error message of "Failed to open a rowset". Is there a way to suppress this message? It's going to worry the users

Thanks...

 

[Bernie Yaeger]

Hi,

Can you test the rowset num row returned first? If so, then
if rownums > 0 then
' print report
else
' messagebox 'no rows in the current capture, thus no report will print'
endif

HTH,

Bernie Yaeger

I have a Crystal report that, if certain parameters are entered, returns

no data. This is fine if I call it from VB6 - it just returns a blank
report. However, from VB.Net, it gives me an error message of "Failed to
open a rowset". Is there a way to suppress this message? It's going to worry
the users.

 

[Guest]

Thanks, Bernie. Unfortunately, the only way I can test the rowcount is by running the stored procedure separately first, which means I'd have to hit the database twice

It looks like this might be the only solution, though, so thanks.