Problems with option button control arrays

budgie · Joined: 04 Oct 2007 Posts: 40

I have used control arrays of option buttons without problems to date, but
always placed within their own frame. Right now I have a series of Yes/No
questions and I had it all working fine in separate frames, but that commits
four screen lines per Q&A. The best use of space on the form seemed to be
questions as labels with a pair of option buttons on the same line for the Y/N
user selection.

So I set up the questions as labels in a frame. I then assigned pairs of option
buttons as control arrays. But VBDOS is treating ALL these OB's as part of one
super-control-array.

The setup is correct. Each pair has the same control name, and indexes 0 and 1
assigned by VBDOS as it asks(for each pair) if I want to set up a control array.

The layout is:

Q1? Option1-Index0 Option1-Index1
Q2? Option2-Index0 Option2-Index1
Q3? Option3-Index0 Option3-Index1
etc

I also repeated this exercise without a frame, in case that was causing to VBDOS
to see it all as one big array. Same outcome.

Am I destined to only get the result I require by individually framing each Q&A?

Archived from group: microsoft>public>vb>dos

Bob O`Bob · Joined: 04 Oct 2007 Posts: 1456

budgie wrote:
> I have used control arrays of option buttons without problems to date, but
> always placed within their own frame. Right now I have a series of Yes/No
> questions and I had it all working fine in separate frames, but that commits
> four screen lines per Q&A. The best use of space on the form seemed to be
> questions as labels with a pair of option buttons on the same line for the Y/N
> user selection.
>
> So I set up the questions as labels in a frame. I then assigned pairs of option
> buttons as control arrays. But VBDOS is treating ALL these OB's as part of one
> super-control-array.
>
> The setup is correct. Each pair has the same control name, and indexes 0 and 1
> assigned by VBDOS as it asks(for each pair) if I want to set up a control array.
>
> The layout is:
>
> Q1? Option1-Index0 Option1-Index1
> Q2? Option2-Index0 Option2-Index1
> Q3? Option3-Index0 Option3-Index1
> etc
>
> I also repeated this exercise without a frame, in case that was causing to VBDOS
> to see it all as one big array. Same outcome.
>
> Am I destined to only get the result I require by individually framing each Q&A?

Yes.

Option buttons are mutually exclusive with all other option buttons
**within the same container**

That is the ONLY way it works.

It has /absolutely nothing/ to do with control arrays.

Bob
--

budgie · Joined: 04 Oct 2007 Posts: 40

On Wed, 03 May 2006 11:19:02 -0700, Bob O`Bob wrote:

>budgie wrote:
>> I have used control arrays of option buttons without problems to date, but
>> always placed within their own frame. Right now I have a series of Yes/No
>> questions and I had it all working fine in separate frames, but that commits
>> four screen lines per Q&A. The best use of space on the form seemed to be
>> questions as labels with a pair of option buttons on the same line for the Y/N
>> user selection.
>>
>> So I set up the questions as labels in a frame. I then assigned pairs of option
>> buttons as control arrays. But VBDOS is treating ALL these OB's as part of one
>> super-control-array.
>>
>> The setup is correct. Each pair has the same control name, and indexes 0 and 1
>> assigned by VBDOS as it asks(for each pair) if I want to set up a control array.
>>
>> The layout is:
>>
>> Q1? Option1-Index0 Option1-Index1
>> Q2? Option2-Index0 Option2-Index1
>> Q3? Option3-Index0 Option3-Index1
>> etc
>>
>> I also repeated this exercise without a frame, in case that was causing to VBDOS
>> to see it all as one big array. Same outcome.
>>
>> Am I destined to only get the result I require by individually framing each Q&A?
>
>Yes.
>
>Option buttons are mutually exclusive with all other option buttons
>**within the same container**

Aaahhh! And I guess that, in the absence of an "explicit" container, the form
is the container.

>That is the ONLY way it works.
>
>It has /absolutely nothing/ to do with control arrays.

Thanks for that very succinct explanation. Back to individual containers it is
then Sad

budgie · Joined: 04 Oct 2007 Posts: 40

On Thu, 04 May 2006 08:21:28 +0800, budgie wrote:

