Sorry I missed this, but I can't seem to replicate this bug. You can change the file name to 3000006, as well as in the file itself, and hopefully it won't happen again? I've tried tracking this one down but I can't get it.
