Cascading Prompts slow with command data sources

[RustyAfro]

I have a report that has a command data source named "qryMain" which takes a while to refresh and drives the entire report.

I want to create a cascading dynamic prompt using a different data source (command) named "qryUsers"

I created that second command data source but didn't link the two commands together as it doesn't seem like it should be necessary. I do get a warning about this "not generally being supported".

I setup the cascading prompt to the columns in "qryUsers" and then referenced the cascading prompt in the SQL of "qryMain" - and it works exactly as I wanted it to...

Except, when the user clicks the refresh button just to get to the prompt selections, it seems like both commands are refreshing as it takes a long time to open where before it was quick.

"qryUsers" on it's own takes 1/10th of a second to run normally, so it can't be slowing it down.

My question is, is there anyway to force crystal to use the data source for the cascading prompt Without refreshing the first query (if that is in fact what is occuring)?

Thanks everyone,

 

[RustyAfro]

I timed this and it seems that it's not "qryMain" running afterall, but there is still a bit more of a delay than I would like before the prompt window opens. If anyone has any insight, please let me know

 

[synapsevampire]

Yep, it's kinda slow, but your method is correct.

-k