Hello All. I posted this question in microsoft.public.exchange2000.development, but I thought there might be some other Exchange experts here as well...
I'm investigating writing an application that would be used with Outlook Web Access and Exchange 2000. There is a SQL Server 2000 database that contains some contact information. I want to be able to display this data seamlessly along with the regular OWA stuff. After viewing the contact, the user can perform a certain operation on the contact which will involve some more processing on the SQL Server. Here are a couple ideas I had from my preliminary research. (1) Create a public folder and populate the folder with the data from SQL Server. This would require some sort of synchronization between SQL and Exchange. Since there are some custom fields involved, I assume that I would have to create a custom content-class, along with a custom web form for displaying that data, which would be added to the Forms registry. (2) Customize / replace the Outlook navbar so that it will contain a new button that loads a separate ASP page that queries the SQL server. In this case the contact data would not be stored in Exchange, so any contact forms would have to be developed from scratch. With this approach, is it possible to add a third "section" to the navbar (in addition to "Folders" and "Shortcuts")? Comments on the feasibility of each approach would be appreciated. Which one would be the faster and/or better approach? Thanks, Brian Baker _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED]
