Views

Re: using a run query button on a secondary view

morphguy112 — Sat, 14 May 2011 03:41:49 GMT

What I did for my code is use a custom rules button with rules. Action 1 would be to run query, Action 2 would then be to switch to that view you are in. Works for me right now, hopefully this will help you out as well!!

Re: using a run query button on a secondary view

Hilary Stoupa — Tue, 07 Dec 2010 17:18:24 GMT

Worst case -- put all your views on your default view in separate sections. Then add a field to your data source (or use a secondary XML data source) simply to control which section is displayed. The buttons that switch between views simply set the field that the conditional formatting for the sections is based on. I use this a lot to get around the issue that we can't switch views and email in the same ruleset without sending a blank email.

Re: using a run query button on a secondary view

homeruk187 — Tue, 07 Dec 2010 12:57:42 GMT

There’s a woman were I work who was having similar problem and I found a possible solution from this site, basically it was something to do with how the data sources and views interact. I’m not sure if she got round to checking the link below but it did make sense when I read it.

http://www.infopathdev.com/forums/p/1094/3886.aspx

using a run query button on a secondary view

king treelo — Tue, 07 Dec 2010 09:31:24 GMT

Hi,

I currently have a form set up which uses 2 buttons on the main view to switch between views 'b' and 'c'.

On these 2 views i have a 'run query' button that takes a value from the same view, and brings info back from a DB.

The problem i am having is that when the 'run query' button is pressed, it automatically takes me back to my default view. Is there any way of keeping the view once the button is pressed so i can display the information or is this not possible using views?