NH> AM>   One of my dialog contains a lot of buttons.
NH> AM>   The ammount of buttons depend on data and is
NH> AM>   usually 100-200.
NH>   Even 50 buttons on a screen are far too many for most
NH>   users to handle properly.  You may want to reconsider the
NH>   type of objects you are using (ie:  a drop-down list box
NH>   containing 10 choices may be easier on the user than 10
NH>   push buttons).
   It sounds like a perfect place to use a hierarchy.
   In an MFC app, assuming that there are logical subsets
   to all these buttons, I would implement property sheets.
   This is similar to a menu with popups for each subgroup.
   If possible, breaking things down into easily managed
   groups would be preferable, usually. It's much simpler
   for the user to find what they want that way, assuming
   that there are reasonable titles for each subset. :)
> ] Let's try randomly accessing YOUR memory once...............
---
---------------