>Why am I hearing the odd rumour that VFP has a year 2000 bug (no-one seems to
>have the details, but this is the 2nd time I've heard it).

Some idiot developer is suing MS because VFP 3 and below always recognize a two-digit year as being in the 20th Century. That's the only Y2K issue with VFP that I'm currently aware of.

Win2K problems, on the other hand... :-)