[AccessD] That SQL date catch again

This is just one of those areas where I know the problem is what I'm asking
and how I'm asking it and I can't figure out how to ask the problem
correctly. :( 

Susan H. 


Something else that you might want to look at is the query itself. I.e., you
open the query, then transpose the fields, the query statement doesn't
change, only the presentation does). Perhaps you did this accidentally at
some point. Perhaps not, but it won't take long to check.

Arthur

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Susan Harkins
Sent: Thursday, July 08, 2004 9:32 AM
To: 'Access Developers discussion and problem solving'
Subject: [AccessD] That SQL date catch again


I've heard you guys discuss the SQL behavior that uses the US standard for
date strings, which causes non-US developers trouble if they don't know
about it. 
 
My question is:
 
Is this a problem only when passing a date "string" or is the same true if
you pass a date data type. I would think SQL should be able to process a
date value passed by a date data type correctly. 
 
I haven't tested anything -- looking for a place to start. 
 
Susan H. 
--
_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

--
_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com