Restructuring Text file to CSV
- 
 I have a Text file that needs to have some restructuring done to it before I can import it. It is a TAB delimited file of about 100 lines so this isn't a large file, but I could foresee my having to import a much larger file (about 3 years of data). The structure isn't difficult to read,.. but the issue is the REQDATE or (x)DATE is in a format that Excel doesn't like well Example: 2015-09-23 12:18:46.000There is no TAB between the year and time. Would it make more sense to go back to the original database and see if it can export differently? 
- 
 So what would an IDEAL format look like? 
- 
 Would this be good? 2015-09-23,12:18:46.000
- 
 More along the lines of this: 2015-09-23 11:48:25.000 2015-09-23[tabbed space here]11:48:25.000
- 
 I should add, that this will be a Crystal Reports Export to be done by another party. not that that should make any difference. 
- 
 So you are wanting a TSV, not a CSV? 
- 
 This is super easy. So assuming that your file is myfile.csv and you are on Linux, just do this... unexpand myfile.csv > myfile.tsvLike magic, Linux saves the day. 
- 
 @scottalanmiller said: So you are wanting a TSV, not a CSV? While I suppose technically speaking, yes it would be a TSV - Tab Space Value. However, TSV is not a Text file option in Excel - Only CSV  
- 
 Excel doesn't know formats, it just knows extensions  Windows apps are not very smart. Windows apps are not very smart.
- 
 Also, all the data is [TAB] not [,] 
- 
 @scottalanmiller said: Excel doesn't know formats, it just knows extensions  Windows apps are not very smart. Windows apps are not very smart.I won't argue you there... 
- 
 @gjacobse said: While I suppose technically speaking, yes it would be a TSV - Tab Space Value. This would be Tab Separated Value 
- 
 How are you planning to resatructure this prior to importing? You say a user is doing this? Then teach them how to handle it in Excel. You will be hard pressed to get a user to do much outside of an office application. Please be more specific about what you are doing with these files. - who is exporting it and from where.
- who is restructuring it
- who is opening it in Excel
- where is it going after that
 
- 
 LOL, right. It's Tab instead of space! The original file is an SSB, Space Separate Values. 
- 
 @JaredBusch said: @gjacobse said: While I suppose technically speaking, yes it would be a TSV - Tab Space Value. This would be Tab Separated Value Yea,.. there is that... 
- 
 So anyway, that one command solves the problem nice and easy. 
- 
 I expect that the 'best course of action' is to have the User rerun the export and adjust accordingly. However I was hoping to perform a trial run of the import with the data I have, about 100 lines or so. But each row has seven (x)DATE items... 
- 
 @gjacobse said: I expect that the 'best course of action' is to have the User rerun the export and adjust accordingly. However I was hoping to perform a trial run of the import with the data I have, about 100 lines or so. But each row has seven (x)DATE items... So does the command that I provided work? Can you provide full sample data so that we can test? 
- 
 @scottalanmiller said: @gjacobse said: I expect that the 'best course of action' is to have the User rerun the export and adjust accordingly. However I was hoping to perform a trial run of the import with the data I have, about 100 lines or so. But each row has seven (x)DATE items... So does the command that I provided work? Can you provide full sample data so that we can test? My apologies Scott, I missed your Linux command in a page refresh. Sadly I don't have this file on a Linux system.. Windows only... 
- 
 @gjacobse said: Sadly I don't have this file on a Linux system.. Windows only... So copy it, only takes a second. 


