Connection error -ODBC not found- Windows 7 64-bit

filippobe · March 22, 2011 10:07AM

Hi,
I'm trying to connect an Access databse .mdb created with Office 2003 to Omniscope. We have recently installed the 64-bit version of Omniscope (Build 2.6-alpha b566).
I get the following error:

"ODBC data source name not found. This might be caused by using an ODBC data source name which has not been configured in the ODBC control panel. Alternatively, this might be caused by mixing 32-bit and 64-bit applications and databases. For example, it is not possible to connect Omniscope 64-bit to Microsoft Access 32-bit, or Omniscope 32-bit to Access 64-bit. You must use the same architecture for both Omniscope and your Access installation. This is a Windows limitation. Note: Microsoft Access was solely 32-bit until Office 2010. With Office 2010, a 64-bit version was made available. Microsoft do not permit you to install Office 2010 concurrently in both 32-bit and 64-bit versions."

I understand this is a Windows limitation, but is there any possibility to use my Access db with the 64-bit version of Omniscope? Did anyone face the same problem?

Thanks

Filippo

Kamel · March 22, 2011 10:56AM

Hi Filippo,

Microsoft Access 2007 and earlier do not support 64-bit ODBC. Support for 64-bit ODBC is available from Access 2010.

If you have Access 2010 64-bit, please use Omniscope 64-bit to import Access files.
If you have Access 2010 32-bit, please use Omniscope 32-bit to import Access files.
For earlier versions of Access, you can only use Omniscope 32-bit to import the data.

steve · March 22, 2011 3:59PM

Note you can use the 32-bit version of Omniscope in parallel with the 64-bit version on a 64-bit Windows PC. Just install both. Then, use the 32-bit version to extract data and save in IOK format, and open/import the IOK data in the 64-bit version.

If you have a server license you can automate the extract-to-IOK process, hourly for example, using the scheduler.

filippobe · March 23, 2011 7:37AM

Thanks Kamel and Steve.
So probably I am gonna use both the versions in parallel.

filippobe · March 24, 2011 1:40PM

One point.
If I use the 32-bit to save my Access database as .IOK and after I open the file with the 64-bit version my formula fields are automatically converted in static values. Therefore it's necessary to reconvert those field into formula fields.
Is it possible to avoid this?
Thank you

steve · March 24, 2011 4:55PM

So you have imported from Access in 32-bit and added some Omniscope formula fields? Exactly how are you saving the IOK file? In the Save As dialog there is an option to clear formula fields / convert to static. But it should not be enabled by default.
If you are adding the formula fields using Field Organiser in DataManager, you need to make sure "Preserve formulas in output" is ticked in the Field Organiser block's spanner/wrench menu.

filippobe · March 25, 2011 10:20AM

My fault, sorry.
Instead of saving the file as .IOK I was using an output .IOK file.

Regards

steve · March 25, 2011 12:14PM

You should still be able to export formulas using this.

filippobe · April 6, 2011 11:31AM

I have installed the latest build of both versions on a 64bit machine with Windows 7, but the 32bit version is not working.
When I try to start Omniscope the following message is displayed:
Could not create the Java virtual machine.
How can I fix?

Thanks

Filippo

steve · April 6, 2011 12:51PM

It sounds like you've configured your installconfig.properties file to use more memory than 32-bit processes are allowed.

See http://www.visokio.com/kb/installconfig
and http://www.visokio.com/kb/omniscope-memory-allocation

In particular comment out the MAX_MEMORY_MB line with a '#' character.

filippobe · April 7, 2011 4:47AM

Yes. It works.
Thanks Steve
I thought there were 2 different installconfig.properties: one for 32bit and the other one for 64bit version.

Welcome!

Categories

Ideas Parade