TIBCO Spotfire

Hi,

I have Spotfire (3.2.1) and Microsoft Access 2010 installed on a 64 bit laptop. My problem is that Spotfire can't see any access database files. It is OK with Excel 2010 workbooks.

Can anybody help?

 

Thanks

 

Pete 

You need to install the 64-bit version of Microsoft Access 2010, so that the 64-bit ODBC drivers are installed.

Is this the only work around this problem? I can't see why Spotfire can't read 32 bit versions of access when it can read 32 bit versions of excel? Seems very odd to me.

Try downloading and installing the 64-bit package from http://www.microsoft.com/downloads/en/details.aspx?FamilyID=c06b8369-60dd-4b64-a44b-84b371ede16d&displaylang=en Spotfire uses drivers provided by Microsoft to read Access files and when running on a 64-bit OS, 64-bit drivers are needed. The drivers needed for reading Excel are included in Spotfire itself.

<flame state="on">

And if you have any leverage within Microsoft please let them know of the absurdity of not supporting 32 and 64-bit Access drivers installed side-by-side and not even explaining why.

http://social.msdn.microsoft.com/Forums/en-US/adodotnetdataproviders/thread/abf34eea-1029-429a-b88e-4671bffcee76/#b6deab32-c1e0-436d-b783-8a4948ff99ec

</flame>

I'm having the same issue, unfortunately when I try to install the 64-bit drivers, I get an error that says I have a 32-bit install of Office.  Is there any other workaround?

 

I'm having a similar problem -- but on a 32-bit machine. Perhaps my memory is bad, because I know that I used to use Access Queries all of the time from Spotfire, but now I don't remember how. We're using Access 2010 and Spotfire 2.2. The option to use a file doesn't permit us to select an MDB file. Which makes me think -- do I need to change the extension to ACCDB for Spotfire to recognize it? It always recognized the MDB extension, and that was an earlier version of Access, but I can't imagine that the file dialog box would being that sophisticated. Rather, I think I'm doing something wrong.

Hello Chuck,

You may want to check with Spotfire Support in your company (Albert van Os), I think he has a work around.

Kind regards, Andre

All hardware devices need 64-bit drivers to work on a 64-bit version of Windows. Drivers designed for 32-bit versions of Windows don't work on computers running 64-bit versions of Windows.

If they are normal application programs, then they probably will work. If they are applications that depend on an actual
driver, then no.

This would appear to be the case for access since Spotfire is using the actual Access driver. Hence the 64bit OS is going to require the 64 bit driver for Access.

Fully agree on this problem being an utterly stupid Microsoft decision. The MS Office 2010 ODBC/OleDB 64-bit driver package *explicitly* checks whether a 32-bit version (from either Office 2010 or Office 2007) is already present on your system. Also Microsoft themselves mention that the 64-bit Office application suite brings little/no advantages and unlike the 32-bit version has very little supported add-ins (!).

However since the Office 2007 application suite (32-bit) does not have such an insane/ridiculous check, you could simply first install the 64-bit Office 2010 ODBC/OleDB drivers and after that the (32-bit) Office 2007 application suite. The Office 2007 setup should not even be able to recognize the 64-bit Office 2010 components. That way both 32-bit and 64-bit MS Office drivers will be present on the system. Spotfire which runs in 64-bit mode on a Vista64 or Win7 x64 based machine and can then use the 64-bit drivers to link to MS Office files without the need to to obtain and install a 64-bit Office application suite.

Lately I came across messages on the Internet, that describe the following workaround to install the 64-bit MS Office 2010 drivers on a system that has existing 32-bit MS Office drivers.

Install the 64-bit runtime files using the "/passive" switch like this:
“AccessDatabaseEngine_X64.exe /passive”

I haven't been able to test this yet, so try at your own risk...

Hi Albert, the "/passive" worked (access file loaded into spotfire) **however** access won't work.   Still, uninstalling worked per MS' instructions on the above link and then access worked fine.  Though less elegant, pasting 100,000 lines into excel is where i'm heading. 

 Would love to hear if anyone else is successful in this renaming of the registry that was recommended on this MS link. http://social.msdn.microsoft.com/Forums/en-US/adodotnetdataproviders/thread/abf34eea-1029-429a-b88e-4671bffcee76/#b6deab32-c1e0-436d-b783-8a4948ff99ec

 

I think these workarounds only make sense if you're attempting to install the 64-bit Office2010 runtimes on a machine which has an existing Office 2007 application suite (32-bit).

This approach won't work properly for getting Office 2010 32-bit and 64-bit to work, as the identifiers for the drivers are identical.This is confirmed by people in the MS link mention you listed. They suggests that typically the 32-bit driver is (re)set as the default and blocks out the 64-bit version.

In short Microsoft is really making a mess of this....