WD97: Word Solution Migration Information on the Web

Last reviewed: February 11, 1998
Article ID: Q163734
The information in this article applies to:
  • Microsoft Word 97 for Windows

SUMMARY

Resources for Migrating WordPerfect Macros to Word 97 as well as additional Word 97 solution migration papers are available on the Office Developer Forum.

Connect to the Office Developer Forum using the following Web address:

   http://www.microsoft.com/officedev

MORE INFORMATION

Solutions migration information for all of the Microsoft Office applications available on the Office Developer Forum Migration page can be found at the following Web address:

   http://www.microsoft.com/OfficeDev/

Converting WordPerfect Macros to Visual Basic for Applications

This white paper describes the methodology, approach, and requirements for converting macros developed for various versions of WordPerfect to Visual Basic for Applications in Microsoft Word 97. See the following Web site at:

   http://www.microsoft.com/WordDev/

WordPerfect 5.1 Macro Text Extractor

WordPerfect 5.1 for MS-DOS uses a proprietary file format for storing macros. This macro-to-text utility converts macros written for WordPerfect 5.1 to standard text for viewing and printing.

   Web site at: http://www.microsoft.com/WordDev/

NOTE: The utility does not translate WordPerfect macro code to Visual Basic for Applications.

Additional Word Solution Migration Papers

The following papers are also available for developers creating solutions in Microsoft Word 97.

   WordBasic Migration to Visual Basic for Applications:

   In Microsoft Word 97, WordBasic code is automatically migrated to
   Visual Basic. This white paper explains the conversion process, many of
   the known conversion issues, and solutions to resolve conversion
   issues.

   WordBasic to Visual Basic for Applications Conversion Table:

   Excerpted from the online Help file found in Office 97, this conversion
   table provides a quick reference guide for Microsoft Word developers to
   locate the Visual Basic for Applications equivalent of WordBasic
   commands.

   Microsoft Word Objects:

   This chapter from the Microsoft Office 97/Visual Basic Programmer's
   Guide talks about the objects available in Word 97. The Programmer's
   Guide is included with Microsoft Office 97, Developer Edition.

   Switching from WordBasic:

   This appendix from the Microsoft Office 97/Visual Basic Programmer's
   Guide talks about switching from WordBasic to Visual Basic for
   Applications. The Programmer's Guide is included with Microsoft Office
   97, Developer Edition.

   Updating String Functions in WLLs and DLLs for Word 97:

   Visual Basic requires external libraries to use BSTR values in string
   -related functions. If you've written 32-bit Word add-in libraries
   (WLLs) or dynamic-link libraries (DLLs) that you need to use or support
   in Word 97, you need to modify any string-related functions in your
   library and recompile it. This paper describes the steps for updating
   those functions in your source files to avoid errors when the functions
   are called from Visual Basic.

   Updated WbODBC.wll Available:

   If you've written Word 95 solutions that use the ODBC functions in
   WbODBC.wll (a Word add-in library available in the Microsoft Word
   Developer's Kit, 3rd edition), you'll need to install this updated
   version of the WLL to run your solution in Word 97. In addition to a
   new version of the WLL, this download also includes new versions of the
   sample ODBC macros template (WbODBC97.dot) and the corresponding test
   database (Test.mdb). The macros in WbODBC97.dot have been updated to
   use Visual Basic and demonstrate how to use the ODBC add-in functions
   successfully in Word 97. For complete information about this update,
   see the Readme.txt file included in this download.

   Download WbODBCwl.exe (83K; expands to 224K)

   Connect to the Additional Word Solution Migration Papers using the
   following Web address:

   http://www.microsoft.com/OfficeDev/

The following articles answer some frequently asked questions and can help you get started in developing your custom solutions in Visual Basic for Applications. To obtain any of these articles, search on the Q number (that is, the identification number or ARTICLE-ID number) that is associated with each of the following articles. If you are viewing this article online, the ARTICLE-ID number is a hyperlink to the article.

   ARTICLE-ID: Q162191
   TITLE     : Article List: Microsoft Word 97 Automation and Programming

Other Web Resources

   Developer Resource Central at the following Web address:

   http://www.microsoft.com/msdn/default.htm

   Visual Basic Online Developer (from Pinnacle Publishing Inc.) at
   the following Web address:

      http://www.pinpub.com/vbd/

   Microsoft Access 97 Expert Solutions--Online Version at the following
   Web address:

      http://www.mcp.com/44580646959077/que/developer_expert/access97es/

   Visual Basic 4 Expert Solutions--Online Version at the following Web
   address:

      http://www.mcp.com/44580646959077/que/developer_expert/vbexsol/

   Visual Basic Resource Center at the following Web address:

      http://www.mcp.com/que/vb4/


Additional query words: 97 word8 word97 8.0 8.0 vb vbe vba
Keywords : kbwordvba kb3rdparty kbfaq kbprg
Version : 97
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 11, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.