|
-
Jan 23rd, 2002, 09:03 AM
#1
Thread Starter
New Member
VBA(Word) problem Tab-key on Userforms
Dear all,
I created a wizzard in Word. On base of present documents in a specific folder (fso object) the templete (with custumized VBA code)places textboxes on the pre-defined userforms(1,2,3).
After this the wizzard automatically starts up and the userforms(1,2,3) are presented to the user to fill in the textboxes. But here comes the problem:
Sometimes the tab key have to be pushed more than 1 time to jump to the next tekstbox (control). It even happens that it looks like when a textbox is focussed, but when the user gives input, the cursor is moving from left to right (in the textbox) filling the textbox only with blanks.
Does anybody know how to solve this problem?
Kind regards,
Chris
-
Jan 23rd, 2002, 08:36 PM
#2
Watch me pull a text box and some characters out of my hat.
Tab Stops:
You may have controls, like Frames, that have tab stops. So, when you press tab, the frame takes focus and it looks like nothing has focus. Then another tab moves on to the next control in the tab order, which may be your text box. Set the TabStop property to False for any controls that you don't want to take focus when the user tabs. (Before you try arrow keys: On VBA forms the arrow keys seem to have a life of their own and don't always follow the tab order. I don't know why.)
Blanks:
Do you have a space in the PasswordChar property of the text box? It's easy to overlook because a space doesn't look like anything. Go to the PasswordChar property then press END then Delete and see if it deletes a space. Now trying runing the program again.
-
Jan 24th, 2002, 03:33 AM
#3
Thread Starter
New Member
I checked comments - tab-key still a problem
Workhorse,
Thanks for your reply!
TabKey:
For the controls created at design time on the Userform the TabStop property is set to False. So this must be correct.
The labels belonging to the textboxes are created at run-time like the textboxes. The TabStop property is after creation at run-time set to False default as far as I can check. Isn't it?
Blanks:
This problem only occurs in combination with the TabKey (focus) problem.
Because these problems occur frequent but the moments that the problems occur are not predictable I'm thinking about memory problems.
If anybody can think up something else please reply.
Kind regards,
Chris Jonkheer
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|