Allow additions=no (sometimes)

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have a form (RFI Resolutions) that I want to open with "Allow Additions"
off, so when the user scrolls through, he cannot scroll to a "new record".
Works great when I open the form on its own. But when I open it from another
form, using a button and a macro to do so, the new record button (the with
the * on it) is enabled even though the property still says no.

What am I missing?

Thanks
 
paulpenta said:
I have a form (RFI Resolutions) that I want to open with "Allow
Additions" off, so when the user scrolls through, he cannot scroll to
a "new record". Works great when I open the form on its own. But when
I open it from another form, using a button and a macro to do so, the
new record button (the with the * on it) is enabled even though the
property still says no.

What am I missing?

What parameters are you specifying for the OpenForm action in the macro?
If you specify "Edit", you'll override the form's settings and open it
in full edit mode. If you leave the argument blank, the form's settings
should rule.
 
I have a form (RFI Resolutions) that I want to open with "Allow Additions"
off, so when the user scrolls through, he cannot scroll to a "new record".
Works great when I open the form on its own. But when I open it from another
form, using a button and a macro to do so, the new record button (the with
the * on it) is enabled even though the property still says no.

What am I missing?

Thanks

You left out the most important part.
What does your macro actually do (or say).

Having already set the form [RFI Resolutions] AllowAdditions property
to No, the following Macro works for me:

Form Name RFI Resolutions
View Form
Window view Normal
 
PERFECT!

Thanks, Dick

Dirk Goldgar said:
What parameters are you specifying for the OpenForm action in the macro?
If you specify "Edit", you'll override the form's settings and open it
in full edit mode. If you leave the argument blank, the form's settings
should rule.

--
Dirk Goldgar, MS Access MVP
www.datagnostics.com

(please reply to the newsgroup)
 
Back
Top