>On Wed, 03 May 2006 11:19:02 -0700, Bob O`Bob wrote:
>
>>budgie wrote:
>>> I have used control arrays of option buttons without problems to date, but
>>> always placed within their own frame. Right now I have a series of Yes/No
>>> questions and I had it all working fine in separate frames, but that commits
>>> four screen lines per Q&A. The best use of space on the form seemed to be
>>> questions as labels with a pair of option buttons on the same line for the Y/N
>>> user selection.
>>>
>>> So I set up the questions as labels in a frame. I then assigned pairs of option
>>> buttons as control arrays. But VBDOS is treating ALL these OB's as part of one
>>> super-control-array.
>>>
>>> The setup is correct. Each pair has the same control name, and indexes 0 and 1
>>> assigned by VBDOS as it asks(for each pair) if I want to set up a control array.
>>>
>>> The layout is:
>>>
>>> Q1? Option1-Index0 Option1-Index1
>>> Q2? Option2-Index0 Option2-Index1
>>> Q3? Option3-Index0 Option3-Index1
>>> etc
>>>
>>> I also repeated this exercise without a frame, in case that was causing to VBDOS
>>> to see it all as one big array. Same outcome.
>>>
>>> Am I destined to only get the result I require by individually framing each Q&A?
>>
>>Yes.
>>
>>Option buttons are mutually exclusive with all other option buttons
>>**within the same container**
>
>Aaahhh! And I guess that, in the absence of an "explicit" container, the form
>is the container.
>
>>That is the ONLY way it works.
>>
>>It has /absolutely nothing/ to do with control arrays.
>
>Thanks for that very succinct explanation. Back to individual containers it is
>then Sad

Follow-up ....

Using individual frames, I am now forced into two pages to solicit responses
from the user. (I probably would have anyway without frames, but now it's
certain). This form(pair) is reached via an OptionButton menu on an earlier
form. ratehr thanexpand that menu further for the second page, I have a command
button on each page "Next Page" or "Previous Page" as the case may be.

When I toggle back and forth about eight times between the forms (in the IDE) I
get a stack overflow. I was doing a Hide and Show between the forms, and
attributed the problem initially to the stack storing "returns". Changing the
Hide to Unload didn't change things.

Is this going to be a problem that will force me to not allow toggling between
these two pages of selections?

Tnx again for any advice.

John Kane · Joined: 04 Oct 2007 Posts: 9

In article , me@privacy.net
says...
> I have used control arrays of option buttons without problems to date, but
> always placed within their own frame. Right now I have a series of Yes/No
> questions and I had it all working fine in separate frames, but that commits
> four screen lines per Q&A. The best use of space on the form seemed to be
> questions as labels with a pair of option buttons on the same line for the Y/N
> user selection.
>
> So I set up the questions as labels in a frame. I then assigned pairs of option
> buttons as control arrays. But VBDOS is treating ALL these OB's as part of one
> super-control-array.
>
> The setup is correct. Each pair has the same control name, and indexes 0 and 1
> assigned by VBDOS as it asks(for each pair) if I want to set up a control array.
>
> The layout is:
>
> Q1? Option1-Index0 Option1-Index1
> Q2? Option2-Index0 Option2-Index1
> Q3? Option3-Index0 Option3-Index1
> etc
>
> I also repeated this exercise without a frame, in case that was causing to VBDOS
> to see it all as one big array. Same outcome.
>
> Am I destined to only get the result I require by individually framing each Q&A?
>

You could use Picture Boxes as the containers, and make the BorderStyle
0-None. This won't take up any more screen space than the labels and
option buttons.

--
Regards, John
news@johnkane.clara.co.uk

budgie · Joined: 04 Oct 2007 Posts: 40

On Thu, 4 May 2006 16:14:43 +0100, John Kane wrote:

>In article , me@privacy.net
>says...
>> I have used control arrays of option buttons without problems to date, but
>> always placed within their own frame. Right now I have a series of Yes/No
>> questions and I had it all working fine in separate frames, but that commits
>> four screen lines per Q&A. The best use of space on the form seemed to be
>> questions as labels with a pair of option buttons on the same line for the Y/N
>> user selection.
>>
>> So I set up the questions as labels in a frame. I then assigned pairs of option
>> buttons as control arrays. But VBDOS is treating ALL these OB's as part of one
>> super-control-array.
>>
>> The setup is correct. Each pair has the same control name, and indexes 0 and 1
>> assigned by VBDOS as it asks(for each pair) if I want to set up a control array.
>>
>> The layout is:
>>
>> Q1? Option1-Index0 Option1-Index1
>> Q2? Option2-Index0 Option2-Index1
>> Q3? Option3-Index0 Option3-Index1
>> etc
>>
>> I also repeated this exercise without a frame, in case that was causing to VBDOS
>> to see it all as one big array. Same outcome.
>>
>> Am I destined to only get the result I require by individually framing each Q&A?
>>
>
>You could use Picture Boxes as the containers, and make the BorderStyle
>0-None. This won't take up any more screen space than the labels and
>option buttons.

Dang! I've just restructured everything on those forms to take frames!

I just tried that suggestion and it works (I'm sure you knew that), so I may
revisit those forms. Many thanks. I'm learning a lot from the helpful gurus
here.

Compiler problems - (the saga continues). Yes, unfortunately I'm back ... This olde QB45 app is now 3/4's converted to VBDOS, and runs fine in the IDE. But when I attempt compilation, it faults. If I try in the DOS box (under 98SE) it exits with a Windows error message "tried to execute an inval

New problem - interaction between control arrays (long) One day, this will all be behind me and I'll look back ruefully at the hours that I wasted on this b####y project ...... I have a form with four seperate control arrays of option buttons. The form is used to (a) enable user configuration selection; (b) d

Problems running EXE on WXP/W2K I have a program developed in VBDOS. When I run from the MSDOS window, does not do anything, just gives the cursor back, without error message. I configure the AUTOEXEC.NT and CONFIG.NT and I could execute it in full screen is only. If I execute the progr

Problems on 32-bit Vista I'm having a couple of problems running my compiled VB-DOS programs on Vista.. 1. Full-Screen mode is not allowed. I can perhaps live with this, but more 2. I'm getting this message as soon as I try to run a program... NTVDM.EXE has stopped

data entry into control array of text boxes - help! I have a form with five columns, each being a control array of 20 text boxes. These are (to be) used for display of data for editing as required by the user. To receive and process user input in a non-CA text box scenario I use LostFocus to recover/check