Windows 7 Forums Search
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find solutions with any problems, errors or issues you are experiencing with Windows 7. The Windows 7 forum also covers news and updates and has an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7 - Win7 x64 / Office 2010 - ODBC connect error

 
08-25-2010   #1


Windows 7 x64
 
 

Win7 x64 / Office 2010 - ODBC connect error

I have a MS Word application which uses a DSN-less connection to access a remote SQL database and which runs properly under a 32 bit OS. However, on my Windows 7 x64 systems with Office 2010 (32 bit) I get the following error when running the application:

[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified.

I have done a bunch of searching, and have found a number of suggested solutions. The one which seems most likely to work is to install the Office System Driver Data Connectivity Components 2010.

Is this the best approach for solving the problem? If so, should I install the 32 or 64 bit version? If this is not the best approach, what would you suggest?

Thank you.

My System SpecsSystem Spec
08-25-2010   #2
ryo


 
 


i don't try yet Ms office 2010.
but i think the work is same with the other Ms.office
i'm also run the excel and connected to the dbase using ODBC.
did you already add the dbase source in it?
My System SpecsSystem Spec
08-26-2010   #3


Windows 7 x64
 
 


I have learned more. Sadly, the problem does not seem to be limited to my Windows 7 x64 machine. I have tried this application on two different XP machine and have received the exact same error message. This is particularly baffling since the exact same application ran perfectly 12 months ago.

Here is the relevant VBA code:
PHP Code:
Dim cn As ADODB.Connection 
Dim cmd 
As ADODB.Command 
Dim rs 
As ADODB.Recordset 
 
Set cn 
= New ADODB.Connection 
cn
.ConnectionString "Driver={SQL Native Client};Server=<ip_address>;Database=<db>;Uid=<uid>;Pwd=<pwd>" 
cn.CursorLocation adUseClient 
cn
.Open 
 
Set cmd 
= New ADODB.Command 
Set cmd
.ActiveConnection cn 
cmd
.CommandText "sp_name" 
cmd.CommandType adCmdStoredProc 
cmd
.Parameters.Append cmd.CreateParameter("@Param"adCharadParamInput25"Value"
Set rs cmd.Execute 
I have also determined that the problem occurs before any data is transmitted to the remote server.

Since the application did not change - the date stamp on the .doc file is last August - I do not know what to look for in order to resolve the problem. Can anyone please suggest an approach?
My System SpecsSystem Spec
.


08-27-2010   #4
ryo


 
 


why don't u try the office 2007 or use the office 2003??
My System SpecsSystem Spec
08-31-2010   #5


W7 X-64 RTM,SUSE 11.1, XP PRO SP3 as a VM, VMware ESXi
 
 


Hi there
I'm trying a similar thing but using Office 2007 -- works perfectly and I'm on Windows 7 X64

My application is an EXCEL spreadsheet that retrieves data from a remote SQL DB and doesn't seem to have any probs.

I've got Office 2010 on a Virtual Windows 7 32 bit machine so I'll try that later --but of course running a Virtual Machine could add another layer of complexity into the mix.

Incidentally on a VIRTUAL W2003 server machine with Office 2007 the EXCEL application runs just fine so I suspect the deal is probably with Office 2010.

Did you use the ODBC software that the remote DB requires -- for example can you just do a basic Connect to the remote DB. in command mode and run any SQL queries.

This should tell you if you've got a problem with OBDC or not.

Another but possibly silly question -- has the remote DB changed its authentication procedures or updated ITS own software. If it has you might also need to apply some fixes on your front end.

Cheers
jimbo
My System SpecsSystem Spec
08-31-2010   #6
ryo


 
 


i'm usually use Ms.office 2003 and 2007 too. and until now didn't have any issue.

Last edited by ryo; 08-31-2010 at 04:07 AM.. Reason: typo
My System SpecsSystem Spec
08-31-2010   #7


W7 X-64 RTM,SUSE 11.1, XP PRO SP3 as a VM, VMware ESXi
 
 


Hi there
just tried a Virtual machine (Windows 7 X86) running Office 2010.

No problem --EXCEL application retrieves data perfectly.

I suspect that the DB software has changed so you need to update your front end accordingly.

There shouldn't be any problems with the OBDC -- perfectly standard protocol.bo

If you are running a JAVA or VB script relying on the .NET interface you could be in trouble as this has considerably changed in Windows 7 even from VISTA.

Cheers
jimb
My System SpecsSystem Spec
09-03-2010   #8


Windows 7 Professional x64
 
 


The default 64bit ODBC is not visible to 32bit applications on a x64 Windows.

For 32bit applications running on a 64bit Windows OS, use ODBC located at:
C:\Windows\SysWOW64\odbcad32.exe

You can add a shortcut to it to your Control Panel.

The 64bit & 32bit ODBC apps look exactly the same, but your DSN entries will not show in both, unless you enter them in both.
My System SpecsSystem Spec
09-03-2010   #9


W7 X-64 RTM,SUSE 11.1, XP PRO SP3 as a VM, VMware ESXi
 
 


Hi there
I forgot to mention that -- thanks for pointing it out.

Note that the MS office 2010 I've been using is the 32 bit version.

Cheers
jimbo
My System SpecsSystem Spec
Reply

 Win7 x64 / Office 2010 - ODBC connect error problems?



Thread Tools



Similar Threads for: Win7 x64 / Office 2010 - ODBC connect error
Thread Forum
Office 2010(Win7, 64bit) won't open Office 2007(WinXPr3 32 bit) files Microsoft Office
Win7 with office 2010 Installation & Setup
Office 2010 Pro Plus Win7 x 64 Excel reconfigures Office 2010 Microsoft Office
Office 2010 Gets Install Error Microsoft Office
Office 2010 32bit/x64 like Win7 keys? Microsoft Office


All times are GMT -5. The time now is 05:18 PM.



Windows 7 Forums is an independent web site and has not been authorized,
sponsored, or otherwise approved by Microsoft Corporation.
"Windows 7" and related materials are trademarks of Microsoft Corp.
© Designer Media Ltd
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30