Comments on: createODBCDate() returns ‘time’ as well? http://www.chapter31.com/2007/10/05/createodbcdate-returns-time-as-well/ development in a land far far away... Wed, 15 Oct 2008 23:41:49 +0000 http://wordpress.org/?v=abc By: Michael Sharman http://www.chapter31.com/2007/10/05/createodbcdate-returns-time-as-well/#comment-29163 Michael Sharman Tue, 04 Dec 2007 20:51:49 +0000 http://www.chapter31.com/2007/10/05/createodbcdate-returns-time-as-well/#comment-29163 Yeah sounds a bit dodgy Dave, I guess it's one of those things we just need to keep in mind. Makes it harder though when the name of the function seems to go against its behaviour. Yeah sounds a bit dodgy Dave, I guess it’s one of those things we just need to keep in mind.

Makes it harder though when the name of the function seems to go against its behaviour.

]]> By: Dave H http://www.chapter31.com/2007/10/05/createodbcdate-returns-time-as-well/#comment-29152 Dave H Tue, 04 Dec 2007 15:53:15 +0000 http://www.chapter31.com/2007/10/05/createodbcdate-returns-time-as-well/#comment-29152 We had a similar experience - passing a createodbcdate(now()) value to a function that increments the date based on the day of the week (using dateadd) resulted in a return of a date/time where time was NOT 00:00:00, but the actual time of day. Outputting the passed variable showed no time, while outputting the function result showed the time. We had a similar experience - passing a createodbcdate(now()) value to a function that increments the date based on the day of the week (using dateadd) resulted in a return of a date/time where time was NOT 00:00:00, but the actual time of day. Outputting the passed variable showed no time, while outputting the function result showed the time.

]]> By: Michael Sharman http://www.chapter31.com/2007/10/05/createodbcdate-returns-time-as-well/#comment-22983 Michael Sharman Sat, 06 Oct 2007 03:46:29 +0000 http://www.chapter31.com/2007/10/05/createodbcdate-returns-time-as-well/#comment-22983 I think that's what was happening Tom, the funny thing was why wasn't I seeing the time part '00:00:00' when I outputted or dumped the createODBCDate() object? createDate() was another option for me, but was more work to pass in each date element (yyyymmdd) etc I think that’s what was happening Tom, the funny thing was why wasn’t I seeing the time part ‘00:00:00′ when I outputted or dumped the createODBCDate() object?

createDate() was another option for me, but was more work to pass in each date element (yyyymmdd) etc

]]> By: Tom K http://www.chapter31.com/2007/10/05/createodbcdate-returns-time-as-well/#comment-22865 Tom K Fri, 05 Oct 2007 08:57:14 +0000 http://www.chapter31.com/2007/10/05/createodbcdate-returns-time-as-well/#comment-22865 I think CreateODBCDate() does have a time index in it - otherwise (I'm guessing here) it wouldn't be a valid ODBC Date/Time Object? if you create a Date/Time field in Access, using Now() as the default, it'll give you: 05/10/2007 09:54:43. Presumably, CreateODBCDate returns: 05/10/2007 00:00:00 and CreateODBCDateTime will give you 05/10/2007 09:54:43. That way they're both valid for access (ODBC); I'd have a play with plain old CreateDate(), which I believe will just return the "date" part. T I think CreateODBCDate() does have a time index in it - otherwise (I’m guessing here) it wouldn’t be a valid ODBC Date/Time Object?

if you create a Date/Time field in Access, using Now() as the default, it’ll give you: 05/10/2007 09:54:43.

Presumably, CreateODBCDate returns:
05/10/2007 00:00:00 and CreateODBCDateTime will give you 05/10/2007 09:54:43.

That way they’re both valid for access (ODBC); I’d have a play with plain old CreateDate(), which I believe will just return the “date” part.

T

]]>