http://www.intersoftsolutions.com/Community/WebGrid/PrepareDataBinding--Columns/http://www.intersoftsolutions.comenCopyright 2002 - 2015 Intersoft Solutions Corp. All rights reserved.60http://www.intersoftsolutions.com/Community/WebGrid/PrepareDataBinding--Columns/Sun, 13 Jun 2010 21:51:21 GMTGlayaar<p>Using the provided SaveRestoreLayout.aspx tutorial sample under V3.1 folder, I could save & restore the WebGrid layout and filter the data without any issue you mention. By default the sample does not allow filtering, however you could enable filtering by setting AllowFilter="Yes" under LayoutSettings. Have you tried using the technique in the tutorial sample?</p><p>If the method is not applicable, please provide us with a simple running sample so we could analyze the issue further. <br /></p>http://www.intersoftsolutions.com/Community/WebGrid/PrepareDataBinding--Columns/Fri, 11 Jun 2010 14:16:49 GMTbloveall<p>Our users are able to save their column preferences so that, if they select some columns on a particular page for removal, these preferences are saved so that when they return, they do not initially see those columns. </p> <p>Say, for instance, that I have a grid with three columns (FirstName, LastName, Nickname). A user comes along and selects "Nickname" for removal. This is saved. The user comes back and does a search, the results of which are displayed in a WebGrid. Initially, they do not see Nickname. If they do another search that results in data, they likewise do not see Nickname. So far so good. But the problem that I am experiencing is that if the result set is empty (e.DataSource is set to a DataTable that is "Nothing") and then the user does another search which has results, the "Nickname' column is showing up. So the problem arises in a grid where one search results in a data, a second search results in no data, and a third search results in data.</p> <p>The code that manages the columns is contained in "PrepareDataBinding" and the routine that I use to retrieve columns is called on the first search (on a post back) but not on subsequent searches. This typically works fine but not in the case above. Do you have an idea as to what might be causing this issue and what I can do about it? Do I have to call my routine to reload the columns after any empty result set?</p> <p>Thanks,</p> <p>Brad</p>