Hello,
We have an odd behavior occurring with one of our web products using the UltraWebGrid 2011.1. We're running the latest patch set. Our product is compiled using .net 3.5. It is installed and running in a large number of client locations.
If the data contains 1000 rows or less, we use the XML Load on Demand value of Background. Infragistics.WebUI.UltraWebGrid.XmlLoadOnDemandType=Background. The number of rows brought back on each post back is also a configurable value to allow the users to customize their preferred performance behavior.
This works fine in ALL of our client installations except one. An existing client recently migrated to a new server. The server is 2008 R2 running IIS 7.
On this new client server, on SOME pages, the Background postback only posts back 3 times, then stops. The number of rows that are returned is ALWAYS 3 times the configured paging size. What is strange is that this only happens on a few datasets, not all of them. I've scoured the datasets looking for characters that might be mucking up the javascript and found none.
I'm concerned that the behavior has to do with the new server, since it has not been an issue anywhere else. We have recently reinstalled both IIS and the .net 3.5 framework on the server. As anyone experienced anything like this before? Have any suggestions as to where to look? I there any reason that the javascript would stop posting back after three repetitions?
That's great, I am happy you have resolved the issue. Let me know if you need any additional help.
Thanks,
Angel
This issue appeared in IE and Firefox.
After a LOT of testing and review, I finally found the source of this problem. Turns out that within the data that that was stored in the database table that we were showing was the ASCII character 20. This is an odd value known as Device Control 4. We don't know how the data was stored, but I modified our stored proc that provides the data to ensure that ASCII characters 0 - 31 are NOT present in the data sent to the grid. We also strip out any < and /> characters as they also tend to screw up the javascript in the grid.
hi,
could you try using a different browser to try to reproduce this behavior? Are you getting any javascript (client-side) or server-side errors ? Thanks,