A lightbulb just went off for me ion the use of the PTC_WF_ROOT variable. Do I understand you right that setting PTC_WF_ROOT will make Pro/E store the stuff they bury buy default deep in the windows user profile folders to a folder of my choosing? That would be the favorites in WF4 & WF5 and now the creo_parametric_customization.ui file in Creo 1.0+. If so, can I set it to a network path? That would solve my issues with Creo and .ui files.
Oh, and setting 'load_ui_customization_run_dir yes' will force Creo 1.0 to load & store the creo_parametric_customization.ui file from the working directory.
The funny this is that I AM able to write to that directory, or at least Creo is, when I make changes to my .ui file. That could be, though, because Creo was installed as admin, and since it was installed as admin, it can write to that dir.
Heck, I'm even part of the Administrators group currently (normally I'm NOT, but had to be added to do some stuff with batch files for some testing that we were doing), and I still can't get to the .settings dir!
Business Continuity with Creo: Learn more about it here.