Hi Howard,
There isn't presently a method or tool for moving
an Office 2003 Local Install Source folder (\MSOCache)
and Repair may not accurately recreate it apparently
A. Was the original \MSOCache folder on your L drive?
B. In what way was the 'new' (repaired) \MSOCache folder
different from the original one?
C. FYI - The Local Install Source (LIS) folder must be off
of the drive root (i.e. it can't be in a subfolder).
D. Interesting that the uninstall found both \MSOCache
folders. Note that they can also be removed
(danger-danger-will-robinson) by using the Disk Cleanup
tool in Start=>(All)Programs=>Accessories=>System Tools
if pointed to a drive that contains the LIS.
E. During setup you can 'choose' a preferred drive using
the property or setup parameters but the drive needs
to have 1.5gb free on it for the request to be honored.
On your #6, I'm not sure I'm following the tie in for
LIS and Office VBA help and MS Visual Basic (from Visual Studio?)
=======
I tried running a detect and repair and noticed the following.
1. All the entries of which I am aware for MSOCache in the registry
reference the K drive.
2. When I did the repair, another MSOCache was created on the L drive, but
directory was not structured the same as the original one on L, which I had
moved to K.
3. I also realized that I was asleep when I did the original install and did
a Custom, not a Complete, install, so I yelled Uncle and uninstalled, then
re-installed Office 2003, allowing MSOCAche to be put on L.
4. I noted that uninstall removed all the registry entries referencing AND
deleted the MSOCache on BOTH K and L.
This did not remedy the problem of missing VBA Help when automating from VB
6. >>