data entry into control array of text boxes - help!

budgie · Joined: 04 Oct 2007 Posts: 40

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 entered data, together with KeyUp and KeyPress events for
handling movement from box to box.

Now that I'm faced with a control array, am I faced with having TWENTY LostFocus
event procedures per column to capture user input? I've gone totally blank on
this. If anyone really wants to see the form I'll post it somewhere.

Archived from group: microsoft>public>vb>dos

budgie · Joined: 04 Oct 2007 Posts: 40

On Mon, 21 Aug 2006 16:40:00 +0800, budgie wrote:

>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 entered data, together with KeyUp and KeyPress events for
>handling movement from box to box.
>
>Now that I'm faced with a control array, am I faced with having TWENTY LostFocus
>event procedures per column to capture user input? I've gone totally blank on
>this. If anyone really wants to see the form I'll post it somewhere.

Ah, OK, the penny has dropped on this one and life has returned to normal -
almost.

Can anyone see a reason for an "illegal function call" ERR05 in

frmPE3.txtRx(0).SETFOCUS

where the form name is "frmPE3" and "txtRx(0)" is the name of the first textbox
in a control array of 20 text boxes, indexes ranging from 0 to 19. This is
preventing a controlled focus when the form's textbox controls are cleared.

Nothing in the error description/explanation fits this circumstance. I would
appreciate any constructive suggestions.

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

budgie wrote:
> On Mon, 21 Aug 2006 16:40:00 +0800, budgie wrote:
>
>> 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 entered data, together with KeyUp and KeyPress events for
>> handling movement from box to box.
>>
>> Now that I'm faced with a control array, am I faced with having TWENTY LostFocus
>> event procedures per column to capture user input? I've gone totally blank on
>> this. If anyone really wants to see the form I'll post it somewhere.
>
>
> Ah, OK, the penny has dropped on this one and life has returned to normal -
> almost.
>
> Can anyone see a reason for an "illegal function call" ERR05 in
>
> frmPE3.txtRx(0).SETFOCUS

When?

>
> where the form name is "frmPE3" and "txtRx(0)" is the name of the first textbox
> in a control array of 20 text boxes, indexes ranging from 0 to 19. This is
> preventing a controlled focus when the form's textbox controls are cleared.
>
> Nothing in the error description/explanation fits this circumstance. I would
> appreciate any constructive suggestions.

that doesn't seem to be the same error we usually see, but you can't
setfocus to a control unless the form is FULLY loaded and visible.

Bob
--

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

Bob O`Bob wrote:
> that doesn't seem to be the same error we usually see, but you can't
> setfocus to a control unless the form is FULLY loaded and visible.

Whoops! I just realized which group this is.
Perhaps it's just as true in VBDOS, but I can't be as certain.
It's probably worth looking into anyway.

Bob
--

budgie · Joined: 04 Oct 2007 Posts: 40

On Fri, 25 Aug 2006 16:57:21 -0700, Bob O`Bob wrote:

>Bob O`Bob wrote:
>> that doesn't seem to be the same error we usually see, but you can't
>> setfocus to a control unless the form is FULLY loaded and visible.
>
>Whoops! I just realized which group this is.
>Perhaps it's just as true in VBDOS, but I can't be as certain.
>It's probably worth looking into anyway.

It certainly appears to be the same. I had the SHOW statement *following* the
cleanup and preparation. When I moved the SHOW to before the SETFOCUS, the
problem disappeared.

Tnx for the heads-up.