Kevin,

How much weight does this guy pull with your development? I hope not enough to persuade the powers that be that you're not doing it right. (And I hope he isn't anyone I know! <g>)

BTW, I *still* don't see how you can DataBind a listview or any other object to data that remains on the server side. You still have to get to that data at some point. Why not get it and keep it in a DataSet on the client-side?!?! How can it even remain on the server-side? I guess I'm missing something somewhere ....

~~Bonnie



>Bonnie...
>
>Thanks...I just wanted to make sure I was being clear. I'm glad to hear someone else is doing the same general thing we are.
>
>The other person is coming from a COM environment, and believes that data should not be brought down from the middle-tier to the client end, period. He believes that grids, picklists, etc. should be 'read' from the middle-tier, without actually pulling down the data. This doesn't seem to make much sense to me. I pointed out that while there is obviously a brief hit when someone does a query (out app involves a great deal of data retrieval and data review), it's much better than assoicating a grid with a data source that's behind the web service. I also mentioned that if someone is editing a row, and then the connection to the web service dies, the changes may be lost. However, if the user is doing a 'local' edit prior to doing a save, you can set up retrys if the initial save fails, without losing any data.
>
>Thanks again,
>Kevin