Hello,

The first time i showed the progress on the project to my boss, he said: "hey!, i don't like paging! couldn't you put a scroll on it??". I've tried to convice him that paging is the natural way to work with the Datagrid control, but no luck. He is too used to work with win-form based applications...

So then i started to search for a method for adding scrolling capability to the Datagrid. The common method is to wrap it with a DIV tag, and then fix the header with CSS/Javascript. Easy. My boss was very happy when he saw it in action.

So then, what's the problem? basically the problem is that the control works very slow. I don't know why (i have to investigate it deeply). The users have the feeling of a heavy and slow application, when only one Datagrid is being shown, with perhaps no more than 60 rows and 8 columns.

Well, firstly i thought that the HTML output size could be very large. Indeed it was not such large. Then I optimized some aspects of my framework, like persisting the viewstate server-side (no more outputing to the client), avoiding obstructive javascript, etc. Obviously, the application performance was slightly improved, but that was not the problem at all.

I decided to re-code some server-side functions as client-side functions, in javascript. The HTML output size decreased again a bit. But still no luck. It is slow, but why? and where?.

I'm start thinking that the problem relies on the browser (IE). Is it slow rendering?. The performance is slightly better with Firefox (let's say that my HTML is not right formated at this time).

I don't know if it exists a solution, or simply i need to convice my boss for going back to the paging mechanism. 

Hope you can help me with some comments...
Thank you very much for your time in advance,
",1] ); D(["mb","Sergio.\n\n",0] ); D(["ce"]); //-->

Sergio.