I was recently required to sign up to voice recognition security when I telephoned a government department. I had to keep repeating the phrase "My Voice is my Password" while it was recorded and analyzed. Now my records are supposedly protected by my voice. That scares me. What happens when my Bank also starts to use this technology? Then the big online retailers? Then the utility service providers. I only have one voice, so all my accounts will be secured with the same voice print security. That is like forcing everyone to use the same password for all their accounts. Human nature will have users relax the complexity of their typed passwords because Voice Recognition becomes the main security measure, which is counterproductive for overall security. One employee in any one organization could steal and abuse all my accounts everywhere using my voice records. Try playing the hacking game Uplink for a demonstration of what might be possible with voice simulation (I found Uplink on Steam). Imagine what happens when a large telephone company get their database of bank account details hacked, together with the voice prints of all their customers? Instant access to all the tools necessary for total identify theft. The responsibility for proving fraud has happened passes from the bank to the customer. Try proving that you didn't transfer all your money to a scammer's account when the bank have what they claim is a recording of you logging in with your voice. Just because we have the technology to do some things doesn't mean we should.

Within limitations I LIKE the design! Provided that as someone implementing it I am allowed to think of the design as a VIEW of the data. I wonder if the multiple uploads problem could be a red herring. When clicking on a grid, nobody works in more than one box at a time. So when wanting to work on an upload grid box, a pop-up screen can be used to capture the new data, url of the document / image, or use drag and drop. I would upload the file as soon as the grid box or row loses focus, or a button is clicked. real multiple uploads would be dependent on there being multiple data entry points, with an 'Upload'/'Save' button at the bottom of the grid - it would need scrolling down to as the grid gets bigger which is bad news for the user. So don't have one, or put the text 'Upload/Save' on it but what it actually does is refresh the grid from the database underneath. This implements things the way you know is right, and does what the user needs too. I would think of it as a 'management overview' screen that can summarize records already in the database with the ability to drill down into attachments, and the ability to launch the process of adding a new record (with a pop-up screen and/or drag and drop). It is just that one user (the designer) would like this to be their home/default screen. If you provide the other screens you want to design, and let each user choose which screen they find useful. If in real life nobody uses the grid overview work screen, what is the harm in leaving it there.