You can also use vbVerticalTab and vbFormFeed. Any of the named constants will be more efficient than the slow Chr$() or slower Chr() functions.

But using any control character as a field delimiter suggests the resulting file (if indeed a file is the goal here) doesn't need hand editing by users. In that case there are many alternatives that will either be faster, more flexible, or both. Splits and concatenations tend to be pretty slow and clunky.

You could use UDTs and record I/O, Jet MDBs, Jet's Text IISAM (which can handle escaping quotes for you), dBase/FoxPro "free tables" via Jet's IISAMs or a VFP Provider, persisted ADO Recordsets, PropertyBags, ... the list ges on and on.