And I believe this is a bad practice. It's a lot easier to segregate data from the OS. Tell windows that "My Data" is on D: if you have to.
I'd encourage people to put *all* parts they're looking at in the database then move/copy the ones that make get a part number (a part you actually use) into that database and then to the database for each product. The engineer can then shadow that entire project on the PC or simply point to it on the server. It's nice to have
*all* the data for a project in one place.The only drawback I see here is that one wouldn't necessarily get the latest datasheet, but this can be a good thing for products that are in production.
...and I believe this is a bad practice. I've segregated the OS from programs and data for a long time, but with this laptop decided to go the M$ way and put everything on C:. Bad move. I'm slowly going to start moving stuff off C: to d:, but I'm afraid to partition the disk now. I'm buying a personal laptop in a few weeks and will buy a spare disk to go along with it so I'll try when I can make a clone
This is goodness. Have you tested your disaster recovery scenario (i.e. take a blank PC and do a full restore and regression on a product)? I don't trust backup processes until their proven to do something useful.
When I moved here from NY in '93 I pitched nearly everything. I didn't pitch it on purpose but I haven't seen my mustard bible since (it's only a second edition, my first grew legs 25 years ago).