DELETING FILES FROM HARD DRIVE WHILE ASSEMBLY OPEN - ????

[tmathieson]

SO... a user was cleaning up some files while he had an assembly opened.  thinking that Inventor worked like other software, they could not delete a file from disk while it was opened in an assembly.... well, not the case!!. the user selected a bunch of files in Windows exploder, and hit delete.  they did not get any errors about "file is in use", etc..  when they went into the open assembly everything looked right.  they saved the assembly closed it, didn't get any errors.  when they opened the assembly again,  a bunch of the files were missing!!  what is up with this?  how can a file be deleted off a hard drive when  it is opened in an assembly? how can ANY file be delete when it is opened?  even Autocad proper doesn't allow this!!

i have attached a short video showing this....

i know of no other software, Excel, Word, other Cad systems, that allows you to delete a file from the hard disk while you have it opened.

i cannot see the logic behind this (i'm sure Autodesk will have some 'valid' reason..., but i'm not interested.).  is there some setting or something that we are missing here, like "allow deletion of files even when they are opened" checkbox or something?

thanks for any insight

[bradeneuropeArthur]

The files here are loaded only but the files are opened in memory (Graphically only).

This is correct and is as long as I know the case.

There will be no setting to change that, I am sure of.

@johnsonshiue do you share this assumption?

[Frederick_Law]

Why would a user delete the files they are using?

Any good reason?

[CGBenner]

@tmathieson @bradeneuropeArthur 

The explanation that I remember seeing years ago (before I worked for Autodesk) is that the Assembly file is just a graphical representation of the parts and how they are arranged and constrained, but as Arthur said, the parts are NOT open in memory.  


EDIT:  See @johnsonshiue post below for a more correct explanation.  🙂

[tobias]

An easy way to clean up the directory.

Open an assembly, then delete all the parts in the directory.

The expectation is that all parts in the assembly cannot be deleted because its an opened file 

but all unrelated parts will. Unfortunatly that didn't went well, I guess.

[tobias]

But your files are still in the trash folder right ? Hope they are.

Or did you do a shift delete, to permanent delete the files?

[Frederick_Law]

An easy way to clean up the directory.

---

First time I heard of this way to clean up files ..... 🙄

In any program.

It might work if Vault is used.

I don't know how files and folders are organized in your company.

Can't really recommend a way to clean up files.

Pack n Go can collect all files used in assembly.  IDW included.

[Frederick_Law]

Drawings are not opened with assembly.

So they'll be deleted.

[mluterman]

Go into the "Old Versions" folder and restore everything (if they're still there). Unfortunately, you cannot recover files deleted from another physical machine/server on the network location unless you are running software like "Undelete" on the server (they just vanish).

[johnsonshiue]

Hi Folks,

Inventor is a file-based distributed design tool relying on referencing multiple files. To facilitate collaborative data management workflows, the files are loaded in the memory when Inventor opens them. After they are loaded in the memory, Inventor operates directly with the memory. An updated version of the files can be pulled down to the disc. The user can use Refresh (File -> Manage -> Refresh) to reload the files on disc to the memory.

This means that the files on disc can be deleted, renamed, copied over after they are loaded in the memory. Otherwise the above collaborative data management workflows will not work. You will not be able to have multiple team members working on different sections of the same assembly, for example.

Many thanks!

[mslosar]

This is the main reason it isn't recommended to have multiple people working off a network folder (not saying this is happening in this case).  Inventor has no protection for files someone has opened. So, you open a file of a network share and work on it, someone else comes in opens the same file, hits save and moves on. You go to save your work and you get hit with errors saying the file isn't the same file, etc. 

The only actually protection against something like this is Vault.

[tmathieson]

really?  pretty common practice, around here anyways. you're working on an assembly, parts are in your directory.  assembly changes, parts get deleted from assembly. you delete the parts from your directory that you no longer need and you inadvertently grab one that is STILL in the assembly... there is no warning or anything, until you save the assembly and get an error that the file can't be saved....

how do you get rid of junk or unwanted files that have built up in the directory or hard drive?🙄

and in reply to your other posts..

1.  no one deleted the files they are working on ON PURPOSE...as described above, the user inadvertently selected a file that was 'opened' in the assembly on the screen.  AutoCad, Solidworks, Word, Excel, will all give a warning if the file is in use, and not allow you to blow it off to never never land....

2. this has nothing to do with drawings.   as stated in my original post, this has to do with being 'allowed' to delete files when the user has them opened in an assembly .

[tmathieson]

yes, we have run into this also, in another scenario.

"Inventor has no protection for files someone has opened"... still trying to get my head around this......

thank you all, for your responses and comments.  the files in question were created thru use of an inhouse ilogic rule, so easy enough to recreate them.  it is just this concept of files not be "protected" that i can't get my head around. 

guess we will just have to get bigger and bigger and bigger hard drives, and not delete anything...

[guttercleaningkansas34]

In my case, I just deleted the whole back up of my website by a mistake. It was just a traumatic night then. I had to startover.