Stuart McLachlan
stuart at lexacorp.com.pg
Wed Aug 1 19:05:34 CDT 2012
I always use the following, it works on any PC regardless of what their local date format is.
--
Stuart
& "' AND DueDate = Datevalue('" _
& rstPODetail!fldPODDateRequired & "') AND PartNumber = '" _
On 1 Aug 2012 at 16:06, Rocky Smolin wrote:
> 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
>