I suppose you are correct as it relates to modifying the original runtime from Microsoft, who I guess should have supplied the patch but didn't. I would agree with your assessment of locking all programs into the same rollover window and if that was a concern then you make a good point, however, I think that would be the exception rather than the rule. I think for most of us a selectable 100 year window would suffice. I've been thinking about both options and believe if the needing multiple (different)rollover functions weren't an issue, then the patch would certainly be a lot cleaner way to go. I certainly haven't looked at y2kfox so speak only from reading their material and not from experience. How does y2kfox handle dates that are feed into ctod() functions as character strings? Does it interpret them as if entered from the keyboard and apply the rollover function to it or does it only do that through an intercept for keyboard entered data? Our source code has a lot of indexes created the following:
STR(CTOD(somedatestring)- CTOD('01/01/01'),8,0) to &smkog..ndx.

As was explained to me the second CTOD would convert to 01/01/1901 with y2kfox and to 01/01/2001 with FOX2000. Can you confirm this either way?

Anyway, for our personal situation we are planning on porting the entire billing system into VFP in the spring. Thiw will only be a temporary measure anyway.

Thanks,

Steve