WordBasic Commands That Are Invalid in Microsoft Binder

Last reviewed: February 5, 1998
Article ID: Q136384
The information in this article applies to:
  • Microsoft Word for Windows 95, version 7.0

SUMMARY

This article lists the WordBasic commands that are known to be invalid in Microsoft Binder. This list is generated using CommandValid. There may be additional invalid WordBasic commands that are not listed here.

MORE INFORMATION

Microsoft Word is an Multiple Document Interface (MDI) application, while its document object, Microsoft Binder, is not an MDI application. This will cause "CommandValid" to show some commands as available that may not work in WordMail. If you encounter one of these commands, the message dialog box will read:

   The <command name> command is not available because this document is
   in another application.

Below is a list of known invalid commands:

   ChooseButtonImage
   CountWindows
   CopyButtonImage
   DisableAutoMacros
   DocClose
   DocMaximize
   DocMinimize
   DocMove
   DocRestore
   DocSize
   DocSplit
   DocumentStatistics
   EditButtonImage
   FileFind
   FilePrintPreview
   FilePrintPreviewFullScreen
   FilePrintPreviewPages
   FileSaveAll
   FileSendMail
   FileSummaryInfo
   FileTemplates
   FormatAddrFonts
   HelpExamplesandDemos
   HelpQuickPreview
   HelpWordPerfectHelp
   HelpWordPerfectHelpOptions
   InsertDatabase
   InsertMergefield
   IsMacro
   Keymacro
   Lockdocument
   Magnifier
   MailMerge
   MailMergeAskToConvertChevrons
   MailMergeCheck
   MailMergeConvertChevrons
   MailMergeCreateDataSource
   MailMergeCreateHeaderSource
   MailMergeDataForm
   MailMergeDataSource
   MailMergeEditDataSource
   MailMergeEditHeaderSource
   MailMergeEditMainDocument
   MailMergeFindRecord
   MailMergeFirstRecord
   MailMergeFoundRecord
   MailMergeGoToRecord
   MailMergeHelper
   MailMergeInsertAsk
   MailMergeInsertFillIn
   MailMergeInsertIf
   MailMergeInsertMergeRec
   MailMergeInsertMergeSeq
   MailMergeInsertNext
   MailMergeInsertNextIf
   MailMergeInsertSet
   MailMergeInsertSkipIf
   MailMergeLastRecord
   MailMergeMainDocumentType
   MailMergeNextRecord
   MailMergeOpenDataSource
   MailMergeOpenHeaderSource
   MailMergePrevRecord
   MailMergeQueryOptions
   MailMergeReset
   MailMergeState
   MailMergeToDoc
   MailMergeToPrinter
   MailMergeViewData
   MenuMode
   NextWindow
   PrevWindow
   ResetButtonImage
   ResetNoteSepOrNotice
   SaveTemplate
   ToolbarButtonName
   ToolbarName
   ToolbarState
   ToolsCreateEnvelope
   ToolsCreateLabels
   ToolsCustomize
   ToolsCustomizeKeyboard
   ToolsCustomizeMenuBar
   ToolsCustomizeMenus
   WindowList
   WindowNewWindow
   DocumentPropertyExists
   DocumentPropertyName
   DocumentPropertyType
   GetDocumentProperty
   FilePost
   MailChecknames
   MailHideMessageHeader
   MailMessageDelete
   MailMessageForward
   MailMessageMove
   MailMessageNext
   MailMessagePrevious
   MailMessageProperties
   MailMessageReply
   MailMessageReplyAll
   MailSelectNames
   AutomaticChange
   HelpMSN

The following commands are valid, but their context activates Binder dialog boxes instead of Word dialog boxes. For example, when the command FileNew is used, it activates a dialog box that contains the Binder templates, not Word's templates. These commands are valid, but they may not produce the expected results within Microsoft Binder.

   FileClose
   FileCloseAll
   FileClosePicture
   FileExit
   FileNew
   FileNewDefault
   FileOpen
   FilePageSetup
   FilePreview
   FilePrint
   FilePrintDefault
   FilePrintSetup
   FileRoutingSlip
   FileSave
   FileSaveAs


KBCategory: kbusage
KBSubcategory: kbmacro
Additional reference words: 7.0 word95 winword word7 binder valid macro
wordbasic
command office
Keywords : kbmacro
Version : 7.0
Platform : WINDOWS


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: February 5, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.