Larry --

After looking over various options, it looks like I'll incorporate your code into a function used whenever we need to store the current filter.

As a design issue in Fox, it does make some sense. And, there's the added complexity of handling the various levels of strictdateness.

However, it feels like Fox is dealing with the "lowest common denominator" here. There isn't a way for Fox to maintain information that a date has been entered unambiguously. And there's no SET DATE TO STRICTDATE to allow that representation automatically, when the rest of the application is following that regimine.

Just a couple observations on an initially murky issue.

Thanks for your insight!