By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
449,140 Members | 1,290 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 449,140 IT Pros & Developers. It's quick & easy.

Cystal: "Failed to open a rowset"

P: n/a
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...
Nov 20 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
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

"InvisibleDuncan" <an*******@discussions.microsoft.com> wrote in message
news:A9**********************************@microsof t.com...
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...

Nov 20 '05 #2

P: n/a
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.
Nov 20 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.