Outlook Express rules to outlook as script
 

I want to convert my OE rules to a VB script or a supported type
defined in http://support.microsoft.com/kb/324568

Because there will be a lot of rule that Outlook won't let, i have to
use a scripting method. But i want to convert already created OE rules
to script because i don't know how to write scripts.

Is there a way to do this?

Outlook Express rules to outlook as script
 

"Seth" wrote in message
ups.com...
I want to convert my OE rules to a VB script or a supported type
defined in http://support.microsoft.com/kb/324568

Because there will be a lot of rule that Outlook won't let, i have to
use a scripting method. But i want to convert already created OE rules
to script because i don't know how to write scripts.

Is there a way to do this?


This newsgroup is for support of Outlook
97/98/2000/2002/2003 from the Office suite of products. Outlook
Express is actually a separate program despite the similar name.

For help with your OE questions, try an OE newsgroup such as
microsoft.public.windows.inetexplorer.ie6_outlooke xpress (for OE 6), or
an OE help website such as http://insideOE.tomsterdam.com. If you're
accessing the Microsoft newsgroups through the MS Product Support
Services "Community Newsgroups" web interface, click
http://communities.microsoft.com/new...ternetExplorer
to get to the Internet Explorer groups, then click the plus sign next to
your version of IE to see the link to the Outlook Express group for that
version number. Good luck!

Outlook Express rules to outlook as script
 

Seth wrote:

I want to convert my OE rules to a VB script or a supported type
defined in http://support.microsoft.com/kb/324568

Because there will be a lot of rule that Outlook won't let, i have to
use a scripting method. But i want to convert already created OE rules
to script because i don't know how to write scripts.

Is there a way to do this?

Did you try to import the rules with Outlook? I don't know of any program
that will convert Outlook Express rules to script.
--
Brian Tillman