SQL Connection To Access - 2007 vs 2003?

[jsurpless]

Hi

My application currently works with Access 2003 using the following approach...

strMSAccess_Connection_SQL = "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=" & strDatabaseFilePath
MSAccess_Connection = New OleDbConnection(strMSAccess_Connection_SQL)

MSAccess_Connection.Open()

When I load it onto a WinVista machine running Office 2007, I get the following error

the microsoft.jet.oledb.4.0 provider is not registered

I was doing a little research and I guess 2007 changed a few things? Introduced something called ACE? I tried using

"Provider=Microsoft.ACE.OLEDB.12.0", etc

but I get a similar error to the above...

Thoughts?

Many thanks!

-Justin

 

[jsurpless]

OK, it looks like I was able to solve this by adding the following line to my project file

<PlatformTarget>x86</PlatformTarget>

Looks like I had to do it this way since I am using VBExpress and this is not exposed?

I added this on my 32-bit machine and all still seems to work... sound about right?

 

[MattP]

This is exposed in the Compile tab for the project properties.

From Solution Explorer double click on My Project and go to the Compile tab. Click on the Advanced Compile Options button and you can change it in the Target CPU ddl.

 

[jsurpless]

Doesn't appear to be for Visual Studio Express... at least, I don't see the option...

 

[JohnH]

In VBE in Platform dropdown click the <new> and select the target CPU. Only the "any cpu" profile exists by default.

 

[jsurpless]

I don't know... I still don't see it in the Compile tab

 

[JohnH]

Oh, I didn't notice Compile tab was mentioned, VBE has no interface to manage this in Compile tab. In VBE you have to enable the "Show advanced build configurations" (in VBE 2008 this is in Options, Projects and Solutions, General), then the Configuration Manager will appear in Build menu.

 

[jsurpless]

Ahhh, that makes sense now...

So I'll just add it there, I guess...

Thanks for the help...