H
Howard Kaikow
Where's the documentation for the meaning of wdUserOptionsPath?
Al I see in the Help is the existence of the option, but no semantics.
Using Word 2003, I see the following behavior.
Depending on whether I run code directly from VBA or via automation in VB 6,
I get entirely different critters.
As I recall, I've see 3 different results, depending on how the code was
run.
1. ":\documents and settings\howard kaikow\application
data\microsoft\templates\templates2003", i.e., the directory in which the
Word template lives, when run in VBA.
2. :\WinNT\System32, when run in VB 6 design window or from a VB 6 compiled
..exe file.
3. My Documents, I saw this yesterday, but do not recall how the code was
run, as I recall it was in VBA.
All the other DefaultFilePath results are the same, no matter how I run the
code, other than wdUserOptionsPath and, as expected, wdCurrentFolderPath.
I would think that wdUserOptionsPath should refer to the same directory no
matter how the code is run.
Al I see in the Help is the existence of the option, but no semantics.
Using Word 2003, I see the following behavior.
Depending on whether I run code directly from VBA or via automation in VB 6,
I get entirely different critters.
As I recall, I've see 3 different results, depending on how the code was
run.
1. ":\documents and settings\howard kaikow\application
data\microsoft\templates\templates2003", i.e., the directory in which the
Word template lives, when run in VBA.
2. :\WinNT\System32, when run in VB 6 design window or from a VB 6 compiled
..exe file.
3. My Documents, I saw this yesterday, but do not recall how the code was
run, as I recall it was in VBA.
All the other DefaultFilePath results are the same, no matter how I run the
code, other than wdUserOptionsPath and, as expected, wdCurrentFolderPath.
I would think that wdUserOptionsPath should refer to the same directory no
matter how the code is run.