There are two ways you can go here (assuming that MaxFrame hasn't been updated). One thing to do would be SET STRICTDATE. The problem with that is that SET STRICTDATE provides valuable warnings about date functions that could cause Y2K problems or problems with international dates. You can always compile with strict dates and fix anything that's a real problem then recompile without strict dates.

The other thing you could do is just change the framework. I think this is sometimes the best course of action. Just keep a log of all the changes you make so you can reapply them if necessary when you upgrade. If you keep these changes to a minimum you'll find that this is really pretty easy.


>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.
>