Hi,
how to make my personal.ucf is written in the same directory as my personal...UPF (on the network)
I've created:
_USTN_HOMEROOT = $(_USTN_ORGANIZATION)USERS/$(USERNAME)/$(computername)/
_USTN_LocalUserAppDataPath = $(_USTN_HOMEROOT)/
but still the personal.ucf is written to:
C:\.....\AppData\Local\Bentley\OpenBuildingsDesigner\10.0.0\prefs (on the computer where OBD is installed)
what other variable do I have to change too
regards,
Rik
Interesting enough, I tried similar this morning as I'm working on a CE build for a firm. I tried to undefine the variable in one of my Organisation cfg files and got the same error. Changed the undefine to the appl cfg and it worked fine.
Sounds like this needs more investigation and changing if it's true.
Hi Bob,
unless you actually used %undefine in your cfg file, which should have been %undef, I don't think I can provide any help.
Hi Mark,
I am currently working through changing all our Bentley software to the CONNECT version, and I have come up against the above .ucf file problem while working on OpenBuildings Designer Update 5.
I have tried the fix you suggest of undefining _USTN_USERCFG but all I get is an error and the program halts.
The error message is:
Exiting, not found, [C:\Program Files\Bentley\OpenBuildings CONNECT Edition\OpenBuildingsDesigner\Config\msconfig.cfg],
line 291
This is the line in mcconfig.cfg "% error Exiting, $(_USTN_USERCFG) not found"
I tracked the cause of the problem to the new line %undefine _USTN_USERCFG in the WorkSpaceSetup.cfg file.
Everything is normal again when I comment this line out.
I have more CONNECT programs coming into the office and quite a few client CAD builds to work through, but I need to get this one sorted first.
Do you have any further suggestions, or am I doing something wrong?
Sean, I'm completely with you on this.
The previous situation was that this config could be redefined by modifying mslocal.cfg or other files in the system folders. This required good understanding of the configuration syntax and often complex use of that syntax. A large portion of our user base lacks that understanding or has not interest in learning it so we are working towards user-friendly solutions while doing our best to ensure that the more complex environments and knowledgeable people like you are still able to tune and protect their systems.
One of the objectives of the CE configuration changes is to have a clear distinction between what is installed with the application which should be left alone and the user's configuration that can be customised as required and protected appropriately. In terms of your approach essentially what has changed is the point at which your hta files start to take effect.
Regards
Marc
Marc, in the past the ucf location was set, but we could always change it at other levels. I agree that there are issues with what a user can change, but IMO this one is the least of the problems and one more the domain of the admins. Now the config is locked, not ideal, but at least it can be undefined.
The whole reason I use the cascaded cfg's is to keep users from being able to make changes. I can set variables at any level (company, site, project.client) and then lock them before the users can do any damage.