Autoexec does not seem to work any longer

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

dave.cuthill@computalog.com - 02 Oct 2007 00:19 GMT

I have used the instructions (on the attached link) to create a
application event procedure in the past for windowselection change and
it worked well to allow me to determine when I moved into and out of a
table. I have now been upgraded to Word 2003 and find that the
procedure does not work that same - specifically the autoexec. What do
I need to change to get this to continue to work?

http://www.word.mvps.org/FAQs/MacrosVBA/AppClassEvents.htm

David

Reply to this Message

Jean-Guy Marcil - 02 Oct 2007 04:41 GMT

dave.cuthill@computalog.com was telling us:
dave.cuthill@computalog.com nous racontait que :

> I have used the instructions (on the attached link) to create a
> application event procedure in the past for windowselection change and
[quoted text clipped - 4 lines]
>
> http://www.word.mvps.org/FAQs/MacrosVBA/AppClassEvents.htm

What is the code you have in your AutoExec macro?
Do you have simply
Set oAppClass.oApp = Word.Application
but it does not fire?

Signature

Salut!
_______________________________________
Jean-Guy Marcil - Word MVP
jmarcilREMOVE@CAPSsympatico.caTHISTOO
Word MVP site: http://www.word.mvps.org

Reply to this Message

dave.cuthill@computalog.com - 02 Oct 2007 14:00 GMT

Yes that is correct. If I run the autoexec after opening the file the
other code runs fine. At this point I think that I might abandon the
autoexec and find some other method of getting the Set oAppClass.oApp
= Word.Application to be executed (maybe a button or something).

> dave.cuth...@computalog.com was telling us:
> dave.cuth...@computalog.com nous racontait que :
[quoted text clipped - 20 lines]
> jmarcilREM...@CAPSsympatico.caTHISTOO
> Word MVP site:http://www.word.mvps.org

Reply to this Message

dave.cuthill@computalog.com - 02 Oct 2007 16:24 GMT

I think maybe it makes more sense to call the autoexec from the
document_new or document_open in the thisdocument area. This seems to
work better over all. Maybe I am misusing the autoexec.

On Oct 2, 7:00 am, dave.cuth...@computalog.com wrote:

> Yes that is correct. If I run the autoexec after opening the file the
> other code runs fine. At this point I think that I might abandon the
[quoted text clipped - 14 lines]
>
> > What is the code you have in your AutoExec macro?

> > Do you have simply
> > Set oAppClass.oApp = Word.Application
[quoted text clipped - 9 lines]
>
> - Show quoted text -

Reply to this Message

Jean-Guy Marcil - 03 Oct 2007 05:48 GMT

dave.cuthill@computalog.com was telling us:
dave.cuthill@computalog.com nous racontait que :

> I think maybe it makes more sense to call the autoexec from the
> document_new or document_open in the thisdocument area. This seems to
> work better over all. Maybe I am misusing the autoexec.

AutoExec executes when Word is launched, not when a document is opened while
Word is already opened.
And, if Word is used in Outlook, and Outlook is already opened, depending on
the Office version, you will run into all kinds of problems.

Signature

Salut!
_______________________________________
Jean-Guy Marcil - Word MVP
jmarcilREMOVE@CAPSsympatico.caTHISTOO
Word MVP site: http://www.word.mvps.org

Reply to this Message