Hi Sue Mosher,

I was looking for a way to do something like you describe below. I want to
take my distribution list and export to a file so I can upload to my website
for monthly newsletters. Are these the correct steps? Or is there a
different procedure for what I am looking to do.

Thank you for your help!

Zeb Mabie


"Sue Mosher [MVP-Outlook]" wrote:

Step-by-step:

1) Go to your Outlook Contacts folder.
2) Double-click the DL to open it.
3) Look on the File menu for the Save As command.
4) Choose .txt as the output format.
5) Select the folder to save it.
6) Click Save.

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003
http://www.turtleflock.com/olconfig/index.htm
and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx

"Dale Watson" wrote in message ...
Sue, thanks for your help. I would have no problem saving the DL as a "txt"
file - IF ONLY I knew how to access the DL. After searching (again), I can't
find a method of accessing the DL in a way that would enable me to save it as
a text file. I won't mind you making me "red-faced" by pointing out that
what you're suggesting "should be obvious". :-). "Many thanks" if you can
point me in the right direction with more specifics.

"Sue Mosher [MVP-Outlook]" wrote:

Just save the DL as a .txt file.

"Dale Watson" Dale wrote in message ...
I'm using Outlook 2003 SP2. I have a large Distribution List, the contents
of which I need to share within our branch.

It would make perfect sense to be able to copy/paste this information into
Excel and/or Word; however this does NOT seem possible.

Is there "any" way to transfer this information - i.e. if not through some
"hidden" method of copy/paste, then perhaps an export/import method, or
perhaps through VBA?

Many thanks for any help offered.

If a solution is offered and if this is monitored by Microsoft staff, might
I suggest that this information should be made known to current users - i.e.
more prominently.

If a solution is NOT offered, might I suggest that Microsoft staff will want
to address this for a future release.

Thanks again.

Dale Watson