Re: us date format
- From: "Douglas J. Steele" <NOSPAM_djsteele@xxxxxxxxxxxxxxxxx>
- Date: Sun, 22 Jan 2006 07:09:02 -0500
"Bob Wickham" <wickham_bob@xxxxxxxxxxxx> wrote in message
news:43d2e2ef@xxxxxxxxxxxxxxxxxxxx
>
> The "Steve" suggestion I was referring to was in response to a question
> asked by you back in October (Steves reply below).
>
> I am wondering if there is a right/wrong or good/bad way to do it or is
> like the "discussions" I have with my father-in-law about the pros and
> cons of PC's and Mac. ie. It depends on what you need.
Whichever way gives you the correct answer is the "right" way. <g>
Take a look at the discussion I had with Marsh elsewhere in this thread. I
don't see that one approach is better than the other. Yes, the CLng approach
assumes that dates are stored as numbers, and if that ever changed then this
wouldn't work, but I can't see such a fundamental thing changing.
Personally, I always use the Format approach (Format(MyDate,
"\#mm\/dd\/yyyy\#") rather than the CLng approach, but I would think that
one function call is just as "expensive" as the other. It's possible that
the CLng approach is actually slight more efficient, since Access has to
convert the string version of the date returned by the Format function to a
date.
--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no private e-mails, please)
.
- References:
- us date format
- From: Bob Wickham
- Re: us date format
- From: Marshall Barton
- Re: us date format
- From: Bob Wickham
- Re: us date format
- From: RoyVidar
- Re: us date format
- From: Bob Wickham
- Re: us date format
- From: RoyVidar
- Re: us date format
- From: Bob Wickham
- Re: us date format
- From: Marshall Barton
- Re: us date format
- From: Douglas J. Steele
- Re: us date format
- From: Bob Wickham
- us date format
- Prev by Date: Re: us date format
- Next by Date: Re: Compacting tempory file using code
- Previous by thread: Re: us date format
- Next by thread: Re: us date format
- Index(es):
Relevant Pages
|
Loading