I have used Excel 2007 happily for many years, and often Sort spreadsheets. The method is to click on a cell, then Sort, at which point all the columns containing data change colour and one can select what criteria you want. Since having transferred to Windows 10, the only sheet that I have added to my ONS database is my data from the 1939 Register. I have 15 columns of data and about 190 rows. Eventually I decided to Search (I think the first time was to separate the sexes) and noticed that only the first 11 rows changed colour, and eventually found that I had to manually select all the Rows before the search, which had never done before. The earlier Sheets in the same Workbook were not affected and continued to behave as before, but coming back to the files today I find that the 1939 register sheet is now behaving normally, but in the process columns 1 to 11 give rows that are correct, but columns 12 to 15 give rows that are in random order - so for instance a family that appear in correct order in the first columns are all at different addresses. In other words I have now got two part-databases that don't match each other and despite trying to replicate various Searches on the two halves I can't get them to go back to the original. It may be that I did a Search without noticing that all of the sheet hadn't been selected, but I didn't notice that. Fixing this will be a nightmare, but nothing compared to the problem if some of my other sheets with nearly 2000 rows do the same. Searching the Net indicates that others may have had somewhat similar problems. Prevention must be to "Save As" the file every time it is closed, using the date for instance so that, while the day's work may be corrupted one could still go back to a recent version - of course, I had never done that and my most recent computer back-up was before the 1939 sheet was added. (I'm a bit baffled that Windows 10 contains a file back-up facility and my computer has a conventional hard-drive and a solid state drive but Windows refuses to use one to back-up the other). Has anybody else had this problem and could suggest whether it is peculiar to Windows 10, has my Excel become corrupted, or is there a mutual incompatability? Adrian

Adrian I had problems with Excel when I upgraded to Windows 7. I am now on Windows 8.1. I found the problems went away when I saved the files to the latest version of Excel, ie changing the file extension from .xls to .xlsx. When you transfer the files they retain the old format and some of the features become unstable. You need to Save As and select Save as Type: Excel Workbook (*.xlsx). Hope that helps. Regards David Burgess On 25/3/16 13:37, Adrian Abbott via wrote: > I have used Excel 2007 happily for many years, and often Sort > spreadsheets. The method is to click on a cell, then Sort, at which > point all the columns containing data change colour and one can select > what criteria you want. > > Since having transferred to Windows 10, the only sheet that I have > added to my ONS database is my data from the 1939 Register. I have 15 > columns of data and about 190 rows. Eventually I decided to Search (I > think the first time was to separate the sexes) and noticed that only > the first 11 rows changed colour, and eventually found that I had to > manually select all the Rows before the search, which had never done > before. > > The earlier Sheets in the same Workbook were not affected and > continued to behave as before, but coming back to the files today I > find that the 1939 register sheet is now behaving normally, but in the > process columns 1 to 11 give rows that are correct, but columns 12 to > 15 give rows that are in random order - so for instance a family that > appear in correct order in the first columns are all at different > addresses. In other words I have now got two part-databases that don't > match each other and despite trying to replicate various Searches on > the two halves I can't get them to go back to the original. It may be > that I did a Search without noticing that all of the sheet hadn't been > selected, but I didn't notice that. > > Fixing this will be a nightmare, but nothing compared to the problem > if some of my other sheets with nearly 2000 rows do the same. > Searching the Net indicates that others may have had somewhat similar > problems. > > Prevention must be to "Save As" the file every time it is closed, > using the date for instance so that, while the day's work may be > corrupted one could still go back to a recent version - of course, I > had never done that and my most recent computer back-up was before the > 1939 sheet was added. (I'm a bit baffled that Windows 10 contains a > file back-up facility and my computer has a conventional hard-drive > and a solid state drive but Windows refuses to use one to back-up the > other). > > Has anybody else had this problem and could suggest whether it is > peculiar to Windows 10, has my Excel become corrupted, or is there a > mutual incompatability? > > Adrian > _____________________________________________ > > RootsWeb lists - surnames, regions, software, etc: > http://lists.rootsweb.ancestry.com/ > ------------------------------- > To unsubscribe from the list, please send an email to [email protected] with the word 'unsubscribe' without the quotes in the subject and the body of the message > -- David Burgess

I had problems as well, somehow my computer had defaulted to an American date set-up and not UK English, once I put that right things got better. Jennifer -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Adrian Abbott via Sent: 25 March 2016 13:38 To: GOONS Subject: [G] Disastrous Excel Behaviour I have used Excel 2007 happily for many years, and often Sort spreadsheets. The method is to click on a cell, then Sort, at which point all the columns containing data change colour and one can select what criteria you want. Since having transferred to Windows 10, the only sheet that I have added to my ONS database is my data from the 1939 Register. I have 15 columns of data and about 190 rows. Eventually I decided to Search (I think the first time was to separate the sexes) and noticed that only the first 11 rows changed colour, and eventually found that I had to manually select all the Rows before the search, which had never done before. The earlier Sheets in the same Workbook were not affected and continued to behave as before, but coming back to the files today I find that the 1939 register sheet is now behaving normally, but in the process columns 1 to 11 give rows that are correct, but columns 12 to 15 give rows that are in random order - so for instance a family that appear in correct order in the first columns are all at different addresses. In other words I have now got two part-databases that don't match each other and despite trying to replicate various Searches on the two halves I can't get them to go back to the original. It may be that I did a Search without noticing that all of the sheet hadn't been selected, but I didn't notice that. Fixing this will be a nightmare, but nothing compared to the problem if some of my other sheets with nearly 2000 rows do the same. Searching the Net indicates that others may have had somewhat similar problems. Prevention must be to "Save As" the file every time it is closed, using the date for instance so that, while the day's work may be corrupted one could still go back to a recent version - of course, I had never done that and my most recent computer back-up was before the 1939 sheet was added. (I'm a bit baffled that Windows 10 contains a file back-up facility and my computer has a conventional hard-drive and a solid state drive but Windows refuses to use one to back-up the other). Has anybody else had this problem and could suggest whether it is peculiar to Windows 10, has my Excel become corrupted, or is there a mutual incompatability? Adrian _____________________________________________ RootsWeb lists - surnames, regions, software, etc: http://lists.rootsweb.ancestry.com/ ------------------------------- To unsubscribe from the list, please send an email to [email protected] with the word 'unsubscribe' without the quotes in the subject and the body of the message