MS interop and ACE versions question

I'll try not to make this to confusing.

I just developed an app that uses an Access accdb database. All the workstations were suppose to have MS Office 2010 with Access installed. I installed the app on a couple of machines and all was fine. Then the next two didn't have MS Office with Acess installed. They had the company that takes care of there system come out and install MS Office with Access on those two machines. I went back out today and installed my app on those machines but the ACE.12 provider wasn't registered. I had to run "AccessDatabaseEngine.exe" on those machines before my app would work. I thought the ACE.12 provider would automatically be installed and registered when MS Office was installed, does the new version of Office 2010 install differently?

This problem made me think about my app's prerequisites. So, I looked at them and found that is uses "Microsoft Office 2007 Primary Interop Assemblies", even though I use the version 14 interops and have MS Office 2010 installed on my machine. I don't know how or IF I should change that to "Microsoft Office 2010 Primary Interop Assemblies".

One of the main purposes of using an Access db was that since they all had MS Ofice installed I could basically copy the app files to the network and there wouldn't be any need to run a setup program to install the app. This app will be accessed by two different offices in two different towns connect by some type of VPN network. I have no desire to travel to the other office and run a setup program on there machines or when they change machines.

Basically, I'm confused why the ACE.12.0 provider wasn't installed and registered when MS Office was installed and also why my prerequisite is using Office 2007 when I have Office 2010 installed.

Any insight into this situation will be appriciated.

How do you install your application ? Do you create a setup project ?

Quote:

---

One of the main purposes of using an Access db was that since they all had MS Ofice installed I could basically copy the app files to the network and there wouldn't be any need to run a setup program to install the app

---

Niya,
Thanks for the reply. No I don't run a setup project at this time. I could but I'm trying to avoid it.

Quote:

---

This app will be accessed by two different offices in two different towns connect by some type of VPN network. I have no desire to travel to the other office and run a setup program on there machines or when they change machines.

---

Oh...guess I missed that.

Quote:

---

So, I looked at them and found that is uses "Microsoft Office 2007 Primary Interop Assemblies", even though I use the version 14

---

Could you explain this better ?

[EDIT]

Nvm, Dunfiddlin seems to be more knowledgeable about this problem than me. I didn't know that "version 14" and MS Office 2007 Interop were the same thing.

Version 14 Interop is 2007. Office 2010 didn't change those specifications at all. As to Ace 12, I'm afraid you can't assume anything. In theory certainly Office 2010 should provide you with that framework but in practice that doesn't always seem to be the case. Whether through the options chosen in the install or just installation glitches nobody seems to have a definitive answer. As with all things Microsoft it's probably best to assume the worst and be pleasantly surprised when it turns out better than that!

dunfiddlin,
Thanks for the reply. that's good information. It just occurred to me that maybe they installed MS Office x64, maybe this has something to do with it.
Instead of running "AccessDatabaseEngine.exe" to install the db runtimes, is there a prerequisite(s) that I can set so that when I publish the app, the "setup" program will install all the necessary files?

I think the "Setup and Deployment" project type creates very flexible installers. I'm willing to bet you can configure it to install whatever per-requisites you want. I've only toyed with it a couple times and mostly to install simple programs so I can't really get into details about how to use to do more advanced stuff.

The prerequisite packages specified in a ClickOnce installer and a Setup project are exactly the same so the information I gave you about creating a custom prerequisite package in your other thread is valid here too.

Just note that you cannot have 32-bit and 64-bit ACE on the same system. That means that there's actually no way to cover all situations with one installer. You should probably build your project twice: once targeting x86 and a prerequisite for 32-bit ACE that the vast majority of people will use and once targeting x64 with no prerequisite that is specifically for those users who already have 64-bit Office installed.