using xlodbc.xla with Excel 2003
 

I can't resolve the error "Attempt to register odbc32.dll failed" when using
the xlodbc.xla reference in an Excel vba macro so I can use the function
sqlOpen.

It used to work but since upgrading to XP, the excel spreadsheet now keeps
coming with the above error. The odbc32.dll file is on the
C:\windows\system32 folder, I have saved and referenced the xlobdc.xla file
from Excel 2002 - but how to get it to register to the correct odbc32.dll now
that I have XP running?

using xlodbc.xla with Excel 2003
 

Hi Nicole,

It used to work but since upgrading to XP, the excel spreadsheet now keeps
coming with the above error. The odbc32.dll file is on the
C:\windows\system32 folder, I have saved and referenced the xlobdc.xla file
from Excel 2002 - but how to get it to register to the correct odbc32.dll now
that I have XP running?

Why do you need that xla? It is quite easy to connect to a database using ADO
from VBA.

Regards,

Jan Karel Pieterse
Excel MVP
http://www.jkp-ads.com
Member of:
Professional Office Developer Association
www.proofficedev.com

using xlodbc.xla with Excel 2003
 

Someone else wrote the macros - and I thought it would be easier to simply
re-map the reference add-in, than having to re-write their macros. But
instead - i can go and learn how ADO works instead, if Excel 2003 with XP is
no longer compatible with xlodbc.xla. Thanks

"Jan Karel Pieterse" wrote:

Hi Nicole,

It used to work but since upgrading to XP, the excel spreadsheet now keeps
coming with the above error. The odbc32.dll file is on the
C:\windows\system32 folder, I have saved and referenced the xlobdc.xla file
from Excel 2002 - but how to get it to register to the correct odbc32.dll now
that I have XP running?

Why do you need that xla? It is quite easy to connect to a database using ADO
from VBA.

Regards,

Jan Karel Pieterse
Excel MVP
http://www.jkp-ads.com
Member of:
Professional Office Developer Association
www.proofficedev.com

using xlodbc.xla with Excel 2003
 

Hi Nicole,

Someone else wrote the macros - and I thought it would be easier to simply
re-map the reference add-in, than having to re-write their macros.

Makes sense. You could start off by trying to run Office Setup again and
figure out whether the odbc addin has been setup. If thtat fails, there's
always ADO.

Regards,

Jan Karel Pieterse
Excel MVP
http://www.jkp-ads.com
Member of:
Professional Office Developer Association
www.proofficedev.com