If you're dates in the CSV file are in dmy order, then I would rename the
workbook to *.txt. Then I could import the data and specify that field as a
date in dmy order.

I _think_ that what's happening is that other users have a different data
order. The data that could pass for dates in that formatted will be converted
to a real date -- but probably not what you want.

For instance if the data shows: 12/02/2008
and you bring it in with your shortdate format of dmy, then you'll see a date of
Feb 12, 2008.

But if I bring it in using my mdy shortdate format, I'll see a date of Dec 2,
2008.

The real bad news is that with an ambiguous date format of mm/dd/yyyy, you can't
tell if the date is really want the CSV intended.

And those "dates" that do not look like dates that match the users short date
format (25/02/2008 for instance) will be a real date for you (dmy) = Feb 25,
2008.

For me with my mdy order, I'll get a text string of 25/02/2008. It won't be a
date.

So my recommendation is to not rely on the user's setting. Bring the data in a
different way--either by renaming the file as *.txt (so you see the wizard).

You could also try: Data|Import external data|get data to see the same text to
columns wizard.

====
My real point is just because the value looks like a date doesn't mean that it
is a date. And even if it is a date, it may not be what the original data
intended.



Nils Titley wrote:

Dave,

I am sorry. I missed you replay. This is the same macro I have been
working on.

The data are in CSV excel files. I am taking the data from the file and
crunching the numbers and output it to another workbook. The dates are in
the 12/2/2008 which is ddmmyyyy. All the dates are in that format.
12/2/2008 is the first problem I have encoutered with the date. It things it
is mmddyyyy.

Gets loads the variable.
RunDate(Beat) = ActiveCell.Offset(0, 1).Value

Any other questions?

Thanks and I am sorry I missed your question.
"Dave Peterson" wrote:

No response????

Dave Peterson wrote:

Yep.

Does the user type it in? Do you pick it up from a cell? Do you import it from
a text file?

Nils Titley wrote:

RunDate = Dim RunDate(0 To 25) As Date
MyNum = Dim MyNum As Long

You need more?

"Dave Peterson" wrote:

Where did you get MyNum?



Nils Titley wrote:

Ron,

I confess, I don't know how to get the numeric value of it?

"Ron Rosenfeld" wrote:

On Sun, 23 Mar 2008 00:52:04 -0700, Nils Titley
wrote:

Thanks to all for responding but I am wondering. Will I have a problem with
12/02/08. This is not December 02,08 but it is Feb 12, 08. The dd/mm/yy has
already caused a problem. The macro is being used in South Africa. I had to
force format on a date because it was changing the format.

The code below produced 02/12/08 when it is 12/02/08. It worked only after
I changed below to Format(RunDate(MyNum), "dd/mm/yy")

With ActiveCell.Offset(0, 0)
.NumberFormat = "dd/mm/yy"
.Value = RunDate(MyNum)
.HorizontalAlignment = xlCenter

How do I force the day of the week?

Thanks , I hope I am making sense.

I believe you may be misunderstanding how dates are being entered into Excel.

Excel stores dates as serial numbers with 1 = 1 Jan 1900. It then formats that
result depending on the cell format.

However, a date expressed like 12/02/08 is ambiguous. So when you enter that
value into a cell, Excel has to decide if you mean 12 Feb or 2 Dec. It does
this by looking at the date settings -- NOT in Excel -- but at Control
Panel/Regional and Language Options.

So if your code is producing 2 Dec when you expect it to be producing 12 Feb,
you need to look at the output of RunDate(MyNum). If the numeric value is
39490, then it is returning 12 Feb; if 39784, then 2 Dec.

If it is returning the desired date, then
.numberformat = "dddd" will return the correct day of the week.
--ron


--

Dave Peterson


--

Dave Peterson

--

Dave Peterson


--

Dave Peterson