Startup path weirdness

M

Mark Tangard

If I place the identical template in 2 folders and alternately designate
one or the other as Word's Startup folder, I get an error with the
following line of code *IF* the Startup folder's path has a period in it
as shown below. The first example runs normally; the second says the
member of the collection doesn't exist (irrelevant components shortened
for visibility):


Templates("C:\DocsSettgs\JDoe\AppData\Msoft\Word\Startup\GlobalTpt.dot"). _
AutoTextEntries("xyz").Insert Where:=Selection.Range -> RUNS
NORMALLY


Templates("C:\DocsSettgs\JDoe.ABC\AppData\Msoft\Word\Startup\GlobalTpt.dot").
_
AutoTextEntries("xyz").Insert Where:=Selection.Range -> THROWS ERROR

(Looping thru both the Templates collection and the AutoTextEntries
collection means reveals that this msg means the former. That is,
templates in the JDoe.ABC hierarchy aren't returned as members of the
Templates collection -- even though I've changed the Startup path to
point there, and closed & reopened Word.)

Now the kicker: This code runs fine on all our other machines,
*regardless* of which path is used for the Startup. All machines run
WinXP and Word 2007 (same license even).

I'll be the first to concede periods in folder names are strange, but
that's our IT guys' scheme, not mine. (The ABC in the examples above is
where our company name appears, and we're told that serves some purpose
for them.) Any idea what's going on?

MT
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top