kadelarsen
Programmer
I have read that Access 2002 has an "Undo" event for forms as well as for controls. Access 2000 does not support this feature. However, I am investigating any possible back-door methods of implementing this functionality.
The problem: I have a form based on a single table with a button to open another form based on a multi-table Oracle view referencing the record on the first form. I am trying to enable/disable the button dynamically. Fields in the first table's key must be filled, and a couple date fields in the record must also be filled, before the button is valid. I have added handlers to the "Change" and "After Update" events for the controls to call a function enabling/disabling the button. However, the user may fill out all the fields (causing the button to be enabled), then choose "Undo," and the button will still be enabled even though the fields are now blank. This is why I want to respond somehow to the "Undo" event (including activation through the menu and ctrl-Z or ESC keypress).
Alternatives: I have considered putting a timer on the form to enable/disable the button. However, I'd prefer to enable/disable appropriately based on events.
Possibilities: I might be able to intercept the "Undo" menu choice using the Office2000 CommandBars interface. Even if this worked, it probably wouldn't intercept the keyboard ctl-Z or ESC commands. To handle these, I might be able to intercept all keypresses going to the form. Another problem with these solutions is that I want the enable/disable code to run AFTER the "Undo" operation has completed and the fields have become blank.
Any suggestions (other than migrating to Access 2002)?
The problem: I have a form based on a single table with a button to open another form based on a multi-table Oracle view referencing the record on the first form. I am trying to enable/disable the button dynamically. Fields in the first table's key must be filled, and a couple date fields in the record must also be filled, before the button is valid. I have added handlers to the "Change" and "After Update" events for the controls to call a function enabling/disabling the button. However, the user may fill out all the fields (causing the button to be enabled), then choose "Undo," and the button will still be enabled even though the fields are now blank. This is why I want to respond somehow to the "Undo" event (including activation through the menu and ctrl-Z or ESC keypress).
Alternatives: I have considered putting a timer on the form to enable/disable the button. However, I'd prefer to enable/disable appropriately based on events.
Possibilities: I might be able to intercept the "Undo" menu choice using the Office2000 CommandBars interface. Even if this worked, it probably wouldn't intercept the keyboard ctl-Z or ESC commands. To handle these, I might be able to intercept all keypresses going to the form. Another problem with these solutions is that I want the enable/disable code to run AFTER the "Undo" operation has completed and the fields have become blank.
Any suggestions (other than migrating to Access 2002)?