Hi Riendy,

Thanks for your reply. I found the documentation of the AllowAutoDataCaching property. From the documentation it does a caching of the DataSource object and is enabled per default. As all grids we use get refreshed with different data on every click, we might change this to False everywhere anyway.

But from the description it also says that the caching feature is not being used automatically and instead we should use IsDataCached property before querying for new data. We are not doing that, so I assume we don't use the caching feature anyway. Also, the description says the cached data is stored in the Session object and that is stored in SQL-Server session handler database, so it's not webserver specific.

I'm looking for some reason why the data is only on one server and not shared or not refreshed properly. So this property would not explain the problem.

Any other ideas? Any known bugs?

Regards,

Eric

Hi Handy,

Did you mean this event list?

1. WebGrid_PreInitialize
2. WebGrid_Initialize
3. Page_Load: Event loading of the current page
4. WebGrid_InitializeLayout: Layout initialization such as assigning static behavior, appearance and styles
5. WebGrid_InitializeDataSource: Data source initialization
6. WebGrid_PrepareDataBinding: Column structure retrieval and creation of necessary objects
7. WebGrid_Load: Indication of successfully preparation of data binding process and data populatingin all rows
8. <<ServerControl Events>> - if Page.IsPostBack: Execution of server control events such as Button1_Click
9. Page_PreRender
10. ...
11. WebGrid_Load
12. WebGrid_PreRender
13. ...
14. Page_SaveViewState
15. Page_Render
16. ...
17. WebGrid_InitializeTable
18. WebGrid_InitializeColumn
19. WebGrid_InitializeRow
20. WebGrid_InitializeCell
21. ...
22. WebGrid_Unload

Occurs after the Control object is loaded but prior to rendering.

Use this event to perform any updates before the server control is rendered to the page. Any changes in the view state of the server control can be saved during this event. Such changes made in the rendering phase will not be saved.

That's not really much information, as you write as well. So yes, please update the documentation (and put it to your homepage too).

Hi Handy,

I looked at your code again. You moved the column creations from .Init to .PrepareDataBinding and added a RootTable.Columns.Clear before the creation. You also moved the footer code from the Page.Load to the grdLower_PrepareDataBinding. But the main change is that in SetColumnVisibility you check if column D exists and if not you just create it.

This can't be your proposed solution, right? If you create the columns and then later when you use them, one column suddenly disappears, you just recreate it? And then you tell me this was a bug in my code and not in your product?

Please fix this bug instead of providing me non-working workarounds.

Thanks,

Eric

You know that you can never test on a production system. And reproducing this is also not possible right now as you know.

So the only thing we can do is to add some logging to find out more details (which might lead to a reproduction scenario or whatever). But you never told me what you need.

I understand that this bug is not very important for you, as this happens currently only for us and only randomly every few weeks and on an old server - together with your limited resources. But it is still a very drastic bug and might still exist on any newer server for any client you have.

So please let me know how to go on. If you don't want to fix it, please tell us this clearly too. Just letting us wait and telling things about reproduction is no option.

Ok, please update this thread when the bug is fixed or when you know when it will get fixed.