Writing to an external file

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Why, when using a write statement to an external file opened in append mode, do I get quotation marks surrounding what I've written? Is there any way to suppress this?

Thank you so much in advance, you guys have perfectly answered my every question.
 
Mark Wipf said:
Why, when using a write statement to an external file opened in
append mode, do I get quotation marks surrounding what I've written?
Is there any way to suppress this?

Thank you so much in advance, you guys have perfectly answered my
every question.
Click to expand...

As the help-file entry for the Write statement says, the Write statement
formats the output so that it can be read back in using the Input
statement. That includes, among other things, putting quotes around
string values and inserting commas between the items written. If you
want to avoid this you should probably use the Print statement instead.
 
-----Original Message-----
Why, when using a write statement to an external file
Click to expand...
opened in append mode, do I get quotation marks
surrounding what I've written? Is there any way to
suppress this?
Thank you so much in advance, you guys have perfectly answered my every question.
.
Click to expand...
Hi Mark,

try this... use tools|references to set a reference to
microsoft scripting runtime.

use the object browser to lookup in the scripting library,
file.OpenAsTextStream

This will possibly give you a bit more control and some
other nice goodies not available in the microsoft office
library.

Luck
Jonathan
 
Jonathan Parminter said:
opened in append mode, do I get quotation marks
surrounding what I've written? Is there any way to
suppress this?
Hi Mark,

try this... use tools|references to set a reference to
microsoft scripting runtime.

use the object browser to lookup in the scripting library,
file.OpenAsTextStream

This will possibly give you a bit more control and some
other nice goodies not available in the microsoft office
library.
Click to expand...

But why add all that extra overhead and an extra reference to be
potentially broken, for no more function than is easily available with
the intrinsic VBA I/O statements?
 
Back
Top