LPurvis
AWF VIP
- Local time
- Today, 07:31
- Joined
- Jun 16, 2008
- Messages
- 1,269
Very true.
Again though, as far as Forcing the save on our own terms, flag variables can come to the rescue.
If you maintain a flag which you only set in your button click to save then any other way of saving can Cancel in the BeforeUpdate without prompt.
Your button save click sets the flag variable to a state that allows the save to progress. (Of course it could still frustrate the user still - not knowing why they can't close the form, navigate to a subform etc...)
Look and feel is very much important.
I find dialog forms can very legitimatey have their windows close button disabled / removed without problem. Larger data entry forms and it would be a more important decision that you'd have to either educate users on or just let them accept it and become accustomed to the implementation.
(There are far greater hardships for them out there I'm sure ;-)
Again though, as far as Forcing the save on our own terms, flag variables can come to the rescue.
If you maintain a flag which you only set in your button click to save then any other way of saving can Cancel in the BeforeUpdate without prompt.
Your button save click sets the flag variable to a state that allows the save to progress. (Of course it could still frustrate the user still - not knowing why they can't close the form, navigate to a subform etc...)
Look and feel is very much important.
I find dialog forms can very legitimatey have their windows close button disabled / removed without problem. Larger data entry forms and it would be a more important decision that you'd have to either educate users on or just let them accept it and become accustomed to the implementation.
(There are far greater hardships for them out there I'm sure ;-)
