Sounds like RDP thought it was working offline with regard to that connection,
so it opened the cached version. Maybe a communications thing caused by using
the old alias?
Dave Shaw
Mohawk Industries
----- Original Message ----
From: Peter Thomas <Peter.Thomas@xxxxxxxxxx>
To: "WDSCI-L@xxxxxxxxxxxx" <WDSCI-L@xxxxxxxxxxxx>
Sent: Wed, March 6, 2013 10:47:21 PM
Subject: [WDSCI-L] Latest member source changes not being retrieved
_______________________________________________________________________________________
Note: This e-mail is subject to the disclaimer contained at the bottom of this
message.
_______________________________________________________________________________________
I wonder if anyone has experienced the following behaviour.
One of my colleagues has recently started using RDP 8.5. He discovered that he
wasn't retrieving the latest changes people had applied using SEU.
I tested this myself on his PC and even though I was using Ctl Shift A it did
not retrieve the latest change I had just made using SEU.
I even opened the member in RDP and then tried to open it at the same time in
SEU. It gave me a member locked error. The same happened if I did the opposite.
Opened it in SEU for edit and then tried to open it in RDP. It gave me a member
locked error.
However if I made a small change in SEU and then saved it. Then opened it in
RDP, the change was not visible.
I then noticed that the connection he was using was a previous alias of the
machine name. I changed the connection to use the current name and everything
started to work OK.
When I pinged the alias name and the current name the return IP address and name
were the same.
I can't explain what was causing the problem. It seemed to be keeping a local
copy of the changes.
midrange.com
