A2K2 AllowAdditions

[Trev]

If I set AllowAdditions to false in A2K2, I can still add records in the
form, I expected to get a blank form if on a new record :-\

[Wayne Morgan]

I don't have 2002 loaded to test on. I just tried it in 2003 and was not
able to go to a new record if Allow Additions was No/False. I even tried
changing it in code while at a new record and the form moved back to the
last record and disabled the new record option.

--
Wayne Morgan
Microsoft Access MVP
"Trev@Work" <bouncer@localhost> wrote in message
news:3f*********************@news.easynet.co.uk...

If I set AllowAdditions to false in A2K2, I can still add records in the
form, I expected to get a blank form if on a new record :-\

[Trev]

"Wayne Morgan" <co***************************@hotmail.com> wrote in message
news:6g******************@newssvr31.news.prodigy.c om...

I don't have 2002 loaded to test on. I just tried it in 2003 and was not
able to go to a new record if Allow Additions was No/False. I even tried
changing it in code while at a new record and the form moved back to the
last record and disabled the new record option.

I just tried in another form and it's OK, just one particular form (of
course, the only one I want to disallow additions, have ATM disabled them by
cancelling BeforeInsert).

Strange.

[Wayne Morgan]

It may be a corrupted form or there may be something blocking the setting
from taking place. In the Immediate Window (Ctrl+G) type

?forms!NameOfForm.AllowAdditions

When you press Enter, it should return true or false to tell you what the
actual status of the setting is.

--
Wayne Morgan
Microsoft Access MVP
"Trev@Work" <bouncer@localhost> wrote in message
news:3f*********************@news.easynet.co.uk...

"Wayne Morgan" <co***************************@hotmail.com> wrote in message news:6g******************@newssvr31.news.prodigy.c om...

I don't have 2002 loaded to test on. I just tried it in 2003 and was not
able to go to a new record if Allow Additions was No/False. I even tried
changing it in code while at a new record and the form moved back to the
last record and disabled the new record option.
I just tried in another form and it's OK, just one particular form (of
course, the only one I want to disallow additions, have ATM disabled them

by cancelling BeforeInsert).

Strange.

[Trevor Best]

On Wed, 17 Dec 2003 15:21:46 GMT in comp.databases.ms-access, "Wayne
Morgan" <co***************************@hotmail.com> wrote:

It may be a corrupted form or there may be something blocking the setting
from taking place. In the Immediate Window (Ctrl+G) type

?forms!NameOfForm.AllowAdditions

When you press Enter, it should return true or false to tell you what the
actual status of the setting is.

Got it, thanks. It was working OK when attached to the client's data
but not to the development database. The property had in fact been set
to true by a generic security routine external to the form. Seems this
routine should take note of the settings prior to setting them. I'll
have to modify this routine to OR the setting with the original
setting or something.

--
A)bort, R)etry, I)nfluence with large hammer.

[Trevor Best]

Ha, nailed it this time. The property was set before the security code
had run (the security code only turned off the properties as
appropriate anyway)

docmd.OpenForm "form",,,,acFormEdit

Turns on the .AllowAdditions property.

Leaving it to default or using acFormPropertySettings it works as
expected.

Thanks for help again Wayne.

--
A)bort, R)etry, I)nfluence with large hammer.