Comments on: createODBCDate() returns ‘time’ as well?

By: Michael Sharman - chapter31 » Caveat using dateDiff() to compare difference in days

Mon, 03 Nov 2008 13:00:13 +0000

[...] had some problems a little while ago using dateCompare() and the same thing bit me recently with dateDiff(). Well really I had a problem [...]

By: Michael Sharman

Michael Sharman — Tue, 04 Dec 2007 20:51:49 +0000

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

Dave H — Tue, 04 Dec 2007 15:53:15 +0000

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

Michael Sharman — Sat, 06 Oct 2007 03:46:29 +0000

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

Tom K — Fri, 05 Oct 2007 08:57:14 +0000

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.