I have a form which has a Go To New Record action on open event.

The form is based on a table so as the form is opened it goes to a new
record as expected. The form is set to cycle on current record only but if
you use the mouse wheel it is still possible to cycle to earlier records in
the table.

Is there a way to prevent this and stay on the new record?

Also - if someone starts to fill in some data for this new record but then
decides to cancel is there a neat way to stop any data being saved rather
than putting lots of code into the Close Form event.

Thanks for any suggestions.

Check out Stephen Lebans MouseHook at

http://www.lebans.com/mousewheelonoff.htm

With it you can disable the scroll.
--
Hope this helps,

Daniel Pineault
http://www.cardaconsultants.com/
For Access Tips and Examples: http://www.devhut.net
Please rate this post using the vote buttons if it was helpful.



"Andy" wrote:

> I have a form which has a Go To New Record action on open event.
>
> The form is based on a table so as the form is opened it goes to a new
> record as expected. The form is set to cycle on current record only but if
> you use the mouse wheel it is still possible to cycle to earlier records in
> the table.
>
> Is there a way to prevent this and stay on the new record?
>
> Also - if someone starts to fill in some data for this new record but then
> decides to cancel is there a neat way to stop any data being saved rather
> than putting lots of code into the Close Form event.
>
> Thanks for any suggestions.

Does opening the form in DataEntry mode work? Set the form's Data Entry
property to Yes, or if you open the form programmatically use this kind of
thing:
DoCmd.OpenForm "Form1", DataMode:=acFormAdd

For the last part of your question, use the BeforeUpdate event of the form
to perform any checks you wish. You can cancel the event if you are not
happy.

Form_Close is too late (i.e. the record has already been saved at that
time.)

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Andy" <(E-Mail Removed)> wrote in message
news:88A8F3CC-A8A7-41A9-8843-(E-Mail Removed)...
>I have a form which has a Go To New Record action on open event.
>
> The form is based on a table so as the form is opened it goes to a new
> record as expected. The form is set to cycle on current record only but if
> you use the mouse wheel it is still possible to cycle to earlier records
> in
> the table.
>
> Is there a way to prevent this and stay on the new record?
>
> Also - if someone starts to fill in some data for this new record but then
> decides to cancel is there a neat way to stop any data being saved rather
> than putting lots of code into the Close Form event.
>
> Thanks for any suggestions.

Thanks - Excellent.

"Allen Browne" wrote:

> Does opening the form in DataEntry mode work? Set the form's Data Entry
> property to Yes, or if you open the form programmatically use this kind of
> thing:
> DoCmd.OpenForm "Form1", DataMode:=acFormAdd
>
> For the last part of your question, use the BeforeUpdate event of the form
> to perform any checks you wish. You can cancel the event if you are not
> happy.
>
> Form_Close is too late (i.e. the record has already been saved at that
> time.)
>
> --
> Allen Browne - Microsoft MVP. Perth, Western Australia
> Tips for Access users - http://allenbrowne.com/tips.html
> Reply to group, rather than allenbrowne at mvps dot org.
>
> "Andy" <(E-Mail Removed)> wrote in message
> news:88A8F3CC-A8A7-41A9-8843-(E-Mail Removed)...
> >I have a form which has a Go To New Record action on open event.
> >
> > The form is based on a table so as the form is opened it goes to a new
> > record as expected. The form is set to cycle on current record only but if
> > you use the mouse wheel it is still possible to cycle to earlier records
> > in
> > the table.
> >
> > Is there a way to prevent this and stay on the new record?
> >
> > Also - if someone starts to fill in some data for this new record but then
> > decides to cancel is there a neat way to stop any data being saved rather
> > than putting lots of code into the Close Form event.
> >
> > Thanks for any suggestions.
>
>