I changed over to "CALCULATE MIN(BegStamp), MAX(EndStamp) FOR selected TO..." instead of the "SELECT Min(BegStamp), MAX(EndStamp) FROM Inputs WHERE selected..." All my unexpected response problems went away. My tentative conclusion: the SELECT does something that messes with the way the table gets updated from the grid.
I now have a filter working with the grid as well. It turns out I was able to setup a single filter that allows all records that meet the datetime range stored in the form variables. My initial plan was to change the filter on the fly but when I had some initial problems with that approach I realized that the logic can all be in the filter. Thanks again everyone, Joe On Thu, Jun 5, 2014 at 4:51 AM, Alan Bourke <alanpbou...@fastmail.fm> wrote: > > > On Wed, Jun 4, 2014, at 11:25 PM, Richard Kaye wrote: > > Over > > the years, when I've had the need to do really fun stuff with grids, I've > > ended up writing methods to set the datasource and rebuild the grid in > > code. > > This. It really is easier and more flexible in the long run IMO. > [excessive quoting removed by server] _______________________________________________ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/CABQeDnV75XRVXuZD9q=vxYeHLHzRm1LFkN_r4ryiqRJTRO2=j...@mail.gmail.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
