G
Guy
Following on from an earlier posting "Microsoft Access 2007 Ribbon" dated
22-May-2007 and after assistance from Albert Kalall (MVP). Thanks Albert.
Finally the .ADP application I am working on has a workable, even elegant
solution to the problem of managing and customizing many Ribbons. The
solution uses a combination of public classes, subroutines and variables.
However:
1) Why have Microsoft made us jump through so many hoops just so that we can
customise the Ribbon?
2) Why have Microsoft appeared not to have considered the timing of Ribbon
callback events in relation to the active Access object events
3) Why have we been forced to use a combination of public classes, variables
(and subroutines) which following an Access error will get cleared causing
any Ribbon management to also fail.
Surely Microsoft there must be a better solution.
If you have a better solution please post it.
Just my two cents worth
Guy
22-May-2007 and after assistance from Albert Kalall (MVP). Thanks Albert.
Finally the .ADP application I am working on has a workable, even elegant
solution to the problem of managing and customizing many Ribbons. The
solution uses a combination of public classes, subroutines and variables.
However:
1) Why have Microsoft made us jump through so many hoops just so that we can
customise the Ribbon?
2) Why have Microsoft appeared not to have considered the timing of Ribbon
callback events in relation to the active Access object events
3) Why have we been forced to use a combination of public classes, variables
(and subroutines) which following an Access error will get cleared causing
any Ribbon management to also fail.
Surely Microsoft there must be a better solution.
If you have a better solution please post it.
Just my two cents worth
Guy