Now that's not a bad idea. I could write a module to do that for now, unless it's something that has the potential for Core development later on. I could always just write it as a Contrib. I do like the idea of being able to do all of my product updates separate from the actual database update. (In other words, get all of my files updated across the catalogue, and THEN find and add it to previous orders).

And hey .. am I a bug finder now?

I am going to play with uc_file some more this weekend and will also work on the output a little. In case you haven't seen it, attached is a screenshot of my current File Product module's custom jQuery, accordion My Files page. (The blue bar is the over state for that DIV - clicking on it expands that file view and contracts the currently opened one).

EDIT: Choosing "Any" SKU when assigning a file to a product, and then submitting, yields a blank white screen. Also how hard would it be to add another field to the process? Can I do this with hook_form_alter()? In our case I like to include a tiny bit of "helper text" for "what file this is" - PAL, NTSC, DivX, etc. (See my screenshot).