The information in this article applies to:
SYMPTOMSWhen you use the WordBasic Print statement with commas to send tab-delimited output to a text file, the text is no longer separated by tabs when you convert and run the macro in Visual Basic for Applications. CAUSEThe Print statement in WordBasic differs from the equivalent Print # statement in Microsoft Visual Basic for Applications. In Visual Basic for Applications, you need to specify the separator by using the vbTab constant. RESOLUTIONMicrosoft provides programming examples for illustration only, without warranty either expressed or implied, including, but not limited to, the implied warranties of merchantability and/or fitness for a particular purpose. This article assumes that you are familiar with the programming language being demonstrated and the tools used to create and debug procedures. Microsoft support professionals can help explain the functionality of a particular procedure, but they will not modify these examples to provide added functionality or construct procedures to meet your specific needs. If you have limited programming experience, you may want to contact the Microsoft fee-based consulting line at (800) 936-5200. For more information about the support options available from Microsoft, please see the following page on the World Wide Web: http://www.microsoft.com/support/supportnet/refguide/The following converted WordBasic sample code outputs the variables (item1$,item2$, and so on) to a text file with the print fields separated by tab characters:
In Visual Basic, the same sample code prints the fields separated by spaces. To work around this problem, use the vbTab constant, as in the following statement:
STATUSMicrosoft is researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available. MORE INFORMATION
For more information about Print # Statement, from the Visual Basic Editor,
click the Office Assistant, type print to a file, click Search, and then
click to view "Print # Statement."
Q176476 OFF: Office Assistant Not Answering Visual Basic QuestionsNOTE: If your programming language was written to call WordBasic commands, and you are anticipating interacting with the Microsoft Word Visual Basic for Applications language for all future development needs, you should convert your code from WordBasic to Microsoft Word Visual Basic for Applications. For additional information, please see the following article in the Microsoft Knowledge Base: Q163618 WD97: Writing Macro Code for VBA and WordBasic BranchingFor additional information, please see the following article in the Microsoft Knowledge Base: Q173707 OFF97: How to Run Sample Code from Knowledge Base Articles REFERENCESFor more information about getting help with Visual Basic for Applications, please see the following article in the Microsoft Knowledge Base: Q163435 VBA: Programming Resources for Visual Basic for Applications Additional query words: wordcon vb vba vbe conversion converting
Keywords : kbdta kbdtacode kbmacroexample word8 CnvVerDif word97 |
Last Reviewed: October 21, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |