I have cured it by the way.

I used the following code

Dim Cell As Object
For Each Cell In Selection
If IsDate(Cell.Value) Then
Cell.Value = DateValue(Cell.Value)
End If
Next Cell
End Sub


I guess that will work with both one or two instances of excel.

Thanks for your help, it got me thinking on the right lines.





"Dave Peterson" wrote:

First, I wouldn't give up on just using one instance of excel and trying to get
that to work correctly.

I can't recall a time when I copied a date and pasted and it didn't stay a date.

Are you sure your original data is really dates?

If you put
=isnumber(a1)
(if a1 is one of the cells copied)
do you get true or false?

If you do the same thing in the receiving worksheet/workbook, do you get true or
false?

The only time I've ever had trouble with dates is when I copied from a different
workbook and that workbook used a different starting date (1904 vs. 1900, on
tools|options|calculation tab).

But the values get pasted as dates, just not the dates I want!

Barbar wrote:

First post, so please be gentle on me!!

I have a workbook with data exported from another DB which contain a mixture
of dates number and times. These are mixed within the same columns.

If I try to copy and paste to another worksheet or workbook within the same
instance of excel the dates are not pasted as dates (even if I use paste
special and select values only). The dates are formatted to the left by
default.

I have got around this by opening another copy of excel and then using paste
special which gives me an entirley different dialog box and then I select
text or csv as the paste special format. Thsi gives me dates as dates
(formatted to the right by default)

So far so good, but now I want to automate the copy ansd paste special

I am using

ActiveSheet.PasteSpecial Format:="Text", Link:=False, DisplayAsIcon:= _
False
This gives the original error of the dates not being true dates. Now they
are formatted to the left by default and any calulation using the dates fails.

The macro was recorded and does not work despite the fact that the original
action that created the macro worked.

Any suggestions?

--

Dave Peterson