How can creation date for a file be after its modified date?!
--
Best regards,
Harvey

Harvey wrote:
> How can creation date for a file be after its modified date?!

Create file.
Set the date in the computer to last week.
Modify file.

Harvey wrote:
> How can creation date for a file be after its modified date?!

If you copy/move a file to a new location it gets a created stamp of when it
was copied/moved. But, it retains the modified date from the original
location.
Note that downloaded files from the 'net will also have the current date
for create date; they obviously weren't written on the day you downloaded
them.

MS calls it a "feature".

Pop`

Thanks for your reply. It seems if files keep thier creation date constant
and change thier modified dates during moving from machin to machin it's less
confusing. I can't think of any benefit for the current setting.
--
Best regards,
Harvey


"Poprivet" wrote:

> Harvey wrote:
> > How can creation date for a file be after its modified date?!
>
> If you copy/move a file to a new location it gets a created stamp of when it
> was copied/moved. But, it retains the modified date from the original
> location.
> Note that downloaded files from the 'net will also have the current date
> for create date; they obviously weren't written on the day you downloaded
> them.
>
> MS calls it a "feature".
>
> Pop`
>
>
>

Think of it this way. The creation date is the date it was created in that
location. Modified means changed. The file itself does not change when it
is moved to another machine. If I open the file in an editor and make
changes to it and save them, then it has been modified.

"Harvey" <Harvey@discussions.microsoft.com> wrote in message
news:F546792E-777C-481F-B7B7-6AF2392ABC2F@microsoft.com...
> Thanks for your reply. It seems if files keep thier creation date constant
> and change thier modified dates during moving from machin to machin it's
> less
> confusing. I can't think of any benefit for the current setting.
> --
> Best regards,
> Harvey
>
>
> "Poprivet" wrote:
>
>> Harvey wrote:
>> > How can creation date for a file be after its modified date?!
>>
>> If you copy/move a file to a new location it gets a created stamp of when
>> it
>> was copied/moved. But, it retains the modified date from the original
>> location.
>> Note that downloaded files from the 'net will also have the current
>> date
>> for create date; they obviously weren't written on the day you downloaded
>> them.
>>
>> MS calls it a "feature".
>>
>> Pop`
>>
>>
>>

> "Harvey" <Harvey@discussions.microsoft.com> wrote:

>> Thanks for your reply. It seems if files keep thier creation
>> date constant and change thier modified dates during moving
>> from machin to machin it's less confusing. I can't think of any
>> benefit for the current setting.

>>> Harvey wrote:
>>>> How can creation date for a file be after its modified date?!

It's because the programmers writing the OS, or likely their bosses
doesn't understand that a digital copy is the original. If not, it
is not a copy but a corrupt file.


--
Nah-ah. I'm staying out of this. ... Now, here's my opinion.

Please followup in the newsgroup.
E-mail address is invalid due to spam-control.

> "Harvey" <Harvey@discussions.microsoft.com> wrote:

>> Thanks for your reply. It seems if files keep thier creation
>> date constant and change thier modified dates during moving
>> from machin to machin it's less confusing. I can't think of any
>> benefit for the current setting.

>>> Harvey wrote:
>>>> How can creation date for a file be after its modified date?!

It's because the programmers writing the OS, or likely their bosses
doesn't understand that a digital copy is the original. If not, it
is not a copy but a corrupt file.


--
Nah-ah. I'm staying out of this. ... Now, here's my opinion.

Please followup in the newsgroup.
E-mail address is invalid due to spam-control.

> "Harvey" <Harvey@discussions.microsoft.com> wrote:

>> Thanks for your reply. It seems if files keep thier creation
>> date constant and change thier modified dates during moving
>> from machin to machin it's less confusing. I can't think of any
>> benefit for the current setting.

>>> Harvey wrote:
>>>> How can creation date for a file be after its modified date?!

It's because the programmers writing the OS, or likely their bosses
doesn't understand that a digital copy is the original. If not, it
is not a copy but a corrupt file.


--
Nah-ah. I'm staying out of this. ... Now, here's my opinion.

Please followup in the newsgroup.
E-mail address is invalid due to spam-control.

> "Harvey" <Harvey@discussions.microsoft.com> wrote:

>> Thanks for your reply. It seems if files keep thier creation
>> date constant and change thier modified dates during moving
>> from machin to machin it's less confusing. I can't think of any
>> benefit for the current setting.

>>> Harvey wrote:
>>>> How can creation date for a file be after its modified date?!

It's because the programmers writing the OS, or likely their bosses
doesn't understand that a digital copy is the original. If not, it
is not a copy but a corrupt file.


--
Nah-ah. I'm staying out of this. ... Now, here's my opinion.

Please followup in the newsgroup.
E-mail address is invalid due to spam-control.