nop. my parts are on my network. I installed standard parts on my hard drive due to it not working on the network. When done, i open configuration manager and point to my network location. now all my hardware is in the same spot so when opening assemblies there's no errors.
More clarity needed: so installing on your local hard drive was a temporary issue because the network didn't work? Then later it did? What happened to the local drive install?
STandard parts which i loaded on my hard drive stays there, i do not remove it. If you remove it nothing will work. All i'm doing is getting access to the configuration wizard so i can link it to my network. If i create a new data base. I loose all my hardware i've created over the years. It sucks when you open a big assemblie and it can't find the hardware.
I'm sorry, I'm still confused. So the master files and the generated files reside locally? And others on the network are actually accessing your hard drive when they request a part? What is the path to those parts in rev man, etc.?
I have access to SP administrator but I didn't load the database to my hard drive. I just loaded SP Admin locally.
@TDB, I think I know what you mean. You work on your network for save keeping and installed your standard parts on your harddrive and generate the parts on your network.
It is easier when you work alone, we have 6 engineers that all work with standard parts. To the database runs for everyone on the network but the administrator tool is on my PC.
Almost the same but completly different, to install the administrator on the network via my PC is so complicated that I need help with every new version
Yeah, we have the database and generated parts on the SQL server and the administrator on a local machine.