Re: How to save after getting dropped from host

[Brian Parkins <goodprophet.bp@xxxxxxxxx>]

I confess I have experienced similar problems in the past - but like 
you, I've not been able to repeat it. (I've got around it by recovering 
the source from RemoteSystemsTempFiles.and saving to the server once 
connectivity has been re-established.)

I was trying a simple test by just disconnecting from the server once 
the member has been opened. I guess the "bug" only rears its head if 
there is an actual network failure - something I can't easily reproduce.

The Plot Thickens!

Brian.

On 21/11/2018 16:12, Jon Paris wrote:
> There must be some weird bug in RDi that causes this Brian.
>
> I was certain that I had done what you describe - but also remembered having issues in the past.  Sure enough when I checked it for Roger's question I found I couldn't do it.
>
> It appears that if a) A member is open and b) the connection subsequently drops then even if the connection is made again then RDi subsequently treats the file as being local and will not offer anything other than local destinations for Save As.
>
> This problem is also responsible I think for some of the occasions where I have edited the source, saved it as normal, and then compiled - only to find that what was compiled was the old version of the program.  When this happens sometimes a restart of RDi has cured it - at other times it requires creating a new member and copying the content of the original in it and saving it that way.
>
> I've never reported it as a bug (although I've mentioned it to the developers) because I can't get it to repeat on demand. It just happens sometimes.
>
>
> Jon Paris