The bad news, there is no easy way to fix this, as far as I know.
#Textpad license details are not correct error manual#
Your manual approach works because the file is being over written in a windows environment, thus producing CR LF combos. So your problem is, your incoming file has a bunch of LFs without any CRs. In a UNIX environment, new line is defined by a single LF. Usually, in a Windows based system, the new line is defined by a CR and LF characters.
The problem is the file comes from a different system. When I open the file using textpad, I can see the carriage returns. I have opened the file using Notepad and I can see that there are no carriage returns. I have stepped through the code and it appears that VB6 is ignoring carriage returns. The scheduled task reported that there was one row in the text file this morning (there is usually about 50,000). WriteError Err, Error$ & " in ImportPersons.", strErrorLog If Trim(strFields(3)) Trim(strFields(1)) Then
There is a function that runs as a scheduled task every day importing text from a text file: Public Function ImportPersons(ByVal strImportFile As String) As VariantÄim intFile As Integer, strRecord As String, strFields() As StringÄim lngReadCount As Long, blnChanged As Boolean