If File Changed error

Bob Hansen · Post by **Bob Hansen** » Thu Nov 14, 2002 3:14 pm

This is a reposting of a topic submitted on 11/10 that has gone unanswered. Additional technical details are on the original posting of 11/10/02 under the topic IfFileChanged error in 19xx.
====

I have just discovered that I am getting incorrect results when using IfFileChanged command comparing dates from 19xx. Perhaps it may be a Y2K problem using a 2 digit year vs. a 4 digit year? I am using MacroScheduler 7.0vb with Windows 98SE. Dates are formatted for 4 digit years.
=================================
Brief explanation using the command like this to copy files changed in the last day:

Label>NextFile
IfFileChanged>Filename,NextFile
...
...
Label>CopyFile
CopyFile>...
...
...
...
If>NotDone,NextFile

Label>End

=============================
The problem is that if the filedate is in 19xx, then it is identified as "Changed" and is processed to be copied.

support · Post by **support** » Fri Nov 15, 2002 9:29 am

Hi,

Sorry you didn't get an answer. We're just looking into this. You may be right - it does seem from what you say that the century difference is confusing it. If this is the case, then I hope there is a fix

Bob Hansen · Post by **Bob Hansen** » Fri Nov 22, 2002 11:08 pm

I see you are "hoping" for a fix.

But I am curious if there might be patch in the near future, or do I need to use different programming methods?

Post by **Marcus Tettmar** » Mon Nov 25, 2002 9:13 pm

Hi,

We have fixed this - it was indeed due to 2 figure dates in this particular command. Will let you know when the update is available for download.

Post by **Marcus Tettmar** » Mon Nov 25, 2002 9:59 pm

Just to let you know build 7.1.12 fixes this issue and can be obtained from http://www.mjtnet.com/dldregd.htm

Bob Hansen · Post by **Bob Hansen** » Tue Nov 26, 2002 12:19 am

Thanks for the fix Marcus.....other products could learn a lot from your customer support