>>>>Why would a command such as:
>>>>? ctod("10/13/15")
>>>>give me the following result?
>>>>10/13/2115
>>>>In other words, next century instead of the current century.
>>>>
>>>>I am trying to import data from a text file, and thought ctod() would be a quick solution. Actually the dates seem to include a century, so the question might be irrelevant for this particular task, but I was still curious what I did wrong.
>>>>
>>>>Here are some relevant settings (Visual FoxPro 9):
>>>>set("date") = "AMERICAN"
>>>>set("century") = "ON"
>>>>set("century", 1) = 20
>>>>set("century", 2) = 65
>>>>set("century", 3) = 2029 && what the heck does this do?
>>>
>>>What is the setting of Rollover? That may be the issue and what Set(Century, 3) is.
>>
>>According to help, rollover would be set("century", 2) - in this case, 65. Strangely, even for the CURRENT YEAR (see example above), it advances to next century.
>
>Is the current system date correct?

Yes. I forgot to mention that, but that was actually one of the first things I checked. According to my computer, the year is 2015.

I just did another check. Accessing Visual FoxPro normally, I get a date for the year 2015; the problem mentioned in my original post appears when I access via Visual ProMatrix, which I use for one of my clients. Therefore, it stands to reason that it is related to some specific setting - but I have no idea which one that would be.