>It appears Visual Foxpro is not 2038 complaint. Unix systems that store the date in 32 bits are prone to this, and it appears some VFP stuff is, too. I found this out, because my system somehow got set to 2057, and I tried to build setup files-- MAKECAB crashed numerous times(every time). I narrowed it down to a 2038 problem. Should this naturally fix itself as 64-bit systems become mainstream, or does MS have to change the way they hold a date? Should I inform MS, or are they well aware?

Derek,

There are several articles in the MS KB on this. You might want to do a search on 2038 and see what comes up. In particular Q142576 may be of interest. This is a windows issue for the following platforms: Win 95, NT Server and Workstation 4.0.