>I'm trying to access a .dbc database on a Windows 64-bit machine. I can open some .dbc databases using VFP9 on my Windows7 64-bat machine. But database in particular will not allow my to use its tables. It gives me an error reading:
>"Connectivitey error: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified."
>
>I have tried to install a VFP ODBC driver using \Syswow64\ODBCad32.exe. It seemed to install ok. I added a path which points to the database I am attempting to use. However I still get the connectivitey error.
>
>Naturally, I must be able to access the database and its tables for ongoing work, and I am stumped.

If you're working in VFP9, using ODBC or OLEDB should not be necessary, it's just another layer of complication.

Simplest thing first: is it possible someone else is EXCLUSIVEly using the DBC or the table(s) you're trying to use?

So, are you saying:

* In VFP9:
SET EXCLUSIVE OFF
SET TABLEVALIDATE TO 0
USE SomePath\Table1inDBC1  && works
USE SomePath\Table2inDBC2  && doesn't work

Are you able to open the troublesome database (without opening any of its tables): OPEN DATABASE SomePath\TroublesomeDatabase.DBC

If that causes problems, back up the DBC, its related files, and related tables, index files and memos, then you can try OPEN DATABASE SomePath\TroublesomeDatabase.DBC VALIDATE. This can help in cases where the DBC stores hard-coded or relative paths to its member tables, and then everything gets moved to new folder(s).

If for some reason you feel you need to try ODBC or OLEDB, the former only supports database/table features up to VFP6, if the DBC or tables use anything newer than that it may not work. In that case you could try the OLEDB driver, which supports up to VFP9. http://www.microsoft.com/en-ca/download/details.aspx?id=14839

A great site for connection strings etc. is http://www.connectionstrings.com/