>>Yep; without some workarounds, FPDOS 2.6 doesn't think February 29, 2000 is a valid date.
>
>Ed: not quite right. FPD2.6 is perfectly happy with 2/29/2000: it's 2/29/00 that it chokes on.
>

>And it's listed as "compliant with issues" -- if you have 4-digit years and avoid the LUPDATE() function, you should have no problems. http://msdn.microsoft.com/vstudio/y2k/vfoxproy2k.asp

Well reading Ed I did the test, it seem's also ok with FPD 2.5b

Tks !