Total Access Components. Total Access Detective. Total Access Memo. Total Visual SourceBook. Total Access Speller. Total Access Startup. Total Access Statistics.
Multi-Product Suites. Total Access Ultimate Suite. Total Access Developer Suite. Total Visual Developer Suite. Visual Basic 6 Products. Total VB Statistics. Total VB Enterprise Suite. Other Products. Sentinel Visualizer. Total ZipCode Database. Thank you! Any more feedback? The more you tell us the more we can help. Can you help us improve? Resolved my issue. Clear instructions. Easy to follow. No jargon. Pictures helped.
Didn't match my screen. This month we perform the reverse operation: get data out of Outlook into Microsoft Access. One might argue that there is an easier way to accomplish what I show below, by using Access linked tables to Outlook or Exchange data, but keep these two things in mind:. The code download that was posted last month contains the demo code for both articles. It is made available again in this link.
The idea for the following solution came from a management request that users be able to upload their emails into a Contacts database where other sales reps could see the history of email correspondence with each contact. Accomplishing this requires:. While this code could run automatically when a user opens the application, it may or may not be ethical to secretly extract all of their correspondence into a database to which others have access.
In my implementation I always left it up to the user to initiate the extraction and gave them control over which folder s were processed.
For example, an employee who chooses to inform HR via email that they are HIV positive might do so with the expectation of privacy. An additional consideration has to do with performance. I found that some of our users have tens of thousands of emails in their Inbox and Sent folders. Processing them all requires no trivial amount of time. In my implementations, I included a date filter so that processing would be limited to a user-selected date.
I also implemented a Cancel function so the user could gracefully exit from the process if it was taking too long. One final point: The code in the article has been modified to avoid line breaks where possible and will not exactly correspond to that found in the demo code. I also noticed that some of my comment lines in the demo code were nonsense. Comments have a way of becoming obsolete. The first step is to give the user an option for which mail folders they wish to process.
To keep the demo simple only the Inbox, Sent Mail and their subfolders will be considered. Since subfolders of subfolders are also enumerated, a function must be created that may be called recursively. Below are the results from a scan of my Outlook folders where my subfolders go only 1 level deep below the Inbox and Sent Items. Part of the enumeration process is to get a count of the number of items in each folder, which is displayed on the left.
This listbox control has its properties set to allow for multiple selections and the Process Emails function will loop through the list and process only those folders and subfolders that have been selected.
Hooking into an Outlook folder is relatively simple. You basically need only two things: An instantiated Outlook object and a folder identifier.
Since this example uses late binding and no reference to the Outlook Library is set, I included comments clarifying that Inbox is 6 and Sent Items is 5. This is all accomplished in the function named GetMAPISubfolders which accepts a long integer value to identify which of our two top folders to process.
0コメント