This is another newbie question.  

Again, I am doing things backwards. My management wants me to build the
form, then IF they decide, we will bind to a database ... that has caused
lots of problems. This time, I am being driven crazy by "Choice groups,
sections, and radio buttons". Also, I have the constraint that upgrading to
2007 is NOT an option.

My form needs to have two, mutually exclusive radio buttons (e.g. "yes",
"no"). I read that to make the buttons mutually exclusive, I must put them in
a "choice section" which has to be in a "choice group", especially if I want
to bind to a database later.

I have several problems with this "choice" stuff:

- Size:  they want to print from the data entry view. By the time I get my
buttons, section, and group all nested, the vertical size taken by these
controls is huge and unacceptable.

- Binding and naming:  In the data source pane, I try to keep the controls,
groups, etc. with meaningful names and arranged in a logical, sequential
sequence. One, I cannot name the "choice sections". Two, heaven help me if I
ever lose the binding. It is hard to get them reassociated with the correct
groups. When I get done, I have all kind of warning "flags" on the form
telling me that something is bound incorrectly, duplicates data, or can't
hold data.

QUESTION:  Can anyone point me to some examples of practical ways to work
with the "choice" objects?  Sizing, naming, re-connecting if they get unbound?

Any help would be greatly appreciated!

Thanks,