Search results

After the row with "full-name" is found, again use Instr in that row to find the next <td> and </td>. The text between both is the value you're looking for.

You need to set the MessageClass property of the contact to the name of your custom form.

See the SendUsingAccount property for setting the account, or see SentOnBehalfOfName for setting an address (this works only with an Exchange account). Good luck for the signature, since OL 2013 there's no easy way. Best approach could be to save a template for each account/signature, and send...

Even if there's only one recipient, Split returns an array with one item, so you can always use arr(0) and don't need the If-Else thing. Even if there's only one recipient, Split returns an array with one item, so you can always use arr(0) and don't need the If-Else thing.

The fist step is ok, move the part you want to move to the new module. Then feed the new function with all the values it needs, for instance strMsgSubject. As strMsgSubject is filled in the old function, it is unkown or empty in the new one. So, to pass that one value the function declaration...

I'd use the Split function, and split the To property by the semicolon. It returns an array, it's first item is what you're looking for.

It only needs to be accessible when the archiving procedure is is running.

Wouldn't it print each item just once, if you don't group by categories?

I'd contact the vendor of ProjectWise. If they offer that API, they'll know how to use it.

The only benefit of 64bit is large files, which most people don't need.

All a rule could do here would be to trigger a script for only those emails you want to forward. For all of the rest you need to write that script. Here's a sample that's not triggered by a rule, but as soon as an item is added to your inbox. It searches a contact by the sender address of the...

Try to add this: dim fw as mailitem set fw=item.forward fw.t0=item.subject fw.subject=... fw.send

There's nothing wrong with the code except this line: oMail = objItem should read set oMail = objItem

If you manually run the rules, you can apply them to any folder.

The DASL name for that property is "urn:schemas:mailheader:keywords". The ID is "Keywords", the GUID "{00020329-0000-0000-C000-000000000046}"

Another drawback of copy&paste is that it also copies the search_key property of the original item. The one or other sync tool could have its problems with that.

This macro creates a copy of the selected task item: Create a New Journal Item Based on an Existing One - VBOffice

This should get you started: Send an Email Template - VBOffice

See the BeforeItemPaste event of the Explorer object. You can get a ref on the dragged item via the ClipboardContent variable, which is a Selection object in this case. Here read the user props of the dragged items. The next event that should trigger is the NewInspector event, which gives you a...

You can access user props this way:... = Folder.Items.Item(iRow).UserProperties("name").Value