Hi Everyone
We run SS2 but I've just had my machine re-imaged SS3 was installed. We have a CFG file in the appl folder that breaks SS3 but is ok with SS2. The CFG file contents are
%if exists (\\Networkfilepath\CAD_Build\Microstation\WorkSpace\ADM.cfg) %include \\Networkfilepath\CAD_Build\Microstation\WorkSpace\ADM.cfg %endif
even if \\Networkfilepath\CAD_Build\Microstation\WorkSpace\ADM.cfg is a blank file or non existent the problem occurs.
When the CFG files is in the aapl folder the "Task" toolbar does not appear and the "Main" tool bar is empty.
Any help appreciated.
Here's what the main toolbar looks like
I'm assuming from the blank Main Toolbar that ADM.cfg modifies your interface in some way.
Do you have a copy of ADM.cfg from SS2 so we can see the contents?
Marc
Hi Marc, Thanks for responding. If I open ADM.cfg and comment out everything the problem happens. If I make ADM.cfg a blank file the problem happens. Adn if I delete ADM.cfg completely it still happens.
the only way I get stop it is if I delete the CFG in the appl folder.
Here's the ADM.cfg file contents I use
_USTN_WORKSPACEROOT = \\\filepath\WKGRPS\CAD_Build\Microstation\WorkSpace\ _USTN_USER = $(_USTN_WORKSPACEROOT)users/ _USTN_USERCFG = $(_USTN_USER)ADM.ucf _USTN_PROJECTSROOT = $(_USTN_WORKSPACEROOT)projects/ADM/ MS_VBASEARCHDIRECTORIES = $(_USTN_PROJECTSROOT)vba/ MS_VBAAUTOLOADPROJECTS = H:\CAD_Build\Microstation\WorkSpace\Projects\ADM\vba\log.mvbaMS_VBAAUTOLOADPROJECTS > H:\CAD_Build\Microstation\WorkSpace\Projects\ADM\vba\ADM.mvba%lock MS_VBASEARCHDIRECTORIES%lock MS_VBAAUTOLOADPROJECTS %lock _USTN_WORKSPACEROOT %lock _USTN_USER %lock _USTN_USERCFG %lock _USTN_PROJECTSROOT %lock _USTN_PROJECTCFG %lock MS_CELL%lock _MS_DGNLIBLIST
MS_WORKSPACEOPTS = 2
One possibility is that as _USTN_WORKSPACEROOT is redefined to point to the network some of the files contained in \\\filepath\WKGRPS\CAD_Build\Microstation\WorkSpace\System are not compatible with SS3, but I would expect that to produce some text windows listing such errors .
The next one is that something in the two mvba files is not happy with SS3?
What do they do?