Perhaps you could create a "dummy" record with just the text/values you need for export. You could either script the creation/deletion of this record for each export, or "hide" it from the user when not exporting and just update it prior to each export.
You would set things up so that this record sorts to the bottom of your found set.
I say "perhaps" because the design/uses of your table may make this suggestion impractical.
I've acheived something similar, but it requires using 'Export Field Contents...' instead of just 'Export...'. You'll need to build the export file record-by-record, field-by-field, using the ¶ symbol to separate lines, and using a copied tab character, or comma, as the delimiter. Create a global field in your table, and a script to loop through the records, adding the fields to the global, and finishing by adding the ¶ "T " & get ( foundcount). Then export the contents of this field.
Dog Savior wrote:
The export file is a flat text file which I created by concatenating all my fields together and exporting the one field in a tab delimited file.
The best way to do this is export as XML, with a custom XSLT stylesheet. The stylesheet can concatenate your fields, add header and/or trailer, even count your records - all this without adding any overhead to your file.
Building the entire file in a global field and exporting it using Export Field Contents… is also possible - but keep in mind that the exported file will be UTF-16 encoded, which the target application may not be able to handle.
Finally, you could import your records into a temp table, and add a dummy record there (the idea of adding a dummy record to your real data makes me shudder).