>>>>>>I am dealing with a project in Visual Foxpro which is having a database of Historical data. I am facing with the problem of entering date that is before 100th century. AD. how do I solve this problem?
>>>>>
>>>>>Matt's reply is correct, VFP can handle dates in the range of 01/01/0100 through 12/31/9999 so you can't enter dates in the first century A.D., at least not as date fields. Do you really need full month-day-year information for historical dates that far back? In addition to Matt's suggestion, if all you need is the year, you might want to consider using a character or numeric field to store it.
>>>>>
>>>>>BTW, here's a GOTCHA I recently discovered when working with dates: it appears that the GOMONTH() function doesn't work on any dates prior to 01/01/1752. It returns the empty date when used with any earlier dates.
>>>>>
>>>>That's when the Western calendar system went from Julian to Gregorian, I believe. They'd need a different function for time prior to that...
>>>
>>>Actually, it was the other way around..
>>>
>>>Therefor Julian day 1 = 01/01/1752 which affects SYS(1) and SYS(11,)
>>
>>----------------------
>>The value returned by SYS(1) is valid in the U.S.A. You can get Visual FoxPro versions for any system date after September 14, 1752, and before December 31, 9999.
>>----------------------
>>The Complete Visual Foxpro system date functions works only within the specified period.
>>The above lines are from Visual Foxpro Help 4.00.950.
>
>OK, I goofed again. Julian Day 1 = 09/14/1752. Hey, nobody's perfect. 'Specially not me.

Hey Cool. Even I donot know regarding this. And since In my office I was asked to give a seminar on Y2K in Foxpro, I started looking at it more and more cloosly. Till you said that Sys function, even I do not know , and was working on your message in VFP and suddenly noticed it in the help file, So I just wanted to inform you. Now I am still working on it.

Even I am not perfect.

If you can , Please solve my 'Data porting ' problem.