Friday, January 29th, 2010 at
21:42
People new to import/export frequently pose a question to an Outlook group asking “How do I import from program “x”? The typical (and correct) response is “Look to see what formats does “program X” export to and select that”
For some reason, when Outlook is involved, far too many people seem to think that anything involving Outlook is an Outlook issue. What really needs to be understood is that the actual importing and exporting from any program is a defined process. The import/export functionality in Outlook has not changed since Outlook ‘2000 (or possibly Outlook ‘97) and deals with very specific kinds of data.
Monday, January 25th, 2010 at
14:26
Using the Outlook import/export wizard is not an option when you want to import/export:
- any user-defined fields (standard message class)
- custom fields contained in a custom form
- an Exchange public folder
- a delegate Exchange folder
- any standard field that does not appear in the Outlook import/export field map
The Outlook import/export wizard only creates new contacts using the standard contact form (MessageClass = <IPM.Contact>) regardless of what the default is for the form
This is a preview of
When Outlook Import/Export is not an option
.
Read the full post (233 words, estimated 56 secs reading time)
Monday, January 25th, 2010 at
14:26
Importing from an Excel file is very common activity. There is likely a good chance that if you are reading this that you are currently investigating a problem that you are having or have had one in the past. One Excel feature that probably generates the most questions (and problems) is “Named Ranges” which include the following:
- When I try to import it keeps asking me for a “named range”
This is a preview of
Outlook & Excel – Importing from/Exporting To
.
Read the full post (629 words, estimated 2:31 mins reading time)