Prev: Printing a Report on a command button
Next: Passing the value of a Combobox to another field.
From: Peter Hallett on 22 Mar 2010 13:30
A form is displayed with the focus set to the first control requiring data
input, which is then solicited in sequence. The form works fine. However,
for a reason which is far from clear, some operators have been using the Page
Down key which then displays the next page. In most cases this is blank,
effectively clearing all the controls and leading the operator to conclude
that he has 'lost his data'. It can, of course, easily be retrieved by means
of the Page Up key, if this is pressed the same number of times as the Page
Down key but an easier way of dealing with this problem might simply be to
disable the Page Up and Page Down keys while the form is on display.
Unfortunately, however, the On Key Press event does not appear to do
anything. A break point inserted in the resulting Sub is never reached. Can
anyone suggest a solution?
From: Jeff Boyce on 22 Mar 2010 13:48
Peter

Open the form in design view. Check for the property setting for "Cycle".
If you set it to "Current Record", I believe the page-down/page-up doesn't
leave the current record.

Good luck!

Regards

Jeff Boyce
Microsoft Access MVP

--
Disclaimer: This author may have received products and services mentioned
in this post. Mention and/or description of a product or service herein
does not constitute endorsement thereof.

Any code or pseudocode included in this post is offered "as is", with no
guarantee as to suitability.

You can thank the FTC of the USA for making this disclaimer
possible/necessary.

"Peter Hallett" <PeterHallett(a)discussions.microsoft.com> wrote in message
news:9B36A16B-96A8-4EEE-AE5F-87D166E71452(a)microsoft.com...
>A form is displayed with the focus set to the first control requiring data
> input, which is then solicited in sequence. The form works fine.
> However,
> for a reason which is far from clear, some operators have been using the
> Page
> Down key which then displays the next page. In most cases this is blank,
> effectively clearing all the controls and leading the operator to conclude
> that he has 'lost his data'. It can, of course, easily be retrieved by
> means
> of the Page Up key, if this is pressed the same number of times as the
> Page
> Down key but an easier way of dealing with this problem might simply be to
> disable the Page Up and Page Down keys while the form is on display.
> Unfortunately, however, the On Key Press event does not appear to do
> anything. A break point inserted in the resulting Sub is never reached.
> Can
> anyone suggest a solution?


From: Rick Brandt on 22 Mar 2010 14:33
Jeff Boyce wrote:

> Peter
>
> Open the form in design view. Check for the property setting for "Cycle".
> If you set it to "Current Record", I believe the page-down/page-up doesn't
> leave the current record.

Cycle only affects usage of the Tab key, not the Page keys.
From: Jeff Boyce on 22 Mar 2010 19:47
Thanks, Rick. Clearly I've never been faced with that!

Regards

Jeff B.

"Rick Brandt" <rickbrandt2(a)hotmail.com> wrote in message
news:ho8un7$ahs$1(a)news.eternal-september.org...
> Jeff Boyce wrote:
>
>> Peter
>>
>> Open the form in design view. Check for the property setting for
>> "Cycle".
>> If you set it to "Current Record", I believe the page-down/page-up
>> doesn't
>> leave the current record.
>
> Cycle only affects usage of the Tab key, not the Page keys.


 | 
Pages: 1
Prev: Printing a Report on a command button
Next: Passing the value of a Combobox to another field.