Replies

Thanks Hans. Found it.

Thanks, Joe. I was able to delete the folder using its short name.

How does book.xlt interact with ‘Options’ settings? It appears that where the two conflict book.xlt rules. So what’s the point of the options?

Hi Rory,

That was it! Thanks. There’s also a file called Sheet.xlt in the XLSTART directory. What’s the purpose of these files? I guess I created them at some point, but I can’t think why.

How is the Linksys security? I want a router that cannot be seen by passers-by. You have to know it’s there and actively negotiate a connection and supply a password.

I guess so!

I need a router, because I’m adding a second computer. Plus I WANT a wireless router, so I can use my new laptop anywhere around my house or backyard.

My fault. I omitted to check the box in front of the source file! As soon as I did that I was able to map the fields. I was able to separate the name and address into two fields by using Notepad’s “find and replace” to replace the right angle bracket with a blank, loading the file into Excel and parsing it using the left angle bracket as a delimiter. Voila! Thanks for your help.

Thanks for the revised code. I was able to run it successfully.

> Outlook only exposes the Sent-on-behalf-of name and not the address.

That’s not correct, or at least it does not seem to be. If you look at an email it shows the address in the from field, enclosed in angle brackets after the name. It may be all one field but it’s parsable. I was able, using a combination of notepad and Excel, to extract the email addresses I wanted. However, I don’t seem able to import them back into an Outlook contacts folder. I exported them to an Excel spreadsheet with two columns, one for name and one for email address. When I try to import this back into Outlook, the ‘Map custom fields’ button is greyed out, so I can’t tell Outlook where to put the data. If I click on ‘Continue’ without mapping custom fields, Outlook just sits there for ever until I click ‘Cancel’.

Thanks for the clarification.

> Set selSelItems = Outlook.ActiveExplorer.Selection is where the items you have manually selected (by clicking, Shift-clicking or Ctrl-clicking for multiples)

That’s good; I don’t want it to loop through all the mail folders, just the one selected.

> Set colContacts = Outlook.Session.GetDefaultFolder(olFolderContacts).Items selects the default contacts folder

I’m not sure which is the default contacts folder. Is that the root ‘Contacts’ folder? If it’s the root folder, that would be OK as there is nothing in that.

Thanks for the code. It partly worked; it got the names but not the email addresses. See attached.

Thanks for the code sample. In the line “Set colContacts = Outlook.Session.GetDefaultFolder(olFolderContacts).Items” I presume this selects the currently selected folder, yes? I have about 300 Outlook mail folders. Where does the code send the output? See my post 618,294. Does this have any impact on the code?

The attached shows what I get when I export to Excel. That’s the address of the mailing list, but if I look at individual emails, the from field shows the actual email address of the sender as ‘Offroad-request@offroadlist.com on behalf of Andrew Simpkins [andrew@xxxxx.com]’. It’s what follows the ‘on behalf of’ that I want to capture. It’s obviously in the email somewhere, but it doesn’t appear to be in an exportable field.

I already tried that and it doesn’t work. Most of the emails are from a mailing list, and although the individual emails show the sender’s email address, the export function doesn’t export that but instead exports just the mailing list address.

No, they’re not Usenet news posts. They’re very similar to Yahoo! groups, though with a slightly different MO. You post via email and get replies via email; all subscribers get all the emails. They also have a web address, enabling you to see posts with a browser. I’m trying to find out if it’s possible to have posts emailed to you after the fact. Of course, the Google people should be able to answer this question, but they haven’t/won’t.