Thanks, will have a try with this tomorrow. I do have an alternative idea of what might be the problem (and it might be on my end)--perhaps something is server-cached and Firefox doesn't recognize that a "new" version is available, while Chrome does? I was using the latest release of Firefox, so...