Thanks for the quick feedback Frank. I will indeed look at that StrictDate setting - as it's not a setting I've seen before nor used.
-K ________________________________ From: ProFox profox-bounces@leafe.com on behalf of Frank Cazabon frank.cazabon@gmail.com Sent: Wednesday, March 26, 2025 8:49 AM To: profox@leafe.com profox@leafe.com Subject: Re: An Issue with Dates...
[You don't often get email from frank.cazabon@gmail.com. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
Hi Kurt,
those dates are ambiguous because different cultures use different date formats (d/m/y or m/d/y or y/m/d).
I tend to code all my dates using DATE(2025, 3, 26) for example.
you can also check the help on SET STRICTDATE
Frank.
Frank Cazabon
On 26/03/2025 8:28 am, Kurt Wendt wrote:
...and I don't mean the fruity kind.
I think this forum is now going to be a bit more active these days! Anyway...
I've been seeing this error a number of times - when trying to compile things recently (and, in case you're curious - I used an online OCR tool to convert the pic of the error to Txt!):
Error number: 2032 Error message: Ambiguous date/datetime constant. Use the format:
{yyvy-mm-dd{. [hh:mm:ss] [alp]]} Line number of error: 51 Command with error: IF thisform.txtDueDate. Value < {1/1/1990} OR thisform.txtDueDate. Value > {12/31/2049} Program with error: MPSBATCHTRANSFER.CMDACCEPT.CLICK
The error has been recorded in our error log for our future reference,
I know that this method of encoding dates in VFP ( the {1/1/1990} style) is indeed an older method. But, at some point - did VFP just simply drop the support of this style of dates usage?
I'm honestly just curious...
-Kurt (The OLD VFP Guy who is now Back in the Saddle!)
[excessive quoting removed by server]