Thanks for apologizing on my behalf, Paul. Actually, you may not remember, but there was a period during which I was finding that scripts would simply not <work> unless there was an activate in them; it had to do with a conflict with one of the add-on utilities, I think it was ASM, and the setting to automatically hide all but the front application. When Entourage was hidden, the script could not get "current messages" from it. So Activate was essential, even for scripts running in Entourage by rule or schedule.
I did fix that problem, but I missed removing the activate from a few older scripts, apparently. On or near 8/9/2002 9:05 AM, Paul Berkowitz at [EMAIL PROTECTED] observed: > By way of explanation: the reason why 'activate' has found its way into some > scripts designed to be run automatically from rules and schedules (and thus > where Entourage may be in the background) is probably that when a scripter > tests out scripts from a script editor (which is in the front when you start > testing), it's often helpful or even necessary to have the targeted > application (Entourage here) come to the front while executing. I guess > Allen forgot to remove a couple of these commands when the scripts were > complete - that's quite easy to do. 'activate' will not ever be a nuisance > in scripts run manually from the Scripts menu, since by definition Entourage > is in the front when you access the menu. -- My web page: <http://home.earthlink.net/~allenwatson/> My scripts page: <http:homepage.mac.com/allenwatson> Microsoft MVP for Mac Entourage/Word--<[EMAIL PROTECTED]> -- To unsubscribe: <mailto:[EMAIL PROTECTED]> archives: <http://www.mail-archive.com/entourage-talk%40lists.letterrip.com/> old-archive: <http://www.mail-archive.com/entourage-talk%40lists.boingo.com/>
