Using your dB from Post #3, I exported a record after writing code to sent the data to a text file from your query.
*** Start Order ***
EXTERNALORDER1: PO83160
DATEEXTERNAL1: 06/8/20
ADDRESSCOMP: name name
ADDRESS1: xxx COUNTY RD G
ADDRESSCITY: BRYAN
ADDRESSSTATE: OH
ADDRESSZIP: 43506
ADDRESSCOUNTRY: US
NOTESTOACCOUNTING: IMPERIAL PO83160
SHIPMETHOD: UPS THIRD PARTY
*** End Order ***
*** Start Customer ***
EXTCUSTOMERID: 961
COMPANY: IMPERIAL
*** End Customer ***
*** Start Product ***
PARTNUMBER: CA2015025-M
Quantity: 1
SIZE1: 0
SIZE2: 0
SIZE3: 1
SIZE4: 0
SIZE5: 0
SIZE6: 0
*** End Product ***
IDORDERTYPE: 21
Obviously, the dB I downloaded is not your "real" dB since there are fields missing in the dB you posted. So I used the SQL from the saved query "ORDERQRY" and added a WHERE clause.
While testing the code, there was/is a problem with the calculation for "Size6" - it returns #Error, so I removed the calculation and substituted a 0.
You do not have a PK field so I used the field "EXTERNALORDER1" to select the record to export. What should happen if you have 2 or more records with the same "EXTERNALORDER1"?
Any field where the data is NULL/missing/Blank is NOT written to the text file.
Just playing around to show have you can use VBA to write to a text file.
Is this close to what you want?