To be honest - i think that there are two different approaches to flagging a button as being the default button ... one approach is mutually exclusive with the cancel button and the other is not.

I implemented the only approach I knew of (at the time) which is the mutually exclusive one. Now that I'm aware of an alternate approach - think we can implement a dual button in an upcoming release.

Specifically, every control has what is called an CONTROLID and there are a couple of well-known ID's ... ID_OK and ID_CANCEL are two of them. The approach kixforms uses is to set the button as either ID_OK or ID_CANCEL depending. But its not possible to set a button to both. The other approach circumvents the ID to identify the DEFAULT button - so now a button may be both - but I have yet to actually code and try it out.