Rx_
Nothing In Moderation
- Local time
- Yesterday, 18:43
- Joined
- Oct 22, 2009
- Messages
- 2,803
Really enjoyed walking through your code!! Thanks!
After maintaining vba unbound controls for two years, the current assignment is to maintain some one elses code (or lack of it) with no validation at any level, leaving the records with lots of nulls. While I have been able to justify a few new buttons, the basic orders are to "keep it looking the same".
Well, your code example brought to mind something I had not though about.
And that is the Form Cycle property
My project uses All Records - that may explain some unintended events I have been experiencing from time to time.
EXAMPLE: use the Cycle property to specify what happens when you press the TAB key and the focus is in the last control on a bound form. Read/write Byte.
expression.Cycle
expression Required. An expression that returns one of the objects in the Applies To list. For the benefit of others:
The Cycle property uses the following settings.
SettingVBDescriptionAll Records0(Default) Pressing the TAB key from the last control on a form moves the focus to the first control in the tab order in the next record.Current Record1Pressing the TAB key from the last control on a record moves the focus to the first control in the tab order in the same record.Current Page2Pressing the TAB key from the last control on a page moves the focus back to the first control in the tab order on the page.
Note You can set the Cycle property by using the form's property sheet , a macro , or Visual Basic .
After maintaining vba unbound controls for two years, the current assignment is to maintain some one elses code (or lack of it) with no validation at any level, leaving the records with lots of nulls. While I have been able to justify a few new buttons, the basic orders are to "keep it looking the same".
Well, your code example brought to mind something I had not though about.
And that is the Form Cycle property
My project uses All Records - that may explain some unintended events I have been experiencing from time to time.
EXAMPLE: use the Cycle property to specify what happens when you press the TAB key and the focus is in the last control on a bound form. Read/write Byte.
expression.Cycle
expression Required. An expression that returns one of the objects in the Applies To list. For the benefit of others:
The Cycle property uses the following settings.
SettingVBDescriptionAll Records0(Default) Pressing the TAB key from the last control on a form moves the focus to the first control in the tab order in the next record.Current Record1Pressing the TAB key from the last control on a record moves the focus to the first control in the tab order in the same record.Current Page2Pressing the TAB key from the last control on a page moves the focus back to the first control in the tab order on the page.
Note You can set the Cycle property by using the form's property sheet , a macro , or Visual Basic .
)
