Actually, the commas are not an issue. Legacy wraps all the fields in quotes and Excel (2003 anyways) then properly separates the fields on the correct commas ...
C.G. Ouimet Kingston, ON -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mike Fry Sent: Friday, March 14, 2008 16:29 To: [email protected] Subject: Re: [LegacyUG] Version 7 Valerie Garton wrote: > I mean the index view where I have edited all my columns which look > just great, even a screen dump would be good. In that case... I would have to agree with the desirability of such a feature. However, one needs to remember the purpose of the Index Tab, which is to locate and select a member of the database (and family) for editing. One way might be to create a CSV file from the Name List where dates could be included. You can print from the Name List and include the dates in the report. Just don't include any locations because of the extra commas. Make sure that the report destination goes to a CSV file. That CSV file can then be imported into an Excel spreadsheet (or the OpenOffice.org equivalent) and your sorting criteria used there. I think that would provide a work-around until such time as you can do it from within Legacy. -- Regards, Mike Fry Johannesburg. 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 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
