Thanks Nick for your msg about Wincreatedlg, on 13 11-13-1994

NK> dialog box is not actually a working "window" until 
NK> sometime just before the WM_INITDLG message is called 
NK> within your dBoxDlgProc.  This is where you need to do your 
NK> field queries and text setting.
NK> 
NK> You're trying to query a window handle and set its text 
NK> before it's accepting messages.  Its message loop doesn't 
NK> start until WinProcessDlg is called.
NK> 
NK> I still do this kind of thing regularly (try to manipulate 
NK> a window before it's really a window :).  That's one of the 
NK> first things I check my own code for!
NK> 

Actually that is not true. When WinLoadDialog() comes back, it
has already completed the WM_INITDLG message (which is really just
an echo of WM_CREATE that the underlying frame window got. So
(assuming that dialog was correctly created), the window handle
will be value. The thing that you have to watch out for is this:


HWND       hwndMyWin;

{
    case WM_CREATE        :
    //
    // Doing something here with hwndMyWin is wrong, because the call
to     // WinCreateWindow() below will not return until WM_CREATE is
done.     //

}

hwndMyWin = WinCreateWindow(....);


But once the WM_CREATE (or WM_INITDLG) completes, control returns
to the caller of WinCreateWindow() or WinLoadDialog() with the
handle.

___
 X KWQ/2 1.2b X "640K ought to be enough for anybody." - Bill Gates, 1981

--- Maximus/2 2.02