Print
Move command only copies files
Posted: 19 June 2008 11:22 AM   [ Ignore ]  
Sr. Member
RankRankRankRank
Total Posts:  119
Joined  2008-05-14

In 5e when I move a file from my desktop to Newforma Project Files, using the Windows context menu Move command, Newforma only copies the file instead of moving it. Is this the programmed behavior?

Profile
 
 
Posted: 20 June 2008 09:22 AM   [ Ignore ]   [ # 1 ]  
Member
RankRank
Total Posts:  37
Joined  2008-03-11

Hi

Can you explain the procedure that you are using in more detail?

Here’s the way it should work:

left-click drag/drop a file from your desktop into Newforma Project Files activity center should copy the file

right-click drag/drop a file from your desktop into Newforma Project Files activity center should present a context menu with: Move, Copy, Cancel. Move will move the file into the folder (removing the original), Copy will copy the file into the folder (preserving the original) and Cancel will do neither.

Faan

Profile
 
 
Posted: 20 June 2008 04:56 PM   [ Ignore ]   [ # 2 ]  
Sr. Member
RankRankRankRank
Total Posts:  119
Joined  2008-05-14

I’m using Move from context menu. NF is copying file and leaving original.

Would indexing latency have an effect on this operation? Ours is 21 hours since we just batch migrated a lot projects.

Profile
 
 
Posted: 23 June 2008 07:23 AM   [ Ignore ]   [ # 3 ]  
Member
RankRank
Total Posts:  37
Joined  2008-03-11

No, indexing shouldn’t affect it. The operation is performed synchronously on the client machine, meaning it happens right away on your computer. Or it should.

The move operation consists of two distinct steps, a copy followed by a delete. The delete may not be successful due to permissions problems, for example. Since you stated that the file is on your desktop, it’s unlikely that you don’t have permissions to delete it, but you should check that anyway.

Sometimes files or folders cannot be deleted or renamed due to ‘another process accessing the file’. If this is the case, close the process accessing the file. Occasionally, you will find that there is no process accessing the file but Windows thinks there is. The only recourse that I have found in this case is a system restart.

Hope this helps,

Faan

Profile