Continuously monitors Outlook and stores email data in database.
shanq
receiving) and store email data in database?
James A. Fortune
> Is there a way for access to continuously monitor Outlook (sending/
> receiving) and store email data in database?
I used Microsoft Office 2000 to automate a system to control orders
automatically for an e-commerce web site. It used an Access ADP, an
Access MDB, Quickbooks and Outlook working in tandem to gather order
data from SQL Server, send HTML orders to catalog suppliers, send HTML
shipping status updates (including backordered items) to customers and
periodically create a Quickbooks import file containing a summary of
the order information. The customer used FrontPage to create the
basic parts of the web site, then I filled in ASP code within that
along with some HTML pages I created to allow customers to log in,
choose items, examine their cart and submit their order through
Verisign. I scheduled Access to open daily and do all the processing
before closing. The only manual part of the whole process was
importing the Quickbooks file. The e-commerce web site offered over
180,000 products.
For what I did to handle the Send/Receive in Outlook 2000, look at:
http://groups.google.com/group/comp.databases.ms-access/msg/f2b38e0abd1559d5
For the second part, I went to http://www.microsoft.com and Bing'ed:
outlook object model
That should give you enough information to enable you to get the email
information and put it into your database. Naturally with code that
old, there are several things that could be done better, but overall
the system worked marvelously. Two large software companies gave up
on the site (web part only) after billing the customer about $20,000
each and not finishing the project. I took on the project mostly as a
way of getting used to working with ADODB, which was relatively new at
the time. I approached the planning as if it were a large Access
database with lots of users using unbound forms. The little bit of
extra knowledge I needed was easily obtainable. The final version ran
so well that I didn't even need to take advantage of optimizations
specific to SQL Server.
James A. Fortune
CDMAP...@FortuneJames.com
Disclaimer: Any programming examples shown are for illustration
purposes only, without warranty either expressed or implied. This
includes, but is not limited to, the implied warranties of
merchantability or fitness for a particular purpose. This post assumes
that you are familiar with the programming language that is being
demonstrated and with the tools that are used to create and to debug
procedures. I might explain the functionality of a particular
procedure, but I am under no obligation to modify these examples to
provide added functionality or to construct procedures to meet your
specific requirements. Any code samples posted contain no known
hidden material defects. However, anyone who uses any code sample
posted does so with the understanding that they are responsible for
any testing of any illustrative code sample for any particular use.
Furthermore, anyone using an illustrative code sample I provide or
code derived from it does so at their own risk.
A 'q' in Pinyin is pronounced "like cheek, with the lips spread wide
enough when you say ee. Curl the toungue down to stick it at the back
of the teeth and [s]trongly aspirate when pronounce it." --
http://en.wikipedia.org/wiki/Pinyin