P
Peter Downes
A client of mine has recently rolled out licensing for Microsoft Office
Small Business Edition 2003. This was done primarily because of the features
of the bundled Business Contact Manager.
He was horrified to learn that there was no support for Exchange built into
this application. He is currently using Microsoft Small Business Server 4.5
with Exchange 5.5. He has no interest in upgrading his server to Microsoft
Small Business Server 2003.
As usual Microsoft offered a rather pithy solution, which was to install the
Business Contact Manager Database into a separate profile with no Exchange
component. This seems to defeat the purpose of having an address book at all.
The second workaround suggests using POP account, which would make the
Exchange Server a redundant solution (many features of which he still uses).
Is there a fix for this ridiculous situation? If so, please share this with
me.
Small Business Edition 2003. This was done primarily because of the features
of the bundled Business Contact Manager.
He was horrified to learn that there was no support for Exchange built into
this application. He is currently using Microsoft Small Business Server 4.5
with Exchange 5.5. He has no interest in upgrading his server to Microsoft
Small Business Server 2003.
As usual Microsoft offered a rather pithy solution, which was to install the
Business Contact Manager Database into a separate profile with no Exchange
component. This seems to defeat the purpose of having an address book at all.
The second workaround suggests using POP account, which would make the
Exchange Server a redundant solution (many features of which he still uses).
Is there a fix for this ridiculous situation? If so, please share this with
me.