Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
DiscussionsAccessExcelInfoPathOutlookPowerPointPublisherWord
DirectoryUser Groups
Related Topics
Outlook ExpressInternet ExplorerWindowsMS Server ProductsMore Topics ...

MS Office Forum / Word / Programming / February 2006

Tip: Looking for answers? Try searching our database.

Automated form doesn't behave when opened as a template

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
CubeRat - 17 Feb 2006 00:26 GMT
Using Word 2000, I have an automated document (drop-downs and such, powered
by VBA code) that opens and runs fine when accessed via the File>Open
command. But some of my users copied this document into their template
directory (still with a "doc" extension) and are trying to open it from there
with the File>New command. It opens, but the drop-downs and checkboxes and
such work erratically. It looks like it's not executing some of the
macros/code.

Any clues why this would be different?
Signature

CubeRat

Cindy M  -WordMVP- - 21 Feb 2006 10:01 GMT
Hi =?Utf-8?B?Q3ViZVJhdA==?=,

> Using Word 2000, I have an automated document (drop-downs and such, powered
> by VBA code) that opens and runs fine when accessed via the File>Open
[quoted text clipped - 3 lines]
> such work erratically. It looks like it's not executing some of the
> macros/code.

Do you use an AutoOpen or Document_Open procedure to initialize things? Have you
used form fields from the Forms toolbar, or from the Control Box? If the latter,
and your code addresses these through the Thisdocument module or using
ThisDocument, that could be a reason (because "ThisDocument" would be the
originating template, not the document created from it).

Cindy Meister
INTER-Solutions, Switzerland
http://homepage.swissonline.ch/cindymeister (last update Jun 8 2004)
http://www.word.mvps.org

This reply is posted in the Newsgroup; please post any follow question or reply
in the newsgroup and not by e-mail :-)
CubeRat - 21 Feb 2006 23:00 GMT
I have an AutoOpen procedure, but all it does is throw a dialog box up that
explains the rules of using the form. I've used form fields from the Forms
Toolbar, not from the Control Box (where is the Control Box?).

Does the name of the form (.doc vs. .dot) make a difference?
Does the location of the form, or the method the user uses to open the form
make a difference?
Signature

CubeRat

> Hi =?Utf-8?B?Q3ViZVJhdA==?=,
>
[quoted text clipped - 19 lines]
> This reply is posted in the Newsgroup; please post any follow question or reply
> in the newsgroup and not by e-mail :-)
Cindy M  -WordMVP- - 28 Feb 2006 18:13 GMT
Hi =?Utf-8?B?Q3ViZVJhdA==?=,

> I have an AutoOpen procedure, but all it does is throw a dialog box up that
> explains the rules of using the form. I've used form fields from the Forms
[quoted text clipped - 3 lines]
> Does the location of the form, or the method the user uses to open the form
> make a difference?

I'm still waiting for a light-bulb to go off <sigh>

could you copy/paste a couple of the procedures into a reply that aren't working when
the user tries creating a NEW document instead of opening the document directly?
Perhaps that will give us a clue...

> > > Using Word 2000, I have an automated document (drop-downs and such, powered
> > > by VBA code) that opens and runs fine when accessed via the File>Open
[quoted text clipped - 9 lines]
> > ThisDocument, that could be a reason (because "ThisDocument" would be the
> > originating template, not the document created from it).

Cindy Meister
INTER-Solutions, Switzerland
http://homepage.swissonline.ch/cindymeister (last update Jun 8 2004)
http://www.word.mvps.org

This reply is posted in the Newsgroup; please post any follow question or reply in
the newsgroup and not by e-mail :-)

Rate this thread:






 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.