Josh,

You are probably getting tired of hearing from me....

Anyway, I understand what the problem is...I didn't want or think I should go into the commercial framework and change the ctot to date. I was wondering if anyone knows whether their is a fix for this from Maxframe. Or maybe its better to just change the strictdate setting from 2 and recompile and just wait for Maxframe to change the txtbase class.

>Paul,
>
>This happens because of VFP 6.0's new strict date checking. Take a look at the help for SET STRICTDATE to will stop it from reporting these errors. It might be better to use the more explicit methods to convert strings to dates. Take a look at the help for DATE() and DATETIME() to see how to do this.
>
>>I just upgraded my VFP from 5.0 to 6.0. When I recompile I get the following compilation errors:
>>

>>Compiling c:\vfpfiles\xlib\x3fw.vcx
>>.Value = ctot(lcString)
>>Error in line 681 of txtbase.year2000strategy (record 77): CTOD and CTOT can produce incorrect results. Use DATE(y,m,d) or DATETIME(y,m,d,h,mm,s) instead, or recompile with STRICTDATE less than 2.
>>.Value = ctot(lcString)
>>Error in line 700 of txtbase.year2000strategy (record 77): CTOD and CTOT can produce incorrect results. Use DATE(y,m,d) or DATETIME(y,m,d,h,mm,s) instead, or recompile with STRICTDATE less than 2.
>>.Value = ctod("02/29/2000")
>>Error in line 977 of txtbase.KeyPress (record 77): CTOD and CTOT can produce incorrect results. Use DATE(y,m,d) or DATETIME(y,m,d,h,mm,s) instead, or recompile with STRICTDATE less than 2.
>>.Value = ctot("02/29/2000 " + substrc(lcValue,12))
>>Error in line 983 of txtbase.KeyPress (record 77): CTOD and CTOT can produce incorrect results. Use DATE(y,m,d) or DATETIME(y,m,d,h,mm,s) instead, or recompile with STRICTDATE less than 2.
>>

>>
>>I looked on Maxframes website for any information regarding this...and I do have the latest patch for 3.01 of Maxframe.
>>
>>Thanks,
>>Paul