>>Thanks for the reply. You have hit on a subtle but important difference. With strictdate set to 1, when I assign a value to the memory variable with the name of the view parameter, (i.e., vp_dDate = {^2000-01-31}), in the command window, the browse for the view works fine. If you release the variable and put the same value in the view parameter dialogue box, you get the "Ambiguous date/datetime constant" error. There seems to be a problem with the dialogue box. I have tried this with several simple views on a test basis and get the same result every time. I am wondering if it is only me or is it with Foxpro. (using Ver 6.0 SP3).
>
>
>It strikes me that perhaps you're complicating things by using the strict datewrapper here. The dialog knows that it's accepting a data. If it's accepting a string, I don't have to wrap it in quotes. What happens if you just enter a non-ambiguous date in whatever the current system form is, less the strict date notation? I just tried a test, and entering the date in the form {^2000-02-12} gave me the error, but 2000-02-12 did not.


I have tried several combinations of date format. Firstly, by using say 2000-02-12, it at least does not give an error, and produces a browse. However, nothing comes up in the browse, records: None. But the date I use has matching records, so it is not reading the date properly. No matter which form of the date I used, it would not come up with the records related to the date. I think when strictdate is set to 1, the dialogue box is not functional for dates.
Notwithstanding, it is most likely that the value of the view parameter can be set from a variable, and the dialogue box is unnecessary. This would avoid the problem. Unfortunately, in testing data and parameters, I was using the dialogue box and got stopped. I think that MS might look at this dialogue at some point, if it doesn't work.

Thanks for your help on this.