Here's more info:
1. The WinNT directory on drive J is dated 8/20/2003 10:00, so I guess that
is when I did the clean install of Win 2000 on J.
2. J:\Program Files\Common Files\Microsoft Shared\Office11 is dated
10/24/2003 14:31, which is when I installed Office 2003.
3. J:\Program Files\Common Files\Microsoft Shared\Office10 is dated
8/21/2003 19:14..
4. I installed VS .NET 2003 on K to save space on the J drive. K:\Program
Files\Microsoft Visual Studio .NET 2003 is dated 8/21/2003 19:09, so I
expect that J:\Program Files\Common Files\Microsoft Shared\Office10 was
created during the install of VS .NET 2003. This solves part of the mystery.
However, it does not explain why the COM object reference points to
G:\Program Files\Common Files\Microsoft Shared\Office10 instead of
J:\Program Files\Common Files\Microsoft Shared\Office10.
There is the implication that something searched ALL the drives and
determined that G:\Program Files\Common Files\Microsoft Shared\Office10 was
more up to date than J:\Program Files\Common Files\Microsoft
Shared\Office10. I sure hope not, but that's what it looks like.
I'm wondering what will happen if there is ever an update to VS .NET 2003
that needs to update the files in J:\Program Files\Common Files\Microsoft
Shared\Office10. Will it instead/also update the files in G:\Program
Files\Common Files\Microsoft Shared\Office10? I sure hope not as that might
break the Office XP installation in the OS on G.
--
http://www.standards.com/; See Howard Kaikow's web site.