ODBC "link table" dialog box immediately disappears in Access 2003

  • I am attempting to create an ODBC link to a SQL 2005 table from Access 2003.  I have already created the file dsn.  When I try to USE the file dsn in Access (via the menu selections File, Get External Data, Link Tables) as soon as I click on the drop-down selection "ODBC Databases ()", the dialog box immediately closes.  It does not even allow me to point to the dsn.

    None of the other file types in the drop-down list cause this behavior.

    Any ideas of what could cause this to happen?

    Thanks,

    Ken Wells.

     

     

  • Does Access 2003 have the latest service pack applied ?(To rule out some possible bugs)

  • Yes, it is up to date.

    Thanks for the suggestion, though.

     

  • Have you found any info in the windows error log? (start->execute->eventvwr)

  • Did you ever find the solution to your problem?  I'm having the same issue.

  • Have you tried adding your dsn to ODBC Data Source Administrator on the "File DSN" tab under from the control panel?  That may help.

  • Here is some code to link a table.  Won't fix your problem but may get you past it.

    Function linkdata(tablename,dsnname)

        DoCmd.TransferDatabase acLink, "ODBC", "ODBC;DSN=" & dsnname & ";;TABLE=" & tablename, acTable, tablename, tablename, False

       

    End Function


  • Problem solved.

    Norton Anti-Virus seems to be the culprit here.

    If you disable the Office Plug-in, the ODBC Administrator window will open correctly.

    How to disable the Office Plug-in:

    1. Open Norton AntiVius

    2. Select Options, Norton AntiVirus

    3. In section Other, select Miscellaneous

    4. Unselect Turn Office Plug-in on

    Thanks for all your input.

    Rick Pearson

  • Thanks all for the good info.  I have not tried the Norton Anti-Virus solution, but I bet that's the answer.  I have Norton Anti-Virus installed.  I will try the solution and see what happens.

     

    Thanks again,

    Ken Wells.

  • Thanks for the info here. Hit the same problem, and yes, it was Norton. Incidentally, it was only a problem after I had installed Office SP3, previously this had worked OK.

Viewing 10 posts - 1 through 9 (of 9 total)

You must be logged in to reply to this topic. Login to reply