Are you using the ES_WANTRETURN style? A rich person is not the one who has the most, but the one that needs the least.

Did you ::InitCommonControlsEx ? Also try to fire up a spy++ to see if those controls were created and if there were, what is there position. Edward

a dialog bar acting as a property sheet, sorry.

You should pick Bitmap Type in Picture properties. Hello World!

It is nothing to do with your configuration. It very likely cause by your code. The reason it won't crash in debug mode is that your linker allocates more storage space for each memory blocks in your program for debug purposes. So, even if your program leaks, the extra space storage save you from crash. This is not going to happen when you are in release mode as when your linker allocate exact storage space for your program. Sonork 100.41263:Anthony_Yio

Problem solved! Thanks :)

Fred. Seriously, what are you trying to do ? Christian I have drunk the cool-aid and found it wan and bitter. - Chris Maunder

Actually, I think the dialog is shown after OnInitDialog() completes. But the point is well taken. /ravi Let's put "civil" back in "civilization" Home | Articles | Freeware | Music ravib@ravib.com

You can also take a look here in CP at the Button articles in order to find out some classes already done... CButton ST is a good class... HTH...

The unusual thing that you are doing, is not actually initializing the dialog -- that is creating it each time. So the 'normal' stuff that MFC does to transfer data from CString's <--> CEdit's is not getting done. I don't know the answer, but it has something to do with the DoDataExchange stuff that get's done when WM_INITDIALOG is handled. A possible hack would be to send your dialog the WM_INITDIALOG message??? (HACK ALERT!) Just a thought... ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Peter Weyzen Staff Engineer Santa Cruz Networks