Hi mrl.lig and welcome to the forum.
Do you need the information on the indented lines as a single block of 'descriptive' text or for each line to be a separate record with separate fields?
The overlapping append approach should work relatively easily for the former but if you need the detail as detail life will be more interesting and, as you mentioned, complicated by the lack of extra detail in some places.
I think the real key to this one is knowing exactly what the output needs to look like and then deciding which of a number of different possible approaches seems the most likely to deliver the goods as efficiently as possible.
If you have data like:
And you need preserve Append 3 in your table somehow, you're going to need two models. One traps your details and appends normally, and exports to an Access file. Another just traps the Appends, then does a lookup to the Access file, and filters out all those Appends for which you ahve a match in the Detail. You then create some dummy Detail data for Append 3 using a calculated field, and export this adding it to the Access table.
Thanks for the feedback, I am attempting to capture as a complete descriptive text field, as stated it is difficult due to the varying size of this field. The intent is to capture all the itinerary data that each employee has for the air ticket. The problem that adds to this is there are sometimes non air ticket transactions which could be only one line in length (no indented data)
The second approach Olly mentioned is one I have considered but was trying to keep the process simple but if need be I can go that route