Thanks for the reply. Yes I did look at 4dialog which _appears_ to use the DialogBox function to create a dialog which is killed by destroywindow, suggesting the dialog is modeless.
The docs say DialogBox is modal, hence my question. How does the DialogBox function know we want the dialog to be modeless?
Also, this has no GETs, which I will want in my m'less dlgs
take a closer look at the dialog(...) statement and you will notice that the <hWndParent> argument has been intentionally left empty. this is the trick. seems ugly but a quick way to switch your dlg from modal to modeless. another big advantage with this technic is you can keep on using your favorite @ dialog .... id ... get ... picture i.e. no need to subclass edit-controls and develop on your own custom maskedit procedures. see attached & good luck for your migration.
Thanks for the program. I have tried it and added 2 messageboxes which indicate that the dialog is modal. I can only see the second message after clearing the dialog