>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?
That's not a VFP problem. VPF fully supports years up to 9999. The problem is coming from the MAKECAB utility. Microsoft is pushing the Visual Studio installer. You should take a look at it. It's pretty cool and MUCH easier to use than the setup wizard. You can get information from the VFP home page.
Craig Berntson
MCSD, Microsoft .Net MVP, Grape City Community Influencer