I've been working with Powershell for a few months, always nice to have an additional source of material. Thanks!

For files with numbers less than 10: FOR /L %F in (1,1,9) DO REN L%F.txt L00%F.txt For files with numbers from 10 to 99: FOR /L %F IN (10,1,99) DO REN L%F.txt L0%F.txt You could expand this out with a check to make sure the file exists: FOR /L %F IN (1,1,9 DO IF EXIST L%F.txt REN L%F.txt L00%F.txt

I worked with a woman who left a trail of teary eyes and coughing whenever she walked past the cube farm. Everyone absolutely dreaded sitting in a meeting with her because after about 10 minutes we were all so saturated with her odor that seven hours later at home our wives accused us of having torrid office affairs. Not to be weightist, but she was a big woman and to this day I cringe when I think about what odor she may have been trying to cover up with the gallons of foul perfume she must have gone through each month.... Jim

Planet of the Apes (the remake!)

Somebody who names a craft Invincible is just dying for an extreme disappointment at the worst possible time.

My 'new' Dell D630 laptop tops out at an oddball 1280x800 - when we loaded W7 on it, the OS popped up and said "Many applications may not display properly at this resolution". WTF? Jim

Filezilla FTW - I just used it over the weekend to transfer close to 500 GB (yes, that is Gigabytes) from a customer site to our data center, several hundred thousand files in all. Great performance, very stable (had it up all weekend without any interruptions) and fast fast fast! I only wish it would allow more than 10 connections to the server because I filled all ten pretty quickly. I did get around the 10 connections limit by running multiple copies, but that's just not the same. I did notice that it couldn't transfer files when the full pathname of the file gets much above 200 characters, but a structure that long has other problems as well.

Yer just beggin' for unmanageable scope creep by making user feedback a part of the requirements doc. Version 1 should provide what was agreed on in the initial signed requirements document (unless there's a REALLY big breakdown of functionality), then features based on feedback can be added as a version 1.1 after the appropriate financial negotiations. Been there, done that, still got the burn marks.