"GJC" <GJC@discussions.microsoft.com> wrote in message
news:CEB4C999-4EE4-40C7-82A0-DA8ACA4D4258@microsoft.com...
> Hello.
>
> I have a text file with names, addresses, email, etc... It contains over
> 700,000 records. When I use the DTS text driver I only get just over
> 400,000
> records. If I Import the data into MS Access, I get the full 700,000. I
> looked at the file in at Hex editor and the row Identifier is a line feed
> (0A). The contains abount 9 fixed length fields.
>
> When looking at the 400,00 records that it did import, I notice that some
> of
> the characters in the last field are cut-off. When viewing these cut-off
> records with the hex editor, they look perfect, no other characters exist.
>
> I'm starting to go bauld from pulling my hair out, HELP!
>

"Kevin Thomas" wrote:

> Just a side thought here. If you've gotten all 700,000 records into Access,
> could you then try and import them into SQL Server from Access? I'm
> assuming SQL Server is your final destination for this data.
>
> I know this doesn't help with your core problem, but I thought any idea that
> might help you keep your hair might be worth mentioning. :-)
>
> Kevin
>
> "GJC" <GJC@discussions.microsoft.com> wrote in message
> news:CEB4C999-4EE4-40C7-82A0-DA8ACA4D4258@microsoft.com...
> > Hello.
> >
> > I have a text file with names, addresses, email, etc... It contains over
> > 700,000 records. When I use the DTS text driver I only get just over
> > 400,000
> > records. If I Import the data into MS Access, I get the full 700,000. I
> > looked at the file in at Hex editor and the row Identifier is a line feed
> > (0A). The contains abount 9 fixed length fields.
> >
> > When looking at the 400,00 records that it did import, I notice that some
> > of
> > the characters in the last field are cut-off. When viewing these cut-off
> > records with the hex editor, they look perfect, no other characters exist.
> >
> > I'm starting to go bauld from pulling my hair out, HELP!
> >
>
>