When I attempt to use No Workspace (Client) -> No Workset Browse uses the previous Workspace name to look for a folder No Workset\DGN.
This results in an error and does not allow browsing for files using No Workspace -> No Workset
Timothy Hickman
CADD Manager | CADD Department
timothy.hickman@colliersengineering.com
Main: 877 627 3772|
1000 Waterview Drive Suite 201 | Hamilton, New Jersey 08691
Can you clarify this. I'm a bit confused
Unknown said:@Ian - no , there is not a config file for this.
Unknown said:@DavidG - I do have a NoWorkspace folder and in that I have a NoWorkSet.cfg - that is it, no other files or folders.
@DavidG - But can you tell me what controls the location of the No Workspace option (see below). Is there a cfg file that this calls up? - there is no configuration to control this.
Unknown said:But can you tell me what controls the location of the No Workspace option
Can I tell you? I have no idea. I still don't understand why something that suppose to do nothing requires a location and a workset, let alone how or what you are internally searching for to determine the proper location of nothing.
I point workspaces to look on my server where I have my project workspaces and those workspace configs point to locations where I keep my project worksets.
Take a look at (but DON'T change) msconfig.cfg, try a search in the text for "nowork" just to find the right area...
Lines 301 to 306 define the place where NoWorkSpace/NoWorkSet.cfg lives.
In my test setup with drives P (= project data: WorkSpaces/Worksets) and W (= resources: Organization) I can reproduce the information message (note this is not an error message, it speaks the truth, MicroStation is looking for a file and it is not there!) by deleting the copy of NoWorkSpace/NoWorkSet.cfg I put there as described in Solution 1 below.
I offer two solutions:
The easiest: Copy NoWorkSpace/NoWorkSet.cfg to the place it's looking.
No one likes untidy folders so in C:\ProgramData\Bentley\CONNECT Edition\Configuration\WorkSpaceSetup.cfg which is where I assume redirection to your equivalents of P and W is being done add a variation of the if loop contained in msconfig.cfg, change the two instances of the variable _USTN_WORKSPACESROOT to _USTN_ORGANIZATION where indicated:
In my case this is:
# To hide the NoWorkSpace folder from the users
%if !defined (_USTN_WORKSETCFG) && exists ($(_USTN_ORGANIZATION)NoWorkSpace/NoWorkSet.cfg)
_USTN_WORKSETCFG = $(_USTN_ORGANIZATION)NoWorkSpace/NoWorkSet.cfg
_USTN_HAVEWORKSET = 0
%else
_USTN_HAVEWORKSET = 1
%endif
Where I have already defined:
_USTN_ORGANIZATION = W:\MstnCONNECT\Organization\
Copy NoWorkSpace/NoWorkSet.cfg to the matching location
This can be anywhere you like (on your LAN!) as long as the location and the if statement match. You could change the folder name but if it is out of sight why bother, that will only obscure its purpose.
Marc
Answer Verified By: DavidG
Unknown said: but if it is out of sight why bother, that will only obscure its purpose.
What is obscure it why the file needs to exist at all. Is its sole purpose appears to be so we don't get an error message?
So far we've just gone in circles. It needs to exist because the program is looking for it. Is that its whole reason for existence?
Unknown said:If it is likely to be a common choice, why so?
Unknown said:MicroStation has always been designed to use project configurations
why shouldn't there be an invisible way to do without, to just fire up and get on - in a single user environment for example?