Conditionally set viewbox query

[gianfior85]

Is there a way to conditionally adjust the query used in a ViewBox control?

In a grid, you can use “e.tmpl.CS.SQL” in the onGridExecute event to conditionally set a SQL query. In a list, you can use the list's beforeQuery event to do the same. Is there an event or somewhere to do the same for a ViewBox with Database Query as its datatype? Or would a Viewbox require writing an Xbasic function and using a custom datasource?

My particular use case is merely adjusting the WHERE clause based on some session variables. One option is having multiple viewboxes, wrapping them in a container, and setting the serverside show/hide expression based on those session variables, but that is a bit of a pain for maintenance and can get out of hand if there are multiple conditions needed in one component.

[madtowng]

Pete Conway and Lance Gurd are far more qualified to answer this question than I am, but
I have started using viewboxes in place of grids.
My preferred method is to pull all the data for the user from sql at the beginning, then filter the
data to suit the user's needs.

I do use more than one viewbox to do this, but the filtered viewboxes are copied from the original,
then populated programmatically.

If you have any questions about the speed, check out Video Finder (youshould-seethis.com)
After clicking the Get Started button, a list of videos will be displayed.
The primary channels are Alpha Software and Web Dev Simplified (the right search box).
The left search box is for keywords (javascript, viewbox, panel). In both cases, you only need
to enter enough info to be unique.

[peteconway]

Instead of telling us what you are doing - tell us the brief or design spec what fields, what session variables what do they do? If the table is the same you probably don't need any of that - how many records are you dealing with ? how is the Argument being set?
Pete

[gianfior85]

Thank you for your responses. You both are absolutely right that the dataset is not huge and I shouldn't worry about retrieving all the data then filtering it.

Pete, to answer your question, the table is indeed the same. A simplified/generic version of the queries in this case are something like:

if session.a = session.b then
select * from accounts where cycle >= session.currentcycle

else
select * from accounts where cycle >1

end if

There are no arguments, just session variables filtering the query.