Howard Kaikow
01-09-2005, 03:55 PM
Due to sloppily written 3rd party apps/add-ins/macros, many users are troubled by the message asking whether they want to save changes to the Normal template.
In many/most cases, one has to know how to examine VBA code to determine the cause of such changes.
I was thinking of doing the following in a class, but I'm not sure whether
this would help or further annoy users.
I would include code that checked for a dirty Normal template at class
startup AND before each macro runs.
I would issue a message asking whether the user wanted the macro to save the changes now, and also give the user an opportunity to cancel the macro. The choices would be Yes, No, Cancel.
Is the above useful?
In any case, I will include code that checks for changes in Normal when the
class terminates. This is to assure that my code does not cause any unintentional changes in the Normal template.
In many/most cases, one has to know how to examine VBA code to determine the cause of such changes.
I was thinking of doing the following in a class, but I'm not sure whether
this would help or further annoy users.
I would include code that checked for a dirty Normal template at class
startup AND before each macro runs.
I would issue a message asking whether the user wanted the macro to save the changes now, and also give the user an opportunity to cancel the macro. The choices would be Yes, No, Cancel.
Is the above useful?
In any case, I will include code that checks for changes in Normal when the
class terminates. This is to assure that my code does not cause any unintentional changes in the Normal template.