G
Guy
Hi All,
Following on from an earlier posting "Microsoft Access 2007 Ribbon" dated
22/5/2007 and with a lot of assistance from Albert Kallal (MVP). Thanks
Albert.
A workable, elegant solution involving public classes, subroutines and
variables has been achieved.
However, the questions I have are:
Why have Microsoft made us jump through so many hoops just so we can
customise the Ribbon?
Why have Microsoft appeared not to have considered event timing issues
concerning the Ribbon callbacks and the active Access object triggering the
actions.
Why have we had to resort to using public variables and classes which in the
event of an Access error will get cleared?
Surely Microsoft there must be a better way.
If there is please post your solution.
Just my two cents worth.
Guy
Following on from an earlier posting "Microsoft Access 2007 Ribbon" dated
22/5/2007 and with a lot of assistance from Albert Kallal (MVP). Thanks
Albert.
A workable, elegant solution involving public classes, subroutines and
variables has been achieved.
However, the questions I have are:
Why have Microsoft made us jump through so many hoops just so we can
customise the Ribbon?
Why have Microsoft appeared not to have considered event timing issues
concerning the Ribbon callbacks and the active Access object triggering the
actions.
Why have we had to resort to using public variables and classes which in the
event of an Access error will get cleared?
Surely Microsoft there must be a better way.
If there is please post your solution.
Just my two cents worth.
Guy