Jump to content


Photo

Generic Client-Side Sort Support for NextDBGrid


  • Please log in to reply
3 replies to this topic

#1 ozmosys

ozmosys
  • Members
  • 19 posts
  • Location:Melbourne, Australia

Posted 23 January 2006 - 04:22 PM

Hi Boki,

Your components are great biggrin.gif , but one thing that is always a stumbling block for me is the lack of generic client-side sorting on the NextDBGrid. I do not want to have to reissue a query every time the user clicks the header (this is a huge performance drain in Client/Server and n-tier systems).

Best regards

Steve

#2 ozmosys

ozmosys
  • Members
  • 19 posts
  • Location:Melbourne, Australia

Posted 27 January 2006 - 05:02 AM

Hi Boki,

Any chance of a comment? :wink:

This question is quite important to me! I could use DevExpress grids (which do everything I need and more), but they add an enormous amount of related code to .EXE! I would love a lighter option, and your Grids are the closest I have found so far ... but client side sorting is one *major* thing missing.

Best regards

Steve

#3 Boki (Berg)

Boki (Berg)

    Boki (Berg)

  • Forum Admin
  • PipPipPipPipPip
  • 8,195 posts
  • Gender:Male

Posted 27 January 2006 - 01:27 PM

Hello Steve,

I will add Sorting non-read-only DataSets very soon, but in that case DataSet need to be transfered in total size trough network and then sorted.

If you have some other idea, I am open to hear it !

regards
boki@bergsoft.net | LinkedIn Profile
--
BergSoft Home Page: www.bergsoft.net
Users Section: users.bergsoft.net
Articles and Tutorials: help.bergsoft.net (Developers Network)
--
BergSoft Facebook page
--
Send us applications made with our components and we will submit them on: www.bergsoft.net/apps.htm. Link to this page will be also set on home page too.

#4 ozmosys

ozmosys
  • Members
  • 19 posts
  • Location:Melbourne, Australia

Posted 27 January 2006 - 02:16 PM

Hi Boki,

Thanks for the reply.

> but in that case DataSet need to be transfered in total size
> trough network and then sorted.

My general approach is to only return the columns needed in the list, therefore your suggested method would be fine. Having the capability to decide whether to use client-side sorting, or sort via refreshing the dataset would be the best of both worlds.

Best regards

Steve




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users