M
Matt
I inherited a multi-user, replicated client information database in Access,
and am looking into a possible conversion to Outlook. If anyone can comment
or direct me to resources that discuss a similar implementation, benefits and
drawbacks, maybe sample forms or structures, I'd really appreciate it.
In executing such a conversion, my intent is to
1) take advantage of Outlook's contact management functionality
2) minimize slow performance caused by Access replication and some
less-than-efficient VBA coding
3) eliminate the need for synchronization and any related replication issues
4) eliminate the need to manage deployment of Access front-end files across
multiple users, multiple locations, and multiple system configurations
In our offices, we use Office 2003, including Access 2003 and Outlook 2003,
with an MS Exchange server. We have offices in Los Angeles, Seattle, and San
Francisco, if that matters.
The Access database contains three tables that I would like to convert
(there are many more that I don't see as necessary anymore):
1) client account information (internal account number, annual revenue, type
of account, product, line of business, etc.)
2) client contact information (name, company, address, phone)
3) vendor contact information (name, company, address, phone)
The first table has a one-to-many relationship with each of the second and
third tables. My thought is to establish the following 2 Outlook folders:
1) a Contacts folder for client account information
2) a Contacts folder for client and vendor contact information
Items in the second folder could be linked as appropriate to items in the
first folder.
In its current state, the Access database serves 2 primary functions: 1) to
maintain client account information and allow for simple reporting (total
revenue per line of business, etc.); 2) to maintain client and vendor contact
information.
Given these 2 basic functions, BCM seemed like overkill. Furthermore, it
would seem Outlook 2003 could easily handle these functions. Again, I would
appreciate any help by way of insight as to advantages or disadvantages, as
well as any examples of similar, simple implementation of a client
account/contact management setup. I did read in this group somewhere, for
example, that an import into an Outlook folder involving user-defined fields
(which there would be many) is not necessarily straightforward. Any
information like this that can help me assess difficulty of implementation
and ongoing maintenance would be great.
Thanks much.
It would seem to me that Outlook could easily handle these tasks without the
performance and maintenance issues. But can anyone refer me to a sample of a
similar implementation, or provide insight as to what disadvantages there may
be? For example, I understand that it will be difficult to import client
account information into the Outlook folder, since
and am looking into a possible conversion to Outlook. If anyone can comment
or direct me to resources that discuss a similar implementation, benefits and
drawbacks, maybe sample forms or structures, I'd really appreciate it.
In executing such a conversion, my intent is to
1) take advantage of Outlook's contact management functionality
2) minimize slow performance caused by Access replication and some
less-than-efficient VBA coding
3) eliminate the need for synchronization and any related replication issues
4) eliminate the need to manage deployment of Access front-end files across
multiple users, multiple locations, and multiple system configurations
In our offices, we use Office 2003, including Access 2003 and Outlook 2003,
with an MS Exchange server. We have offices in Los Angeles, Seattle, and San
Francisco, if that matters.
The Access database contains three tables that I would like to convert
(there are many more that I don't see as necessary anymore):
1) client account information (internal account number, annual revenue, type
of account, product, line of business, etc.)
2) client contact information (name, company, address, phone)
3) vendor contact information (name, company, address, phone)
The first table has a one-to-many relationship with each of the second and
third tables. My thought is to establish the following 2 Outlook folders:
1) a Contacts folder for client account information
2) a Contacts folder for client and vendor contact information
Items in the second folder could be linked as appropriate to items in the
first folder.
In its current state, the Access database serves 2 primary functions: 1) to
maintain client account information and allow for simple reporting (total
revenue per line of business, etc.); 2) to maintain client and vendor contact
information.
Given these 2 basic functions, BCM seemed like overkill. Furthermore, it
would seem Outlook 2003 could easily handle these functions. Again, I would
appreciate any help by way of insight as to advantages or disadvantages, as
well as any examples of similar, simple implementation of a client
account/contact management setup. I did read in this group somewhere, for
example, that an import into an Outlook folder involving user-defined fields
(which there would be many) is not necessarily straightforward. Any
information like this that can help me assess difficulty of implementation
and ongoing maintenance would be great.
Thanks much.
It would seem to me that Outlook could easily handle these tasks without the
performance and maintenance issues. But can anyone refer me to a sample of a
similar implementation, or provide insight as to what disadvantages there may
be? For example, I understand that it will be difficult to import client
account information into the Outlook folder, since