So my question to this blog https://communities.bentley.com/products/microstation/b/microstation_blog/posts/the-explorer-part-five-the-sheet-index-tab is why do you have to have a workset to have a sheet index. Surely you can have a Sheet Index without one?
Hi Stuart.
Sorry to answer your question with a question but my I ask what are you creating a sheet index of? What is the association of the files in the index?
~HTH
John.
yep
John Frampton said:Sorry to answer your question with a question but my I ask what are you creating a sheet index of? What is the association of the files in the index?
Good question and one I can't answer as we don't user Worksets, as SI's are not available to the No Workset users.
Ok, lets approach this another way. Step back from the key board for a minute, close your eyes and imagine that you have created a sheet index (you have created a sheet index before correct?). What are the files in the index and how are they associated to one another?
Stuart
What is your objections to using worksets....... from my point of view there is so much you can do with them and their configurations, that actually save you and the teams time.
Ian,
No objection. I just can't get them to work the way I want and with the folder structure that we use in the office for all projects. When creating a workset I want it to point to an existing project folder and I don't want any folders created. Have tried this but it just doesn't work.
Stuart. You need someone like Ian to help you then as that's exactly what we do. Our Workset points to existing project folders. We create new worksets simply by copying an existing .cfg file and renaming it for the new project. This allows our users to select a workset and it then points them to the correct folders for that project. It doesn't create them. We do that as the project folders often need to exist before we start using Microstation.
I completely agree, that's why I have developed a CONNECT setup that has configurations/Workspaces.
/Worksets that looks like V8i, simple to understand and very easy to manage.
Its all in one place................
With worksets you can...
Get the project folders mapped so the DWG go into the correct folder, the PDF also go into the correct folder, When you Ref attach it opens in a predefined project folder, which makes navigation easy.
You can also add things like,......
Project specific Display Rules, Reports, title blocks that read project data ie project number.. the list goes on
stuartw said:and I don't want any folders created
Setting the following variables to nothing will do that.
_USTN_WORKSETSTANDARDSUBDIRS = _USTN_WORKSPACESTANDARDSUBDIRS =
There is a disconnect between the UI and these variables.
H Folks,
If you need a workset for each sheet index where am I going to find someone to work for peanuts to manage 7000 or 8000 worksets just so I can use this function. And if we need more than one index per project, which is usual, multiply that number x 3 or 4.
This sounds like a great function but you must be able to make as many sheet sets as required without them being connected to worksets. They need to be connected to a project folder set with the "Sheet Index file" located in the project folders.
Because we have so many live projects it is not practical to use a workset for each so we have sorted projects into project types with a workset for each type, only 5 or 6 types at this stage.
Hopefully a workable solution will come eventually.
Hi John,
John Davidson said:someone to work for peanuts to manage 7000 or 8000 worksets just so I can use this function. And if we need more than one index per project, which is usual, multiply that number x 3 or 4.
I am just wondering who is managing the Sheet Index 7000/8000 x 3 or 4 Sheet Indexes. Why is a workset more burden some than that?