I am going to have to agree with Jean-Guy.
"a program running that would continuously monitor your input" is a dangerous
thing for two reasons.
1. it will suck up resources big time
Think about it. "continuously monitor your input" means:
you type " ".....it executes
you type "t".....it executes
you type "h"....it executes
you type "i".... it executes
you type "s"....it executes
you type " ".... it executes
you type "i".....it executes
you type "s".... it executes
and on and on. Word memory management is better than it used to be (the
older ones of us here remember the nightmare of Word 6), but continuously
monitoring input will be a huge strain. As you do not have access to the
REAL guts of Word, you have to work through VBA, which means its parser and
compiler. These take resources.
2. unless your logic is flawless, the possibility of creating typos - rather
than fixing them - is rather high.
I am not disputing the need you express, but I too wonder about the approach.
Real-time monitoring - and possible processing (i.e. changing) - of input in
Word is not recommended. But if you do, be darn sure your logic is bang on.
Jean-Guy Marcil wrote:
>> Of course, you are not dyslexic :)
>>
>[quoted text clipped - 4 lines]
>> thousand of my users would, as they have tried it and then paid for
>> it.
>
>I was not arguing the usefulness of what you are trying to achieve. I was
>just commenting on the approach. While your goal maybe praiseworthy, your
>approach is fraught with dangers and difficulties that can't easily be cured
>with Word VBA. This is why I recommended a few alternatives to help you
>achieve your goal.
>
>Even if you manage to make your code run correctly, you will have to warn
>your users that as long as your code is running, they cannot use any other
>add-ins or macros. Unless, you provide a Stop/Start button that your user
>will need to use before and after running code from other macros.
--
Message posted via OfficeKB.com
http://www.officekb.com/Uwe/Forums.aspx/word-programming/200802/1