Thank you for your answer. :rose: I read that and if I understand well, I shall begin a CScrollBar child class from scratch... X| I think I will handle it in another way.... :) I actually began in this way : A <--- This a button to scroll up | <--- This a background bmp | [] <--- This a button (the box showing the current position in every scrollbar) | <--- This the same background bmp V <--- This another button to scroll down It's a bit messy but I've already done that for a slider, and that works well, so why not ?... ;) My only problem is to get rid of those f*#@^" srollbars inside the CListCtrl (disabling them by checking the 'No scroll' check box won't help : I won't be able to send some WM_VSCROLL to the CListCtrl...) :( If anyone has any idea... :)

Here a little quotation of MSDN doc about CWnd::SetWindowPos, the function I'm using (here you've got the description of the first parameter) pWndInsertAfter    Identifies the CWnd object that will precede this CWnd object in the Z-order. This parameter can be a pointer to a CWnd or a Pointer to one of the following values: wndBottom   Places the window at the bottom of the Z-order. If this CWnd is a topmost window, the window loses its topmost status; the system places the window at the bottom of all other windows. wndTop   Places the window at the top of the Z-order. wndTopMost   Places the window above all nontopmost windows. The window maintains its topmost position even when it is deactivated. wndNoTopMost   Repositions the window to the top of all nontopmost windows (that is, behind all topmost windows). This flag has no effect if the window is already a nontopmost window. As you can see I'm actually using the predefined variable. I tried with other variable such as the Picture controls that should be under others : It works well (for example I used : upper.SetWindowPos(lower,...) where upper and lower are 2 Picture controls). But what is wrong is when I use this class : CxSkinButton. This class is a marvelous Button which can have any shape and any bitmap over. It reacts to the mouse over event and change bitmap when it occurs. So what's interesting here, is that the buttons are hidden behind a bitmap that should normally be shown behind them at the beginning. And when I go over where they should appear with the mouse, then they appear with the 'MouseOver' bitmap. After I leave the sensitive zone, the button remains visible with proper bitmap and is working as it should work. So, actually my problem is that when I start the application, I must move the mouse over each button so that it can appear => :(( I hope I've explain not so bad because it's a bit confusing... Thank you in advance. Joel .:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:..:.:.:.:.:.:.:.:..:.:.:.:.:.:.:.:.:. Should computing stay as a source of benefit or become like knowledge : free and opened to every one ?... ;) ':':':':':':':':':':':':':':':':':':':':':':':':':':':':':':':':':':':':':':':':':':'