WD98: Print # Statement Separates Fields with Spaces, Not Tabs (183311)


The information in this article applies to:

  • Microsoft Word 98 Macintosh Edition
This article was previously published under Q183311

SYMPTOMS

When 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.

CAUSE

The 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.

RESOLUTION

Microsoft provides programming examples for illustration only, without warranty either expressed or implied. This includes, but is not limited to, the implied warranties of merchantability or fitness for a particular purpose. This article assumes that you are familiar with the programming language that is being demonstrated and with the tools that are used to create and to debug procedures. Microsoft support engineers 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 requirements. 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: 
   Sub MAIN
      ' Define the variables.
      item1$ = "item1"
      item2$ = "item2"
      item3$ = "item3"
      item4$ = "item4"
      ' Open the file for output.
      Open "Macintosh HD:DeskTop Folder:Test.txt" For Output As #1
      ' Print to the output file.
      Print #1, item1$, item2$, item3$, item4$
      ' Close the output file.
      Close #1
   End Sub
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: 
   Print #1, item1$ & vbTab; item2$ & vbTab; item3$ & vbTab; item4$

STATUS

Microsoft 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."

NOTE: If the Assistant is hidden, click the Office Assistant button on the Standard toolbar. If the Assistant is not able to answer your query, please see the following article in the Microsoft Knowledge Base:

176476 OFF: Office Assistant Not Answering Visual Basic Questions

NOTE: 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:

181394 WD98: Writing Macro Code for VBA and WordBasic Branching

For additional information, please see the following article in the Microsoft Knowledge Base:

181058 OFF98: How to Run Sample Code from Knowledge Base Articles

REFERENCES

For more information about getting help with Visual Basic for Applications, please see the following article in the Microsoft Knowledge Base:

163435 VBA: Programming Resources for Visual Basic for Applications

Modification Type:MajorLast Reviewed:6/17/2005
Keywords:kbbug kbdtacode kbmacroexample kbpending KB183311
©2004 Microsoft Corporation. All rights reserved.