Blank Linked Table Manager (repost)

[Al Camp]

Folks,
Sorry for reposting the same question in one day, but something weird is
going on. I can only see my post to this newsgroup by using Find.
(10/17/05 12:08PM) But, I can not locate it in the normal NG listing. (??)
Never seen that before, so I'm reposting just in case no one else can see it
either... very strange.
-------------------------------------------------------
I develop apps in 97, 2000, and 2003. Access 2000 is the culprit that
causes my 2003 Linked Table Manager to repoeatedly come up blank. Every
time I use 2000
it edits the reg entry to make Access use the 2000 ACCWIZ.DLL... so that
when I then go to 2003... the Linked Table screen is blank.

The RegSvr32 "fix" no longer works, but the RegEdit "fix" does.

My questions...

1. Is there a "permanent" fix for this problem? Will Microsoft ever fix
this? (I'm not holding my breath...)

2. Is there a way to create a .bat file that will automate the Regedit
process, so I don't have to wade through the registry each time, find the
correct registry item, and edit the value manually?

Any help/suggestions would be appreciated.

Thanks,
Al Camp
Candia Computer Consulting - Candia NH
http://home.comcast.net/~cccsolutions

 

[Dirk Goldgar]

Folks,
Sorry for reposting the same question in one day, but something
weird is going on. I can only see my post to this newsgroup by using
Find. (10/17/05 12:08PM) But, I can not locate it in the normal NG
listing. (??) Never seen that before, so I'm reposting just in case
no one else can see it either... very strange.
-------------------------------------------------------
I develop apps in 97, 2000, and 2003. Access 2000 is the culprit that
causes my 2003 Linked Table Manager to repoeatedly come up blank.
Every time I use 2000
it edits the reg entry to make Access use the 2000 ACCWIZ.DLL... so
that when I then go to 2003... the Linked Table screen is blank.

The RegSvr32 "fix" no longer works, but the RegEdit "fix" does.

My questions...

1. Is there a "permanent" fix for this problem? Will Microsoft ever
fix this? (I'm not holding my breath...)

2. Is there a way to create a .bat file that will automate the
Regedit process, so I don't have to wade through the registry each
time, find the correct registry item, and edit the value manually?

Any help/suggestions would be appreciated.

Al, I haven't encountered the problem you're talking about, though I've
heard of it and read the KB article (some time ago). I don't know if
there's some permanent fix for it. As for your second question, though,
IIRC you should be able to export the correct registry key or subtree to
a .reg file, and later just double-click on that file to restore the
registry items embodied in the file.

 

[Al Camp]

Al, I haven't encountered the problem you're talking about, though I've
heard of it and read the KB article (some time ago). I don't know if
there's some permanent fix for it. As for your second question, though,
IIRC you should be able to export the correct registry key or subtree to
a .reg file, and later just double-click on that file to restore the
registry items embodied in the file.

--
Dirk Goldgar, MS Access MVP
www.datagnostics.com

(please reply to the newsgroup)

Dirk,
There's a whole bunch of posts regarding this annoying bug. I even have
a .doc file on my website that helps beginner's apply the 2 fixes suggested
by Microsoft.
It would appear that 2000 and 2003 were not given seperate Reg entries to
point to their respective ACCWIZ.DLL files, so whenever 2000 runs, it alters
the Reg entry to it's path, and then 2003 tries to use that reg entry...
thus the bug.
97 does not cause this problem... I would bet it has it's own Reg entry
for locating it's own ACCWIZ.DLL.

I'm very familiar with .bat files, but I don't know how to address or
apply a registry change using that vehicle.to a .reg file
I'll try Googling to find out how I might do that, but could you direct
me to any resources on how that might be accomplished?

I have a lot of work coming up that will involve using both 2000 and
2003 almost daily, so I need to be able to develop an easy method to
overcome this problem.

As always... thanks Dirk.

Al Camp
Candia Computer Consulting - Candia NH
http://home.comcast.net/~cccsolutions

 

[Al Camp]

Al, I haven't encountered the problem you're talking about, though I've
heard of it and read the KB article (some time ago). I don't know if
there's some permanent fix for it. As for your second question, though,
IIRC you should be able to export the correct registry key or subtree to
a .reg file, and later just double-click on that file to restore the
registry items embodied in the file.

Dirk,
I'll also try the XP newsgroup... I'll bet they can get me going in the
right direction...
Thanks,
Al Camp