Exchange 2003 Back-End Database(s)

[DanChard]

Hello.

I've been asked to link the company contacts database into Exchange such that the most current contact information can be accessed across the company using Outlook.

I'm normally an SQL/ VBA programmer which is why I've ended up with this but I know next to nothing about Exchange other than that it is all built around a relational database model.

So, if anyone knows anything that might be of help or could point me in the right direction then I'd be most grateful.

Thanks in advance,
Dan

 

[jvande]

Exchange is it's own database. I would recommend importing the existing contacts database and making the swith to just use the exchange contact managment and database functionality built into exchange. We use it and it is very robust.

 

[DanChard]

Hi, thanks for your suggestion.

There will always be a need to keep the contacts in a seperate database as it has a number of other uses, and since most of our users who maintain the contact data access it through a web front-end (and won't want this to change) there needs to be a custom database for them anyway.

Plus, although I haven't looked at it in great detail, there seem to be an awful lot of redundant fields in the Exchange contacts database. And if we had a contact with more than just a business, home and other address we wouldn't be able to store those details in Exchange.

This is my main justification for keeping the database separate but it all goes wrong when those with little knowledge but a lot of power come along and make 'helpful suggestions'.

Any other ideas?