Linked table manager (Access 2003) does not show any tables

This may or may not help:
http://support.microsoft.com/default.aspx?scid=kb;en-us;323658&Product=acc

try deleting an odbc linked table (just the link not the table!) and redo...see if that helps

If all else fails, try exporting everything to a new database and linking the tables again.  May be corrupt database.

you can unhide MSysObjects (tools options system objects) have a look for your links..are they there...

you could also try to copy the whole thing into a new mdb

> try deleting an odbc linked table (just the link not the table!) and redo...see if that helps

I did that yesterday and it did not make any difference.  I was thinking maybe that one table might show up, but still empty.  Sorry, should have mentioned that in my question!  I am going to check out the link supplied by shanesuebsahakarn now.

This link from shanesuebsahakarn...

http://support.microsoft.com/default.aspx?scid=kb;en-us;323658&Product=acc

...had to do with Oracle and Access 2000.  I even tried the registry hack suggested there, but it really didn't apply or make any difference.  I put it back the way it was.

As for the MSysObjects, the linked tables are in there and my database is not corrupt.  This problem is system-wide, that is, a computer with this problem shows an empty linked table manager in all databases, and we have a bunch.

Sorry to keep shooting down all these ideas!

Can you still access the linked tables?

Yes, the tables come up fine and the application works.  Of course we copy databases around from one developer's computer to the next, and to laptops and then need to refresh the links.  We also have end-users complaining about this.

Here's something really odd: If you ignore the fact that the linked table manager window is empty and click "select all" then "OK", the progress meter shows "Refreshing linked tables..." and the little boxes march across and then it says "all linked tables successfully refreshed".  If you check the box that says "always prompt for a new location", and select all and proceed, it allows you to browse to your ODBC connection, but when you let it rip you get:

Method 'List' of object '1FieldListWnd' failed

Pasting that into Google returns exactly one hit*.  That is where I got the ACCWIZ.DLL red herring.

Also, on a computer with this problem, using Access 2000 the tables are all there in the linked table manager.

* Isn't there a prize for that?

This certainly sounds like a corruption issue, and the fact that you have already reinstalled Office at least once leads me to believe it is something in the DB as well.  Have you tried making a copy of the DB and programmatically removing all the linked tables?  If you can remove all the linked tables, then use the normal methods of relinking one, and have that one show up in the DB window, then we know the culprit was a corrupted internal table.

I have many, many Access databases with linked tables on a network drive.  They all exhibit this behavior from a computer with the problem, but not from other comoputers that don't have the problem.  Same database; different behavior depending on the computer Access is running on.  Also, I have deleted the links and relinked and that doesn't make any difference.  Again, I don't think it can be in the database as the same database works fine from computers whose linked table manager works fine--or even from the screwed up computer if you use Access 2000 instead of Access 2003.

Have you installed all of the Office 2003 service packs?

Perhaps mis-matched versions of MDAC? You can run the Component Checker from MS to determine the version of MDAC installed on a "good" machine vs a "bad" machine.

Component Checker:
http://www.microsoft.com/downloads/details.aspx?FamilyID=8f0a8df6-4a21-4b43-bf53-14332ef092c9&displaylang=en

Service packs: About MS Access shows SP1 and I don't think there is another for 2003.  Also, I have been to Office Update and it says there are no updates for the bad computers.  Isn't that all I can do as far as SPs go?

MDAC: Does that apply on XP?  I thought that went away with Windows 2000 and beyond.  I'll run the checker, though, and report back.

Thanks for your perseverance!

Service packs - You certainly should update Access and Office, but those have nothing to do with MDAC - this is ENTIRELY separate and is not automatically updated.

MDAC: Yes, this applies to XP. MDAC is alive and well and is the root of many odd issues associated with Access, especially when dealing with linked tables to a SQL server. I really don't think this is your issue, however, but it's worth a look. Run the component checker - if nothing else, it'll eliminate at least one avenue of suspicion.

I ran the MDAC component checker.  The machine that does NOT work instantly reports: The following product releases were matched: MDAC 2.8 RTM (It's a Windows Server 2003 box.  We also have the problem on two XP SP2 machines but I won't have access to them for a couple of days (on a trip).)

On two where the linked table manager works properly cc.exe says: The following product releases were matched: UNKNOWN

Drilling down to the ODBC driver for SQL Server (SQLSRV32.dll) I find this version on the BAD box: 2000.85.1025.0 and...
...this version on the GOOD box: 2000.85.1117.0

Different OSs, however.  How in the heck do you update this?  Should I attempt it?

Sounds like that could be the version from the post 2.8 hotfix. Try downloading it from office.microsoft.com, and see if that fixes it (search for MDAC 2.8).

The MDAC 2.8 download I found* supports all OSs except the one I am using, in this case Windows Server 2003.

* http://www.microsoft.com/downloads/details.aspx?FamilyID=6c050fe3-c795-4b7d-b037-185d0506396c&displaylang=en

Can I update just the SQL Server ODBC Driver component somehow?  Is all this really likely to help?

Look here:
http://www.microsoft.com/downloads/details.aspx?FamilyID=39472ee8-c14a-47b4-bfcc-87988e062d91&DisplayLang=en

MDAC will need to be updated on your workstations rather than your server.

My Windows Server 2003 machine is an Application Server.  Access 2003 is the main application it serves up to remote users.  I'm going to install the security patch above on it.  I tried installing it on one of my good XP computers and it would not.  Complained it could not determine the current version of MDAC--just as cc.exe declared the version UNKNOWN.

I have tried all the suggestions posed here and I appreciate everyone's time.  Nothing helped, so I am not sure this entire thread needs to stay in the system.  I am going to ask the EE Overlords to remove it.  I will probably call Microsoft support to see what to do.
Thanks again!
Steve

