>Many client ask me about their system isn't pass Y2K.
>
>some of my client useing DOS5.0 DOS6.0 WINDOW3.1 OFFICE4, FOXPRO2.6(DOS)
>
>can you tell me what will the system will appear when Year2000

None of the systems you mention are Y2K compliant; the exact impact of continuing to run with them isn't clear. Some problems, such as date rollover in BIOSes, will be easyu enough to fix in many cases; reseting the system date and time on a one-time basis may be the only immediate impact, or, depending on the BIOS implementation, may cause a problem every time the system is restarted. Without extensive testing, no one can be sure what's going to go wrong.

FPDOS may be the least problematic, or a real disaster, depending on how much date manipulation is done, and whether dates are stored as date fields or as character fields. There are commercial products like Y2KFox which can help let FPDOS applications run with much better Y2K compliance; depending on what your client has budgetedand his target environment, Y2KFox may be a relatively low cost (at around US$1000 for a 20 seat license the last I looked) and easily implemented mechanism to avoid porting his apps out of FPDOS.

I'd suggest that you pick up a Y2K analysis tool and run it against your client's systems; both Norton and McAfee have test tools available that will examine a wide range of issues. Date Hound from Digital Coyote (an advertiser here on UT) is very useful in analysing FP/VFP code for Y2K compliance and can help suggest codearounds for some of the problems.