[AccessD] Ribbon context

[Rocky Smolin]

Then if it ain't broke...

Perhaps you just need to trap that error (on error goto)...) and give a
friendlier message.

r

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

> Oh to clarify, there are several forms that could use the contextual
> enable/disable (the forms most users use, not the outliers/seldom used,
> etc).
>
> I need to ponder more on this I guess.   Right now the ribbon works, you
> can just press buttons that throw errors because your back end permissions
> basically block you from performing the button action.
>
>
>
> 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
> >
> >
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>