>>>>>Just think of a big bunch of text with "MSH" and "EVN" imbedded at the beginning of lines. MSH means the first line of a message and a new record is appended. EVN (and any other following headers) mean that information needs to be populated into the new record. I do not have the luxary of putting triggers on this table, so it needs to be done in the code. When a message has finished I need to be able to say, "Cool, it finished. Let's send something back telling the sender it went well." Then onto the next message in the big bunch of text.
>>>>
>>Does something like this work for you??????????
>>

>>llFirstRecord = .T.
>>FOR EACH lineofText IN oText
>>  DO CASE
>>     CASE LEFT(lineofText,3) = "MSH" AND llFirstRecord
>>        llFirstRecord = .F.
>>     CASE LEFT(lineofText,3) = "MSH"
>>        SendCompletionMessage
>>     OTHERWISE
>>        && Do Nothing - must be EVN, etc. record
>>  ENDCASE
>>
>>  DO CASE
>>    CASE "MSH"
>>    CASE "EVN"
>>    CASE "ETC"
>>  ENDCASE
>>ENDFOR
>>SendCompletionMessage  && For Last set of records

>
>If we move the first do case into the end of the loop, we would not need to execute it outside of the loop.

I don't see it. When you encounter a new message (code = "MSH") you know have have finished the previous one. How can you know the last message has been processed when the code isn't "MSH"