 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
| HomeDiscussionsAccessExcelInfoPathOutlookPowerPointPublisherWordDirectoryUser Groups Related Topics Outlook ExpressInternet ExplorerWindowsMS Server ProductsMore Topics ... |
MS Office Forum / Word / Numbering / October 2005Checking for List Numbering Bloat in the VBE
Hi All, When I try to check a document for list numbering bloat in the Visual Basic Editor, I get a message "Cannot execute immediate statement in design or run mode, or if the current thread has no stack frames". This occurs in all documents (but I swear it worked for me a few weeks ago). I'm sure there's a simple answer to this but can anyone give me a hint? Thanks, Caroline. Would you like to post your code so we can take a look at it?  SignatureChuck Henrich www.ProductivityApps.com > Hi All, > [quoted text clipped - 7 lines] > Thanks, > Caroline. Hi Chuck, The code I was using was from the knowledge base article 241581 about list template bloat in Word 2000 (yes I have Word 2000) - Type the following command in the Immediate Window and press ENTER: ?activedocument.listtemplates.count Cheers, Caroline. > Would you like to post your code so we can take a look at it? > [quoted text clipped - 9 lines] > > Thanks, > > Caroline. Hmm. The command works for me. I'm assuming that when you type the command in the Immediate window that no macros are running or in break mode. Just to check, do you get the error message if you open a blank document, open the VBE, open a module in Normal.dot, type the command in the Immediate window and press enter? Forgive me asking the obvious if that's what you've been doing but just thought I'd check. SignatureChuck Henrich www.ProductivityApps.com > Hi Chuck, > [quoted text clipped - 21 lines] > > > Thanks, > > > Caroline. Argh! I knew I was doing something silly! I was going into the script editor instead of VBE. (slaps forehead) Thanks Chuck. > Hmm. The command works for me. I'm assuming that when you type the command > in the Immediate window that no macros are running or in break mode. [quoted text clipped - 29 lines] > > > > Thanks, > > > > Caroline. You're welcome, glad the mystery's solved. SignatureChuck Henrich www.ProductivityApps.com > Argh! I knew I was doing something silly! > [quoted text clipped - 37 lines] > > > > > Thanks, > > > > > Caroline. |
Reply to this Message |
 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.