Stephen Bond
stephen at bondsoftware.co.nz
Wed Aug 1 18:24:03 CDT 2012
We use dd/mm/yyyy dates down here ... if I need to change it round for a
SQL statement I use this:
... " AND DueDate = " & Format(
rstPODetail!fldPODDateRequired,"\#mm\/dd\/yyyy\#")
It generates the string (for August 2nd) #08/02/2012#
Does this give you a way forward?
Stephen Bond
-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin
Sent: Thursday, 2 August 2012 11:16 a.m.
To: Stephen
Subject: [AccessD] International date format problem
Dear List:
I have the following line which works fine here with mm/dd/yyyy but does
not
work for my client in Mexico where the date format is dd/mm/yyyy:
rstSupply.FindFirst "OrderNumber = '" & Me.txtPONumber & " - " &
rstPODetail!fldPODLineNumber _
& "' AND DueDate = #" _
& rstPODetail!fldPODDateRequired & "# AND PartNumber = '" _
& rstPODetail!fldPODPartNumber & "'"
where fldPODDateRequired is Date/Time data type. This is A2K3 BTW.
When
date format is set in Windows to dd/mm/yyyy rstSupply.NoMatch=True, when
date format is mm/dd/yyyy rstSupply.NoMatch = false (finds the record)
I think I may have this problem in other places in the code. Is there a
general method to avoid this problem?
MTIA
Rocky Smolin
Beach Access Software
858-259-4334
www.bchacc.com <http://www.bchacc.com/>
www.e-z-mrp.com <http://www.e-z-mrp.com/>
Skype: rocky.smolin
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com