[AccessD] Ribbon context
wrwehler at gmail.com
Tue Jan 25 12:02:17 CST 2022
That might be the sensible thing to do. But adding pizazz is sometimes appreciated.
Sent from my iPhone
> On Jan 25, 2022, at 11:58 AM, Rocky Smolin <rockysmolin2 at gmail.com> wrote:
> Then if it ain't broke...
> Perhaps you just need to trap that error (on error goto)...) and give a
> friendlier message.
>> 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,
>> 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>
>>> 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
>>> Unless you're saying that ANY form MIGHT need the button depending on
>>> condition. In which case you could still do it with a line of code in
>>> 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...
>> AccessD mailing list
>> AccessD at databaseadvisors.com
>> Website: http://www.databaseadvisors.com
> AccessD mailing list
> AccessD at databaseadvisors.com
> Website: http://www.databaseadvisors.com
More information about the AccessD