Hi,

I’ve just noticed some weird behavior of the VFP6 Query Designer and strict date formats in filters. I’ve searched the MSDN knowledgebase and found nothing. I’ve also not heard this mentioned at conferences or in the MS Y2K info.

One of my clients has a folder that contains queries they can manipulate through the Query Designer. I created a config.fpw file that runs a setup program that sets up the default folder, paths and environment. (set exclusive off, set strictdate to 1, set century on). They filter their queries with dates. We type in the date constant using the strictdate format {^1999/12/01}, click on the run button get our results, great! We save and close the QD re-open the just closed query and, voila! the date constant is now {12/01/1999} ( it does this for year =2000 also). Why doesn’t it save the query using the strictdate format in the date filter field?

They, as well as I, are used to changing query date filters by not having to type in the full date again. Maybe just changing the month or the day.

You guys know MS better than I do. Would you consider this a bug with the QD?

This also brings up another issue: My client has some reports that contain parameterized views in the DE (not my design, just assigned to make sure Y2K ok) asking for start and end dates. They didn’t want to see the 4 digit year on reports so in the Init Event of the DE I set century OFF. I have strictdate set to 1 for the application these reports run in. I’m getting the ambiguous date error even if I fill in the asked for parameters like this {^1999/12/01} or DATE(1999,12,01). These are the combinations I’ve tried in the init of the DE with the results when trying to run the report:

1. strictdate = 0, century off runs ok using {^1999/12/01} as the parameter
2. strictdate = 0, century on ambiguous date using {^1999/12/01} as the parameter
3. strictdate = 1, century off ambiguous date using {^1999/12/01} as the parameter
4. strictdate = 1, century on ambiguous date using {^1999/12/01} as the parameter

I would appreciate your insight into this matter.

TIA,
Jacci