If it is that important (which you stated it's not, but if it does become so...) add a few extra columns in your excel file (assuming you opened csv in Excel for this) to the right of the problem child column, and then from your menu bar select [Data] [Text to Columns]. **Make sure you have enough blank columns to fit the longest entry so as not to overwrite anything important further to the right*** Once you convert text to columns, in the next blank right column, use =concatenate( , , ,) to restructure the date to your desired structure.
(That's how I would resolve it.) Happy formatting! Jess M > >>> You aren't dense at all. As a matter of fact, you've hit the exact > >>> point. That *is* the way I actually entered the dates -- i.e., > >>> 11/24/1988. CSV didn't change anything -- and neither did Legacy. The > >>> *view* in Legacy is according to the Customize> Dates option. I enter > >>> "11/24/1988" in the Legacy field, hit tab, and the view in that field is > >>> changed to "24 Nov 1988" per my options. > >>> > >>> My question was, since I've entered the dates in so many different ways, I > >>> now have, basically, garbage for dates in my CSV file. Trying to change > >>> the format in those cells creates even more of a mess. The "11/24/1988" > >>> is okay -- but "Nov 1988" or "1788-1794" isn't. > >>> > >>> It really isn't that important and I'm not going to mess with it anymore. > >>> What I'm really using at this point in the CSV is the RIN and the name. I > >>> wanted the dates to help identify people with the same names, and wanted > >>> to find out if there was a quick fix for the dates for future reference in > >>> case I wanted to use them in a CSV in the future. > >>> > >>> Kris Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages: http://www.mail-archive.com/[email protected]/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
