Bizarre date handling from a user-defined 'tool'
Posted: Thu Jan 12, 2006 5:37 pm
I have a bunch of scripts which I run from TP tools I created. One of these scripts creates an MD5 hash against a file using, amongst other things, a date string. The string is formatted VB Script using long date:
FormatDateTime([thefileobject].DateCreated, 4)
When run from a command prompt, I get the date I want, '25 October 2005'. However, when the script is run from the TP tool, I get short date, '25/10/2005'
This has to be a bug, right? If not, is there a work-around? And please don't suggest using some string other than the date...
FormatDateTime([thefileobject].DateCreated, 4)
When run from a command prompt, I get the date I want, '25 October 2005'. However, when the script is run from the TP tool, I get short date, '25/10/2005'
This has to be a bug, right? If not, is there a work-around? And please don't suggest using some string other than the date...