Thanks for your reply, Jim. I think I'm resolved now wrt the "date created" problem. I dont know what changed, but when I went back to the utility and tried the date feature again, it worked. Thanks to your super utility, I ultimately got out of a sticky situation. We took a 16 day trip to Turkey and took better than 1000 images on 2 different cameras. The plan was to collect the image files into one folder and then choose between the many similar shots. To our horror, we discovered that the time had not been correctly set on one of the cameras. We determined the offset (a bizare 6 hrs 17 minutes - not exactly explained by the time change!) and then I set to work. After some false starts, a plan developed to use your "file taken" feature to use the bad timestamp by itself as the filename, then use a bruteforce method by importing a textfile that would replace the "bad" timestamp characters with "corrected" ones. I chose this direction because 1) it quickly became obvious that I was not going to convince the utility to adjust the timestamp characters as if they were numbers. So the next thing was to build a monster textfile (prepared in Excel) that included a 12character timestamp (YYMMDDHHMMSS) to identify every possible timestamp that the "bad" camera might have recorded on a pic. Naturally, the paired filename in the text file was simply a timestamp offset by 6hrs 15 min. The word "simply" refers to the concept more than the method to create. (If I hadnt gotten tangled up in Excel with timestamp and string manipulation issues, I'd be less tired right now!) Anyway, the bottom line is that we got all pictures synchronized from the 2 cameras, and then relabled with a nice new previx and numbering scheme, and my marriage is saved. And I certainly gave my new pc a workout
I guess the point of this diabtribe is to give you enuf sense for my situation so that you might consider adding a potentially life-saving feature for others who could easily have this same problem. If there were a way for you to offer the user a method to offset "file taken" data, it could be a tremendous boost. It would nicely serve even those shooting with one camera that has the timestamp all botched up.
One other question to ask that threw me a bit. I dont know if it is my computer or your utility that can explain this, but for some reason, the "file taken" stamp produced by BRU was 1 hour later than the file taken stamp registered on each image (I'm speaking of the shots from the camera with the correct timestamp). Can you think how this might have happened?? It didnt affect my project above, because the resulting file timestamps were offset by the same hour for pics from either camera, so my offset of 6hr 17min was still correct. But it was a bizare finding...