Access Database fails to allow ODBC connection

[RichT]

I have just installed on my PC Access 2003 - currently SP2. I have also installed an Ingres ODBC set of drivers which work fine using a VB5 program that I wrote and execute on the same PC.

I am trying to connect from my Access database through ODBC to another RDBMS (Ingres). After I create my ACCESS database I want to import the data from my Ingres database into my Access database. To do this I have gone to the File --> Get External Data -->Import. At this time the import screen opens. I change the "Files of Type:" to "ODBC Databases()" the Import window closes, with no error message and I do not get the "Select Data Source" window. I am back in Access but no ODBC connection.

When I originally installed Access (as part of MS Office Professional on CD) I upgraded to SP2. When the problem described above occurred I uninstalled Access and reinstalled it with all options but did not upgrade to SP1 trying to reduce the number of variables.

Is there something in the Access application which I must configure to have it connect to the ODBC Data Source window? If no is there a log file or something else that I can look at to help me diagnose what is happening?

Thanks

[MMcCarthy]

Have a look on the Ingres website for an odbc driver for Access. I've never used Ingres but I had a similar problem with MySQL some years ago and I think that solved it.

I have just installed on my PC Access 2003 - currently SP2. I have also installed an Ingres ODBC set of drivers which work fine using a VB5 program that I wrote and execute on the same PC.

I am trying to connect from my Access database through ODBC to another RDBMS (Ingres). After I create my ACCESS database I want to import the data from my Ingres database into my Access database. To do this I have gone to the File --> Get External Data -->Import. At this time the import screen opens. I change the "Files of Type:" to "ODBC Databases()" the Import window closes, with no error message and I do not get the "Select Data Source" window. I am back in Access but no ODBC connection.

When I originally installed Access (as part of MS Office Professional on CD) I upgraded to SP2. When the problem described above occurred I uninstalled Access and reinstalled it with all options but did not upgrade to SP1 trying to reduce the number of variables.

Is there something in the Access application which I must configure to have it connect to the ODBC Data Source window? If no is there a log file or something else that I can look at to help me diagnose what is happening?

Thanks

[RichT]

Thanks but Access will not let me get to any ODBC driver. I even created a system DSN for an Access database and I have the same problem. When I click on "ODBC Databases()" Access does not take me to the "Select Data Source" window so it does not look like I am even getting to ODBC at all.

[MMcCarthy]

Thanks but Access will not let me get to any ODBC driver. I even created a system DSN for an Access database and I have the same problem. When I click on "ODBC Databases()" Access does not take me to the "Select Data Source" window so it does not look like I am even getting to ODBC at all.

As a test instead of importing try to link to the odbc, do you get the options here?

Mary

[RichT]

I have tried linking and I get the exact same behavior

[nico5038]

Looks an Office problem to me.
First try a repair and when still failing uninstall Office completely and reinstall :-(

Nic;o)

[RichT]

Thanks everyone for trying to help me. I found the problem. In addition to MS Office Professional installed I also had Norton System Works and Norton personnal Firewall installed. When I uninstalled the Norton applications my Access ODBC import started working.

Thanks again.

[MMcCarthy]

Thanks everyone for trying to help me. I found the problem. In addition to MS Office Professional installed I also had Norton System Works and Norton personnal Firewall installed. When I uninstalled the Norton applications my Access ODBC import started working.

Thanks again.

I new Norton had caused other conflicts but this is the first time I've heard of this one. I'll have to make a mental note of that.

Thanks for letting us know RichT

Mary