M
Mike babb
Hi All,
I've built a Microsoft Access 2010 application that imports data from
my Outlook 2010 email account. My email is an exchange email account.
I'm connecting to the account through Outlook (the mailbox store) and
not to directly to the exchange account.
In a nutshell, the program imports email, appointments, contacts,
notes, and tasks into several tables in Access. It's a very helpful
tool because it helps with time tracking. I can enter the appointments
in my calendar in Outlook, press a button in Access, and the
appointments are parsed and inserted into the proper tables in
outlook. I'm now curious about optimization.
To connect to outlook, I'm using outlook.application. I then iterate
through the different stores and then iterate through various folders
in each store. The problem is that the time it takes to iterate
through each folder in each store is only going to increase because I
will always be adding more items to each folder. The link is not a
live connection: it's opened and then data is read. For example, to
get the appointments, I iterate through the calendar.items object.
Each appointment then becomes a row in a table. The calendar.items
object seems rather slow.
Based on what I've seen, it seems like outlook.application functions
quite similar to a database. The reason why I'm not linking to an
outlook folder under the external data tab in Access is that the
linking to an outlook folder option does import the date and time of
calendar appointments (quite a severe limitation).
What are my options for linking to an outlook folder? Is there
something like an odbc connection to an outlook folder? Is there an
optimized ado conncetion I could be using?
Thanks,
Mike
I've built a Microsoft Access 2010 application that imports data from
my Outlook 2010 email account. My email is an exchange email account.
I'm connecting to the account through Outlook (the mailbox store) and
not to directly to the exchange account.
In a nutshell, the program imports email, appointments, contacts,
notes, and tasks into several tables in Access. It's a very helpful
tool because it helps with time tracking. I can enter the appointments
in my calendar in Outlook, press a button in Access, and the
appointments are parsed and inserted into the proper tables in
outlook. I'm now curious about optimization.
To connect to outlook, I'm using outlook.application. I then iterate
through the different stores and then iterate through various folders
in each store. The problem is that the time it takes to iterate
through each folder in each store is only going to increase because I
will always be adding more items to each folder. The link is not a
live connection: it's opened and then data is read. For example, to
get the appointments, I iterate through the calendar.items object.
Each appointment then becomes a row in a table. The calendar.items
object seems rather slow.
Based on what I've seen, it seems like outlook.application functions
quite similar to a database. The reason why I'm not linking to an
outlook folder under the external data tab in Access is that the
linking to an outlook folder option does import the date and time of
calendar appointments (quite a severe limitation).
What are my options for linking to an outlook folder? Is there
something like an odbc connection to an outlook folder? Is there an
optimized ado conncetion I could be using?
Thanks,
Mike