[AccessD] Fwd: Ribbon context

[Rocky Smolin]

---------- Forwarded message ---------
From: Rocky Smolin <rockysmolin2 at gmail.com>
Date: Tue, Jan 25, 2022 at 9:57 AM
Subject: Re: [AccessD] Ribbon context
To: Access Developers discussion and problem solving <
accessd at databaseadvisors.com>


I don't let users use the ribbon. I keep it minimized.  I have add, delete,
save and undo command buttons on my forms.  Very old school, I know, but
that ribbon is more trouble than it's worth (IMO).

r

On Tue, Jan 25, 2022 at 9:44 AM Ryan W <wrwehler at gmail.com> wrote:

> The problem is it doesn't contextually change if you change forms with tabs
> in the Open/Close events.  OnActivate seems like the best place, but let us
> say we're in a form where it's deactivated through invalidation and they
> open a new form that basically has no requirements to contextually
> disable/enable the button. It stays disabled, because the new form was
> opened and has NO code to invalidate the ribbon control. So it stays
> disabled.
>
> Keeping forms open and using tabs is why I needed to figure out a way to
> add the calling code to every single OnActivate event on every form,
> nearest I can tell.
>
>
>
> On Tue, Jan 25, 2022 at 11:30 AM Rocky Smolin <rockysmolin2 at gmail.com>
> wrote:
>
> > If you can disable the button with a line of code and it is needed in a
> > dozen forms, then I would take the brute force method - put that disable
> > line of code in the open event and put the enable line of code in the
> Close
> > event.
> >
> > Unless you're saying that ANY form MIGHT need the button depending on
> some
> > condition. In which case you could still do it with a line of code in
> each
> > form calling a public function that would return True/False for
> > disabling the delete button.
> >
> > Unless each form that MIGHT need to have its delete button disabled would
> > have differing conditions.  In which case...
> >
> > r
> >
> >
> > On Tue, Jan 25, 2022 at 8:47 AM Ryan W <wrwehler at gmail.com> wrote:
> >
> > > Well, lets put it this way:
> > >
> > > All forms need it but only a dozen or so forms that are used frequently
> > > that the contextually enabled function would be nice
> > >
> > >
>
>