Hi,
I'm having trouble linking Visio or Excel to my elevatedb database via ODBC.  I've loaded the ODBC driver and configured it via c:\windows\syswow64\odbcad32.exe but when I look for the driver in Visio it is nowhere to be found.
I presume that Visio is maybe looking in the 32bit ODBC area where the elevatedb driver isn't located.  I'm using the 64 bit version of Visio so I presumed it would look in the right place for the ODBC driver.  I think the problem is that I don't really understand the registering of the drivers in the Win7 64-bit environment.  Can something be modified so that the driver appears in both the 32 and 64-bit ODBC registration areas, or is there something else that I need to be aware of to get this working?
Thanks for any help.
Colin

I'm pretty certain that you cannot use 32bit ODBC from a 64bit app - like Visio. Hence you either need to use 32bit version of the Visio or 64bit version of the elevate ODBC - while i don't use it i believe it is available as of latest version 2.06.

So for this you should install 64bit version of the edb odbc and use the regular 64bit odbc connection admin utility (not 32)

Raul


<<

Colin Wood wrote:

Hi,
I'm having trouble linking Visio or Excel to my elevatedb database via ODBC.  I've loaded the ODBC driver and configured it via c:\windows\syswow64\odbcad32.exe but when I look for the driver in Visio it is nowhere to be found.
I presume that Visio is maybe looking in the 32bit ODBC area where the elevatedb driver isn't located.  I'm using the 64 bit version of Visio so I presumed it would look in the right place for the ODBC driver.  I think the problem is that I don't really understand the registering of the drivers in the Win7 64-bit environment.  Can something be modified so that the driver appears in both the 32 and 64-bit ODBC registration areas, or is there something else that I need to be aware of to get this working?
Thanks for any help.
Colin
>>

Raul wrote:

I'm pretty certain that you cannot use 32bit ODBC from a 64bit app - like Visio. Hence you either need to use 32bit version of the Visio or 64bit version of the elevate ODBC - while i don't use it i believe it is available as of latest version 2.06.

So for this you should install 64bit version of the edb odbc and use the regular 64bit odbc connection admin utility (not 32)

Hi Raul, to load the odbc driver I used the trial version of  ElevateDB DAC-TRIAL - Version 2.06 Build 1.  I'm not aware how to tell it to load in 32 or 64 bit mode.  Is this possible, or does the installation simply look at the operating system to determine what it should load?
Col

Sorry but i don't use edb odbc so have no first hand knowledge.

I would assume that installer installs both. If you look under the install folder (usually in c:\program files\ or c:\program files(x86) find Elevate related folder - in this case for ElevateDB DAC or such ) and see if there are files and or folders for both 32 and 64.

Looking  at my system the 64 bit ODBC admin appears to be in windows\system32 and is called "odbcad32.exe" (that is completely unintuitive but task manager shows this is 64bit app). the one in
Windows\SysWOW64 is also called odbcad32.exe and appears to be a 32bit app.

So if running the odbc admin from windows\system32 does not let you create EDB data sources then i would suggest you get in touch with Elevate support as they can probably help you quickest (64bit stuff is brand new) : support@elevatesoft.com

Raul


<<
Hi Raul, to load the odbc driver I used the trial version of  ElevateDB DAC-TRIAL - Version 2.06 Build 1.  I'm not aware how to tell it to load in 32 or 64 bit mode.  Is this possible, or does the installation simply look at the operating system to determine what it should load?
Colin
>>

Thanks Raul, judging from the timestamp on this post, my guess is that everyone from support is fast asleep now.  I'll have to wait a while... usual problem as I'm in Australia and time zones are a bit out of whack with others.

Yes, Elevate support does operate in eastern time (-5) from 900-1700 so you will be out of sync in regards to daytime.

I still suggest you email support with this one as these newsgroups are peer supported and elevate support staff does not actively monitor them

Raul


<<
Colin Wood wrote:
Thanks Raul, judging from the timestamp on this post, my guess is that everyone from support is fast asleep now.  I'll have to wait a while... usual problem as I'm in Australia and time zones are a bit out of whack with others.
>>

Colin,

<< I'm having trouble linking Visio or Excel to my elevatedb database via
ODBC.  I've loaded the ODBC driver and configured it via
c:\windows\syswow64\odbcad32.exe but when I look for the driver in Visio it
is nowhere to be found. I presume that Visio is maybe looking in the 32bit
ODBC area where the elevatedb driver isn't located.  I'm using the 64 bit
version of Visio so I presumed it would look in the right place for the ODBC
driver. >>

Actually, if you're using the 64-bit version of Visio, then you need the
64-bit ODBC driver, which is available as part of the EDB-DAC products.
Unfortunately, I noticed that the EDB-DAC installations were not updating
the registry for the 64-bit ODBC drivers properly during installation, so I
needed to upload new versions of the 2.06 B2 builds (2.06 B2 just came out
today).

If you download any EDB-DAC product after 12:20pm (EST) today, you'll be
getting the correct installation with the proper registry updates.

--
Tim Young
Elevate Software
www.elevatesoft.com

"Tim Young [Elevate Software]" wrote:

If you download any EDB-DAC product after 12:20pm (EST) today, you'll be
getting the correct installation with the proper registry updates.

Hi Tim, the new version has a problem.  When using the ODBC Administrator to configure the new driver it ends up crashing and reports "ODBC Administrator has stopped working"  the ODBC Administrator is then restarted, but the configuration is lost.  This happens in both the 32 and 64 bit versions of the Administrator.
Col

Both the trial and full versions seem to do the same thing.

Colin


In your situation I'd send an email direct to Tim rather than waiting for him to visit these groups again.

Roy Lambert