How can 2 cells have the same values, such that when I edit either cell the
change is reflected on both?

It is not possible without using some sophisticated features of event
listening and macros. But one should ask the question: what would be the
benefits? You can refer the second cell from the first one -- something like
A2: =A1, so A1 and A2 will both have the same value and each time you change
A1, A2 will change.

pls help wrote:
How can 2 cells have the same values, such that when I edit either cell the
change is reflected on both?

This macro will do as you describe.........

Private Sub Worksheet_SelectionChange(ByVal Target As Excel.Range)
If Target.Address = "$A$1" Then
Range("a2").Value = Range("a1").Value
Else
If Target.Address = "$A$2" Then
Range("a1").Value = Range("a2").Value
Else
End If
End If
End Sub

Vaya con Dios,
Chuck, CABGx3



"pls help" wrote:

How can 2 cells have the same values, such that when I edit either cell the
change is reflected on both?

On my version of Excel 2003, if I am in A1 and type 444 then press the down
arrow, A1 is being updated with the value from A2...

I would recommend that you replace the first line:
Private Sub Worksheet_SelectionChange(ByVal Target As Excel.Range)
by:
Private Sub Worksheet_Change(ByVal Target As Excel.Range)

Interesting.....good catch.
Thanks for the heads-up.

Vaya con Dios,
Chuck, CABGx3



"squenson" wrote:

On my version of Excel 2003, if I am in A1 and type 444 then press the down
arrow, A1 is being updated with the value from A2...

I would recommend that you replace the first line:
Private Sub Worksheet_SelectionChange(ByVal Target As Excel.Range)
by:
Private Sub Worksheet_Change(ByVal Target As Excel.Range)

Chuck,

You will also have to have a line:

Application.EnableEvents = False

before any changes are made to the sheet and:

Application.EnableEvents = True

before the End Sub to stop the code firing multiple times. For me in XL97
it fires 198 time before VBA thows in the towel.

--
HTH

Sandy
In Perth, the ancient capital of Scotland
and the crowning place of kings


Replace @mailinator.com with @tiscali.co.uk


"CLR" wrote in message
...
Interesting.....good catch.
Thanks for the heads-up.

Vaya con Dios,
Chuck, CABGx3



"squenson" wrote:

On my version of Excel 2003, if I am in A1 and type 444 then press the
down
arrow, A1 is being updated with the value from A2...

I would recommend that you replace the first line:
Private Sub Worksheet_SelectionChange(ByVal Target As Excel.Range)
by:
Private Sub Worksheet_Change(ByVal Target As Excel.Range)

Hi Sandy.........
I bow to your much greater experience, and wish to learn all I can. In this
instance, I intentionally left those lines off and do so as a general rule
anymore because I like to see things flash as the macro progresses.....sort
of in lieu of a progress indicator. I was not aware that their absence could
actually affect the operation of the macro itself. I use '97 also, and see
no evidence of multiple firings here. How did you conclude that the macro
had fired 198 times?

Vaya con Dios,
Chuck, CABGx3


"Sandy Mann" wrote:

Chuck,

You will also have to have a line:

Application.EnableEvents = False

before any changes are made to the sheet and:

Application.EnableEvents = True

before the End Sub to stop the code firing multiple times. For me in XL97
it fires 198 time before VBA thows in the towel.

--
HTH

Sandy
In Perth, the ancient capital of Scotland
and the crowning place of kings


Replace @mailinator.com with @tiscali.co.uk


"CLR" wrote in message
...
Interesting.....good catch.
Thanks for the heads-up.

Vaya con Dios,
Chuck, CABGx3



"squenson" wrote:

On my version of Excel 2003, if I am in A1 and type 444 then press the
down
arrow, A1 is being updated with the value from A2...

I would recommend that you replace the first line:
Private Sub Worksheet_SelectionChange(ByVal Target As Excel.Range)
by:
Private Sub Worksheet_Change(ByVal Target As Excel.Range)