By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,650 Members | 1,980 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,650 IT Pros & Developers. It's quick & easy.

Access crashes when linked to exchange

P: 1
Hello,

I'm building an asp.net application that will get contact information from an Access Database that is linked to microsoft exchange or outlook.

I go to link tables in Access and choose outlook() and am able to link to the contacts data base. However, when I run my application locally, I get the error: No MAPI clients installed on this machine. Install a MAPI client such as Outlook. Well, Outlook is installed on the local machine but not on the server where Exchange is installed. So, that might be the problem with that approach.

With using the outlook link, I am able to import the contact data, but am not able to link to it with my application. I tried running the application on the server and when I try to run it in IIS, I get the error; "The Microsoft Jet Database cannot find the input table or query "contacts" Maker sure it exists and is spelled correctly.

I have also tried to link directly to Exchange. It pulls up everything, and I am able to select the folder I want. However, when I click finish of the link wizard, Access 2003 crashes. Microsoft gives me an link to how to fix the error. (http://support.microsoft.com/?kbid=239114). This is just to make sure you have the latest version of Microsoft Jet. I have the latest version for both my local machine and server. (That might be the problem there, the server is running microsoft server where my local machine is running xp pro. (The versions of Jet are different)).

Also, Access is not installed on the server. However, I am able to access non-linked access databases with my application on the server.

So, I'm think I have a few choices here:

1.) Install Outlook on the server and link directly to outlook (which doesnt crash access).

2.) Install Access 2003 on the server (the versions of Jet would all be the same and could work)

However, I'm not sure which would be the best approach or if something else could be done. Installing Outlook or Access is something I want to avoid. Im about all out of ideas.

Also, we have two servers and both are running exchange. They syncronize with each other somehow. I didn't set up the exchange part not have much experience with exchange.
Mar 5 '07 #1
Share this question for a faster answer!
Share on Google+

Post your reply

Sign in to post your reply or Sign up for a free account.