Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 4 of 4 total
Thread User DSN properties not persistent
Fri, Dec 30 2011 5:45 AMPermanent Link

Thiriaux

be.wan

Hi,

I just bougth DAC-STD (206b2edbdacstd.exe) and want to use ODBC to import data into Excel
I create a User DSN with ODBC Datasource administrator.
When I import data from xl and select the  DSN I just create, the EDB ODBC Configuration dialog popup with and ask me to re-enter all properties.
I am never able to keep the supplyued properties
why ?

Thanks
Luc
Tue, Jan 10 2012 4:11 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Luc,

<< I just bougth DAC-STD (206b2edbdacstd.exe) and want to use ODBC to import
data into Excel I create a User DSN with ODBC Datasource administrator. When
I import data from xl and select the  DSN I just create, the EDB ODBC
Configuration dialog popup with and ask me to re-enter all properties. I am
never able to keep the supplyued properties >>

Are you using the 32-bit ODBC Administrator to configure the DSN ?  Please
see here for more information:

http://www.elevatesoft.com/supportfaq?action=view&category=edb&question=odbc_driver_64_bit

Excel is still a 32-bit application, so it will look for/load the 32-bit
ODBC driver and use the 32-bit DSN definitions in the registry.

--
Tim Young
Elevate Software
www.elevatesoft.com
Tue, Feb 7 2012 7:59 AMPermanent Link

Johnny McRae

Using Windows 7 64bit and excel 2010
I have been having this exact same problem in excel over the last few day having just changed over from dbisam.
Sometimes the driver would work and some times it would ask for the connection details again despite them already being defined in the DSN. There was no apparent pattern to this intermittent behavior. I was using 2.05 build 7. Upgrading to 2.07 build 1 seems to have solved the issue for me.

In regards to the 32 vs 64 bit odbc administrator issue, both seem to work Identically within excel on my setup.
I created two DSNs
1 from C:\Windows\System32\odbcad32 and 1 from C:\Windows\SysWOW64\odbcad32
both return data from EDB using the same process. Don't know why windows give them both the same name

I do have another issue regarding using '?' as a parameter but think I will create a new thread as below

http://www.elevatesoft.com/forums?action=view&category=edb&id=edb_connect&page=1&msg=465#465
Tue, Feb 7 2012 11:08 AMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Johnny,

<< Using Windows 7 64bit and excel 2010
I have been having this exact same problem in excel over the last few day
having just changed over from dbisam.
Sometimes the driver would work and some times it would ask for the
connection details again despite them already being defined in the DSN.
There was no apparent pattern to this intermittent behavior. I was using
2.05 build 7. Upgrading to 2.07 build 1 seems to have solved the issue for
me.

In regards to the 32 vs 64 bit odbc administrator issue, both seem to work
Identically within excel on my setup. I created two DSNs 1 from
C:\Windows\System32\odbcad32 and 1 from C:\Windows\SysWOW64\odbcad32 both
return data from EDB using the same process. Don't know why windows give
them both the same name >>

The 32-bit EDB ODBC Driver will only work with the 32-bit ODBC
administrator.  64-bit processes cannot load 32-bit DLLs, period.

The 32-bit vs. 64-bit DSNs can seem confusing because the ODBC Administrator
writes out the DSN data in both the 32-bit area of the registry and the
64-bit area of the registry.  But, for MS Office you should always use the
32-bit EDB ODBC Driver and the 32-bit ODBC Administrator.

--
Tim Young
Elevate Software
www.elevatesoft.com
Image