might it not be worthwhile to paq and refund?  

if someone else runs across this problem, at least knowing that the only apparent answer is a call to MS...and if MS has an answer...the author could post here for...

just a thought...

I am on the phone with Arvid Saxena (Microsoft technical support).  Have been for one hour.  He is stumped but still working with me.  I'll keep you posted.
Steve

After three hours on the phone, we are pretty sure the problem is with computers with multiple versions of Access, usually.  Not only that, but the DLL "accwiz.dll" in particular, is at the heart of it.

I registered it using:
regsvr32.exe "C:\Program Files\Microsoft Office\Office11\accwiz.dll"
...on one of my computers with this problem and it fixed it.  It did not fix it on my main computer--a Windows Server 2003 running as an (Access 2003) Application Server.  It would not even let regsvr32 register the DLL.  MS sent me a new DLL and still no go on registering it.  Then MS sent me "regtlib.exe", which was able to register accwiz.dll, so that was cool!  Too bad the linked table manager is still empty.  :(

As for accwiz.dll, search the MSKB for 835519 for complete details.  My case is still open with Microsoft technical support, but I am not holding my breath.

As for removing this question from the EE, I think the new information regarding accwiz.dll could be a help to some people with this problem.  It fixed one out of three of my computers.  All the rest of our systems were OK anyway, so we know how to install Access.

Steve

I'm all for PAQ/Refund.  

geekboysteves: please keep us up-to-date on anything returning from MS on this issue.  I'd be quite interested in seeing a final resolution to this.

I agree, PAQ/refund is good.

I am running Access 2003 sp1 under Windows XP sp2 and am have exactly the same problem with the linked table manager. I have found no solution other than removing the older versions of Access.

HarrySanders5

HarrySanders5,
Are you running _Office_ 97/2000/2002 Pro and Access 2003 by any chance?  I mean, do you have Access 2003 as a stand-alone product possibly, installed after a full Office 2000 Pro, for example?  That is the configuration that I can't fix.  I need 2000 and 2003 on the same machine.  The linked table manager would be nice, but I have work-arounds.  Of course my installation is complcated by the fact that my computer is a Windows Server 2003 in Application Server mode...
GeekBoySteves

GeekBoySteves
When I originally had the problem I had Office Developer 2003 and Office 2002 runtime installed at the same time. I removed the 2002 runtime and the problem went away. Later I reinstalled 2002 full edition (developer) along with 2000 developer and the problem returned. The linked table manager seems to work fine with the older versions (2002 and 2000).

I no longer use Access 97, so it is unlikely I will need to install it.

HarrySanders5

Hi guys, I was just poking around for a bit trying to solve the same issue.  

My Access 2003 wouldn't even bring up a window for the Table Manager after I installed SP1.  I came across this post and registered  regsvr32.exe "C:\Program Files\Microsoft Office\Office11\accwiz.dll"

This got the Table Manager window to pop up but still no tables.

I then read you talking about different versions, and sure enough I have the 2002 Runtime installed.  
I uninstalled it and now I have the Table Manager with the tables in it.

-Air

MS called me at least three times before closing this issue.  Arvind (MS engineer) duplicated the problem on multiple computers including a Windows 2003 Server.  He found that if multiple versions of Access are installed in version order but to *different folders* (not all pointed to Program Files\Microsoft Office) and the accwiz.dll is registered, then the linked table manager works properly in 2003.

I have not been able to put this to the test on my production application server, but I take his word for it.  MS really bent over backwards on this issue, and they "refunded" my support call--so I still have a "free one" in the bank.

Steve

What about all our lost time trying to solve the issue, Microsoft looks all good that they helped, but their bug caused us all grief/time/money and they should be paying us to solve it for them. In return they outsourced the support to India.  

Please don't act like they did you a favor, you just solved a bug for them and they are letting you go without paying the tax, oh gee, thank you Microsoft.

" all pointed to Program Files\Microsoft Office"

this actually isn't a bug...you install any program over older versions you are going to get weird behaviour...if the thing works at all...I've installed A97, A2000 and A2002RT "in different folders" and not had any problems...and completely hosed one install by forgetting to change the default install folder...but that's MY problem...not MS's

i've seen all sorts of dll probs caused by multiple version installations... not just in access altho the wizards seem especially prone
to problems...

I would at least hope the Microsoft would program some logic into the install to not allow this to happen, but from a marketing approach I guess you could make more $$ if the program didn't do any checks and people had to call in for support.

By default, Access installs itself in different folders (Office10, Office11, etc). Is Microsoft saying that this is not adequate and that we need to install completely independent paths for different Access versions?

It is my understanding that the problem is exacerbated by installations of multiple versions with "Program Files\Microsoft Office\" in common.  The line of demarcation should be immediately after "Program Files".

As in:

\Program Files\MSO97
\Program Files\MSO2K
\Program Files\MSOXP
\Program Files\MSO2003

Steve

that's exactly my experience GBS...and with that setup...been no problems...except for the A97 No License bug (which is a true bug) which has an easy fix (the Haettenschweiler Font switcheroo)

I got this problem even though my installs are in different drives!
Office 97 Pro - C:\Program Files\Microsoft Office\Office
Office 2K3 Pro - F:\Program Files\Office2K\OFFICE11

Removing Access 97 fixed up the linked table manager (I'd already tried registering accwiz.dll to no avail).
However, I also have an install of Outlook 2002 in C:\Program Files\Office2K\Office10. Can't see why that would have an impact but it sounds like the only difference from MS's scenario.

It probably does not matter if they are installed to different places since some files go into the \Program Files\Common or the system directories.

answer plz