Our workspace is set up by project years. There is a workspace cfg file for each year and then in the folder for each year are the workset configuration file. Similar to the delivered workspaces in that like there is an Examples.cfg that corresponds with the Examples Folder. We do not build seperate workspaces for each project, instead in the Examples folder, we would have workset.cfg files. These set rudimentary variables like the year and project number that when combined give the _USTN_PROJECTDATA folder, The we set a couple of MS_RFDIR variables. A number of our workspace years can contain up to 80 different workset variables.
Like
122.0001.01
122.0093.01
112.0650.01
The problem is doing a debug, we see that after running the 2002.cfg which points to the 2022 Folder, (i.e. the examples.cfg point to the examples folder) all the cfgs in the 2022 folder run and ORD sets the MS_RFDIR to all the workset configuration files contents. How do we get the config to just run the workset.cfg file that is set in the manager?
Thanks
how are you using _USTN_PROJECTDATA in ORD ?
Timothy Hickman
CADD Manager | CADD Department
timothy.hickman@colliersengineering.com
Main: 877 627 3772|
1000 Waterview Drive Suite 201 | Hamilton, New Jersey 08691
_USTN_PROJECTDESCR = VISION_PRJ_USTN_PROJECTNAME = VISION_PRJ_USTN_PROJECTDATA = $(SA_PROJECT_FILES)$(SA_PROJECT_YEAR)$(VISION_PRJ)
Where VISION_PRJ IS FROM OUR ACCOUNT SYSTEM
This then sets where ORD open the browse button or the new file button
I'm not sure _USTN_PROJECTDATA has any meaning to Connect/ORD. According to the Help documentation, that variable has been replaced by _USTN_WORKSETROOT, which is the variable to define where the worksets are stored.
While I'm not sure how this would or would not impact your workspace organization, it's possible that, by using the deprecated variable, something isn't as defined as you might think.
MaryB
Power GeoPak 08.11.09.918Power InRoads 08.11.09.918OpenRoads Designer 2021 R2
Mary jumped in ahead. I agree with her post - I don't think the PROJECT configurations work the same - if at all in ORD.