project file management

[bradipo666]

hi guys, I've already read all threads about project file management though I would like more tips... in the office we are in two, we obviously work on two separate positions and both in the same room (gomito a gomito to understand us..) sometimes it happened to have to work in the same project: Maybe one works on a sub-assieme and another works on another sub-assieme. we intend to buy a network hard disk where to "post" all files and be able to access both from the office through lan and from the outside via the internet... I want to know how to better manage project files. For example: if I copy all part-assieme files etc on the network hd (and I delete all copies from the hds of the two pcs), then how do I have to behave with the project files? Where do I make them? ... do I create one on the network hd or two equal on the two pcs??? If I do not use the vault, do you not recommend working on the same project at the same time?? What could be the problems I might encounter?? thanks

 

[diegus]

If I understand correctly you both work on your pc, how do you share files?
cmq the brutal copy of the files together, parts, dwg etc. in the new folder on the network hd works as long as you create a project file with the well set work area.
the project file create it in the folder where the files on the network hd are contained, then on each pc select this project with the command "cut".

the problem now arises with the elements of the contained center, until now where you saved them?
sure the best method would be to use the pack&go without forgetting to remake settings in the application options


I think it's not exactly something for not really experienced users.
consider using the network hd only for future jobs and leave everything else on individual pcs.

or consider starting using the vault and using the autoloader to import everything into the database.
this solution is definitely the best since you would not be forced to always work with the network files all at the expense of speed (inventor suffers a lot of slow access to the files). while with the vault you always work on local files.

Good luck!

 

[bradipo666]

Thanks for the diegus answer! Yes, we both work on your pc. I just arrived in this office and found this situation: all files are stored on one (and I only say) hd (the one of the laptop...) which is connected to the wireless network. then from my pc (fix), by cable, I go to read and edit files without copying them on my hd, I amount the project files with "cut". until now we have not had big speed problems, even because they are simple enough assemblies... As for the content center I have actually never placed the problem, but I usually avoid inserting bolt screws and what else if not strictly necessary. . .
I had thought of a network hd so we could transfer all files first to have a backup copy of all jobs, then maybe trying to earn something in terms of speed that never hurts! Do I necessarily have to use vault to work simultaneously on the same project?? I am not very experienced, it is true I have never used it but it makes me a bit afraid I am vault:/

 

[GiGa]

I work alone but by two posts (house and office) and very simply I have all the files on the nas of the office (to which I connect vpn away from home).
for the management of the content center I set the default folder always on the nas (in my case an external folder to the project where there are all the c.c. components generated over time) and never had problems.
purtruppo, having a adsl to only 1mb of upload in the office, for more "corposi" projects I have to copy everything (at least the modified files) locally on the home pc and at the end of the day synchronizzo with the nas.

of course in my case, however, I'm just accessing files... for the management of contemporary accesses I think it agrees to go of vault..

 

[Peppe]

purtruppo, having a adsl to only 1mb of upload in the office, for more "corposi" projects I have to copy everything (at least the modified files) locally on the home pc and at the end of the day synchronizzo with the nas.

of course in my case, however, I'm just accessing files... for the management of contemporary accesses I think it agrees to go of vault..

Wouldn't you want to use the vault even if you work alone? the vult when you open a set does nothing but load the whole project locally then when you decide to release a more updated version of the project copy it all on "server". you would avoid synchronizing by hand every time

 

[GiGa]

Surely... in fact it is already in quote... I just expect to have some time to format everything and start from scratch with a clean installation (as well as a new workstation for home). .

Unfortunately, what has stopped me so far is that having never used it "seriously", I know I have great shortcomings in the use of vault... So, in addition to the installation time, I have to also consider the training to do a lot of tests before using it for work.

 

[bradipo666]

Uhm..so from what I understand you recommend using vault if I want to work simultaneously on the same project... for now, given the reduced times, I will do as giga says and avoid working both on the same project. next step will surely learn to use vault... from where could I start? ?