S
sprucely
I have a dynamic menu system that will modify the contextual popup
menus for highlighted datasheet rows, columns or cells according to
available column names. Each time a user switches between forms it will
check to be sure only operations applicable to the active form are
visible within the context menus.
I need a robust way of detecting when a form, view or table is opened
so that I can set it's OnActivate property. Yes, views, queries and
tables are accessible as forms with an OnActivate property. Just check
screen.activedatasheet.
So far I've managed to accomplish this in two ways, both of which cause
unacceptible instabilities.
One is subclassing the MDIClient window to capture WM_MDIACTIVATE using
vbAccellerator's ssubtmr.dll. This just causes too many crashes. The
other is having an OnTimer loop periodically fire to check if
screen.activedatasheet has changed. This one causes "action
unavailable" and some other weird errors when executing custom
commandbar functions, having something to do with not being able to
trigger one event while in the middle of executing another.
Maybe I'll have to give in and build an application seperate from
Access.
Any suggestions?
menus for highlighted datasheet rows, columns or cells according to
available column names. Each time a user switches between forms it will
check to be sure only operations applicable to the active form are
visible within the context menus.
I need a robust way of detecting when a form, view or table is opened
so that I can set it's OnActivate property. Yes, views, queries and
tables are accessible as forms with an OnActivate property. Just check
screen.activedatasheet.
So far I've managed to accomplish this in two ways, both of which cause
unacceptible instabilities.
One is subclassing the MDIClient window to capture WM_MDIACTIVATE using
vbAccellerator's ssubtmr.dll. This just causes too many crashes. The
other is having an OnTimer loop periodically fire to check if
screen.activedatasheet has changed. This one causes "action
unavailable" and some other weird errors when executing custom
commandbar functions, having something to do with not being able to
trigger one event while in the middle of executing another.
Maybe I'll have to give in and build an application seperate from
Access.
Any suggestions?