Database: Useless row numbers. Need to be able to adjust column widths.
(Note: this is a revision of my earlier comment of today (“row numbers”) because as soon as I posted it, the database changed! I saw no way to delete that comment, which is now outdated.)
Today there is a new editing procedure in the database. Each row has an edit icon (pencil) and a delete icon (trash can) to the left of the row. It makes editing a row easier. One can sort the way one likes, and then edit a row without having to scroll through the whole database to find the row. Good. An improvement. We thank you.
The entries in the table are now very readable, without most of the awful line breaks in the middle of the words. Good again.
But … there is a new left-most column called Row, with a unique number in the column for every row. What is the meaning of this? The rows are not numbered consecutively from 1 to n. They appear to start at 1 but, for reasons known only to Yahoo, some numbers are skipped. My table with 48 rows has the rows numbered from 1 to 86, with many numbers skipped (it goes 1, 15, 21, 24, ...). When I add a row, it says it is adding row 49 (good) but then labels it in the Row column as row 87 (strange). This apparently useless new Row column takes up valuable real estate, better used by the other data in the table.
The columns are still one-size-fits-all, and too wide for most of my data. If I could adjust the column width as people have asked for earlier, my data would be more readable. I would have skinny columns for dates and wide columns for email addresses, which still have bad line breaks.
Also, I am concerned about how close together the Edit and Delete icons are, 1/4" on my monitor. Yes, you ask for confirmation before deleting the row, but wouldn’t it be better to separate the icons more, say by putting one icon all the way to the left of the row, the other all the way to the right, for user-friendliness?
Please allow the moderator to adjust column widths in the database, and either explain or get rid of the row numbers.
more comments on the new databases after revampiing
I appreciate yahoo trying to make the databases usable again
Indeed there are many good things in the improvements and I appreciate you got us the French accented characters back again.
However, the format is still difficult to read and use for following reasons:
1/ column headings do not align with the actual columns as soon as you click on one of the columns to have it ordered. After reordering one column, column headings stay the same at the top but when you scroll down, column widths vary and no longer fit the headings!
example: I try to sort out column number 3 according to zip code, all columns realign but not with the headings, one still cannot understand what each column is about
2/ I dont understand the first column: these numbers are of no use at all, I used to have the first column for the name of the group member who put in the information, this is what I wanted first but now it is no longer! It takes space for no use.
3/ I appreciate having more length for reading each column but this is far toooooo long now, you need to use the cursor to go very far to the right, while it used to be possible to read the whole table without using cursors.
4/ In particular, to move the cursor to the right, you need to go ALL THE WAY down the database, even if it was the first entry you wanted to go and read towards the right! Now if you want to go back and read the second entry (out of 400 or so entries) you need to scroll back all the way to the top, and then when you want to go to the right to see what is in the 5th or 6th column,, you need to go ALL THE WAY down to get the cursor towards the RIGHT, you must be KIDDING ME ?
Therefore, I much prefered having pages, rather than scroll down the entire list !
5/ It would be nicer to have the entire page free to read the database and thus PLEASe could you get rid of the list of all the groups I own or am a member of, on the left of the screen, this is really totally unnneeded once I am in a group and even more when we are trying to read a database.
Overall comment: you have really worked hard and I appreciate.
HOWEVER, it is really still very difficult to use and far LESS convenient than it USED TO BE
Deborah from PAris