In industry where there are many parts for a product, and many vendors for parts, vendors for sub-assemblies, and revisions of them all, storing in a single file quickly becomes unwieldy. Creating BOM's, revision BOM's, etc. becomes an issue.amartino wrote: ↑Wed Apr 01, 2020 12:41 pm Thanks
I don't know in general. I'm trying to use it for woodworking and the ability to have parts in the same project file in Assembly4 was really convenient. There isn't much complicated parts to work with in that case and having to have splits into files would be an overhead.adrianinsaval wrote: ↑Wed Apr 01, 2020 3:05 amAs for using different files for each part, that's the standard approach for assemblies I think
For smaller projects or personal use probably not an issue.
Also, back in the 1960's everyone thought having a console TV/stereo/radio was the in thing...until they realized when one part died and the repairman had to take the console to the shop, they now had no TV, stereo, or radio until it returned.
My point here is that having one file get corrupted and losing the entire project is something to think about.
Of course proper backup regimens can make all the difference.