My problem has been solved. I think they key for me was to make sure that I was creating System DNS's for both the 32-bit and 64-bit odbc connections. When creating a User DNS it only allowed one odbc connection with the same name so when I created the 64-bit connection it over-wrote the 32-bit connection. It didn't do that when they were both System DNS's.
heh heh, no worries, there's a little "check accessibility" button right up under the Local menu item at the top.
I think he means that you have to configure the database itself with a username and password. To do that you open Access then open the database in Exclusive mode (click the drop-down menu next to the Open button and you'll see it). From there you can go into the File->Options and set the username and password.
However, it still doesn't work. No effect on the behaviour we're describing. When I test the connection in the DW Admin Tool it gives me an error that says "Cannot open connection: ERROR [IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified". Interestingly, when I set up a 32-bit ODBC connection to the same db it tests fine in the DW Admin Tool but it still can't see the tables.
Hi David, I also can't get an odbc connection to an Access database working and this is in a fresh DW7 installation. I just did a remote session with a DW tech and we tried 64-bit and 32-bit and though it's not giving the same error as you it's not seeing the tables in the db at all. At this point the DW tech is working on it on his end. I'll update here.
Does the Local Data Connector have to be installed on the same server as the database? If not, how far can it see? eg. does the db server have to be on the same network as the LDC or can it be a completely different cloud server?