What am I missing? I have a single form view. I have set the "allow
deletions" property to NO. But when I open the form, it allows deletions.
What could be hiding in there???

When I open the form from the db container, it does not allow deletes. When I
open the form with a macro that simply runs the open form command, it opens
and allows deletes. Aargh!

"slickdock" wrote:

> What am I missing? I have a single form view. I have set the "allow
> deletions" property to NO. But when I open the form, it allows deletions.
> What could be hiding in there???

I am not very familiar with macros but im pretty sure you can specify how you
want the form to open
Check the open form arguements in the macro.. or add some to the macro

Barry

"slickdock" wrote:

> When I open the form from the db container, it does not allow deletes. When I
> open the form with a macro that simply runs the open form command, it opens
> and allows deletes. Aargh!
>
> "slickdock" wrote:
>
> > What am I missing? I have a single form view. I have set the "allow
> > deletions" property to NO. But when I open the form, it allows deletions.
> > What could be hiding in there???

I already checked that out before posting to this board. There is no macro
condition for opening with Delete set to No. I was hoping for some macro
condition along the lines of SetValue of the active form to NoDelete, but
can't find any google help on that...

"Barry A&P" wrote:

> I am not very familiar with macros but im pretty sure you can specify how you
> want the form to open
> Check the open form arguements in the macro.. or add some to the macro
>
> Barry
>
> "slickdock" wrote:
>
> > When I open the form from the db container, it does not allow deletes. When I
> > open the form with a macro that simply runs the open form command, it opens
> > and allows deletes. Aargh!
> >
> > "slickdock" wrote:
> >
> > > What am I missing? I have a single form view. I have set the "allow
> > > deletions" property to NO. But when I open the form, it allows deletions.
> > > What could be hiding in there???

"slickdock" <(E-Mail Removed)> wrote in message
news:53E28DFA-818B-485B-8EF9-(E-Mail Removed)...
> When I open the form from the db container, it does not allow deletes.
> When I
> open the form with a macro that simply runs the open form command, it
> opens
> and allows deletes. Aargh!

What *exactly* does your macro say, in terms of actions and arguments? And
what version of Access? Using Access 2003, if I have a form with Allow
Deletions set to no, and I run a macro that just opens the form in form
view, normal window mode, with no other arguments, that form does not allow
deletions.

--
Dirk Goldgar, MS Access MVP
Access tips: www.datagnostics.com/tips.html

(please reply to the newsgroup)

Hi Dirk,
It's Access XP (2002).
Macro exactly: action: "Open form"
Form Name: myForm
View: form
Filter name: (blank)
Where condition: (blank)
Data mode: edit
Window mode: Normal

I am scratching my head on this one...


"Dirk Goldgar" wrote:

> "slickdock" <(E-Mail Removed)> wrote in message
> news:53E28DFA-818B-485B-8EF9-(E-Mail Removed)...
> > When I open the form from the db container, it does not allow deletes.
> > When I
> > open the form with a macro that simply runs the open form command, it
> > opens
> > and allows deletes. Aargh!
>
> What *exactly* does your macro say, in terms of actions and arguments? And
> what version of Access? Using Access 2003, if I have a form with Allow
> Deletions set to no, and I run a macro that just opens the form in form
> view, normal window mode, with no other arguments, that form does not allow
> deletions.
>
> --
> Dirk Goldgar, MS Access MVP
> Access tips: www.datagnostics.com/tips.html
>
> (please reply to the newsgroup)
>

"slickdock" <(E-Mail Removed)> wrote in message
news5F384E5-2E2D-4A76-90C9-(E-Mail Removed)...
> Hi Dirk,
> It's Access XP (2002).
> Macro exactly: action: "Open form"
> Form Name: myForm
> View: form
> Filter name: (blank)
> Where condition: (blank)
> Data mode: edit
> Window mode: Normal
>
> I am scratching my head on this one...


Try leaving the Data Mode argument blank, and see what you get. For me,
that made no difference, but I'm using A2003.

--
Dirk Goldgar, MS Access MVP
Access tips: www.datagnostics.com/tips.html

(please reply to the newsgroup)