A
Atlas
I've develop a small accounting app (Access 2003, .adp, ADO/SQL Server 2000)
that would benefit from managing dynamically Exchange Server Contacts
straightfully. Customer's data is allready in there.
I don't need to store Contacts' data in a SQL table. I only need a reference
to the multiple Public Folders\Contacts, eventally letting Access users to
list names and eventually group them on a category basis.
Would like to avoid continuos import/export.
Just to avoid Exchange Server downtime problems it could be wise to store in
a SQL table the minimum necessary customer data, like:
- Customer.id
- Display name
- Category
- Reference to Exchange Server contact
This minimum data could be used for lookups/sorting/grouping. More details
could be retrieved from the Exchange Server loading and instance of Outlook
What technique could be involved?
once done, what if a contact is moved somewehere else?
Thanks
that would benefit from managing dynamically Exchange Server Contacts
straightfully. Customer's data is allready in there.
I don't need to store Contacts' data in a SQL table. I only need a reference
to the multiple Public Folders\Contacts, eventally letting Access users to
list names and eventually group them on a category basis.
Would like to avoid continuos import/export.
Just to avoid Exchange Server downtime problems it could be wise to store in
a SQL table the minimum necessary customer data, like:
- Customer.id
- Display name
- Category
- Reference to Exchange Server contact
This minimum data could be used for lookups/sorting/grouping. More details
could be retrieved from the Exchange Server loading and instance of Outlook
What technique could be involved?
once done, what if a contact is moved somewehere else?
Thanks