K
KR
If anyone has a code snippet that would be fine too, but I'm not opposed to
spending additional hours trying to wrestle this to death...I'm a slow
learner, but eventually brute force attempts get me something that works...
I had a template that worked fine on Win95 and Win98 (untested on Win2K).
When we were upgraded to XP, one of the things that broke was the
installation routine (tries to write to the template directory) and the
other thing that broke was my ability to create and append information to a
..txt file on the desktop, because in XP the desktop has a different path (I
was hardcoding the path before).
Given the numerous versions of both Win OS and Word that are all operating
now (I need to be backward compatible to Word97 on Win95, and upward to the
most current stuff) what is the most reliable method to identify where a
..dot should install itself (yes, I use a routine so if the activated dot is
_not_ in the template directory, it installs a copy of itself then closes)
and also to locate the path to the desktop of whatever machine it is on?
Many thanks,
Keith
spending additional hours trying to wrestle this to death...I'm a slow
learner, but eventually brute force attempts get me something that works...
I had a template that worked fine on Win95 and Win98 (untested on Win2K).
When we were upgraded to XP, one of the things that broke was the
installation routine (tries to write to the template directory) and the
other thing that broke was my ability to create and append information to a
..txt file on the desktop, because in XP the desktop has a different path (I
was hardcoding the path before).
Given the numerous versions of both Win OS and Word that are all operating
now (I need to be backward compatible to Word97 on Win95, and upward to the
most current stuff) what is the most reliable method to identify where a
..dot should install itself (yes, I use a routine so if the activated dot is
_not_ in the template directory, it installs a copy of itself then closes)
and also to locate the path to the desktop of whatever machine it is on?
Many thanks,
Keith