Yeah, that's it. So around line 220, you can see this line of code:
fwrite( $fp, "This is the contents of a text file" );

That's why the attachments always have that content.

Now, what I'm not sure about is what you actually want there. :-) Trying to skim through the code, it seems like you're trying to copy the contents of one file attachment to another file attachment. If that's what you're trying to do, then this probably does come back to a Connect question, where I'm definitely not the expert.

Patricia started this process (see above) as a question of Connect PHP file attachment management which is why that line is there. This does not need to be done using Connect PHP and may not be pertinent given that this is really CPv2. I would suggest ripping out the Connect PHP code and use CPv2 semantics for creating a file attachment.

I am going to ask a dumb question then hopefully we can be done with this.

Does all the PHP Connect code reside within this file (if so what lines are examples of it) and if not, please give me an idea of where else I need to look.

Yes Patricia no longer works here so I am trying to get down to where she left off and how I can get this monster back in its cage. I can add the fileAttachmentUpload widget very easily but I assume this code is getting in the way.

Please guide me in how I can remove this and I will go from there.

You assistance has been so helpful. Unfortunately we have no documentation from her as to why, how or why things were done.

Today's assistance has been great. Thank you ahead of time again for your assistance.

To start from scratch, I think you might be able to simply replace the custom/input/FormSubmitAsk_CS0101 widget in your citation_0101.php page to input/FormSubmit. That should use the standard FormSubmit widget, which will create the incident normally and bypass the custom controller function (sendFormAsk_CS0101) and the custom model function (sendForm_CS0101).