Jump to content

RDS Casa

Member
  • Content Count

    170
  • Joined

  • Last visited

Community Reputation

3 Neutral

1 Follower

About RDS Casa

  • Rank
    Journeyman

Personal Information

  • Occupation
    Architect
  • Location
    United Kingdom

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. RDS Casa

    Anyone using Database?

    Dear all, an update on progress regarding notes, data bases and work flows. Anyone who finds this helpful, you have my brother to thank for this. Sadly I'm not a VB coder. Attached is a text file with a script written in Visual basic for excel. It allows you to use excel to drive your Vectorworks notes database, where by it runs an export from an excel file, creating: - The A column becomes the description, - The B column becomes the notes (main text content). Tabs become different sections, but as yet it just names them -1, -2,-3 etc, and these need to be changed within VW. But we are looking to resolve this. This means as a team you can use excel to edit, and input into a central data set (and use all the notes and track changes included in this). For those of you using NBS, its possible to export into excel using a few methods, then with some simple editing you can have your NBS references etc as notes (NBS used to make a tool to do this, but it stopped working with VW 2016 I think. There was little uptake on it, so NBS stopped supporting it) How to use. You need excel. Maybe it works in google sheets, I’ve not tried it yet but I will. - First turn on the developer tab. Do this via File>options>customise ribbon, and tick the developer tab. - Then open the visual basic editor (far left on my version) - Then click inset > module - Copy and paste the contents of the text file into here. - goto tools >> references and scroll down and tick "Microsoft scripting runtime" to include the libraries that you need - No need to save anything. Just close the VB editor. Every time you want to run the macro, go to the developer tab, click on macros (second left on my version), then run the macro called export. This will save a .xml file where you choose. From VW, go to database controls > choose > click the exported xml, and… all your data is now in the VW database😀 Obviously, we are taking no responsibility for messing up excel files/data files. But all the above worked well for me. I’ll post up if we get the tab naming thing working. Here are some more detailed notes about the code and external data base control, if you are using them… The long random strings in the example files are GUIDs which are unique identifiers that are used by databases to identify objects. Usually they are automatically created whenever you add a new entry to a database table. If you are importing your xml to create new items in the CAD database it probably doesn’t expect to be given guids - it will create its own as it creates each object from the xml entries However, reading the documentation it looks like they can be used by the CAD software to synchronise between its objects and those in an external database (or excel etc) and it’s own items. In which case they may be needed. There is a flag at the top of the code to turn on and off the ability to generate guids in the xml when it creates the file depending on whether the cadsoftware needs them or not. Change to true or false (with in the code in the module) to export with or without guids. Also note that it will generate a new guid for each item every time you export the file. If you intend to use the xml to sync or update entries then you don’t want it to create new guids every time - it will likely create duplicate entries in the cad data - instead it will need to use existing guids and will need some slightly different code to this. ExportToXML2.txt
  2. Hello @BG You are right about the formating, so I thought I would post an update on progress regarding notes, data bases and work flows. Anyone who finds this helpful, you have my brother to thank for this. Sadly I'm not a VB coder. Attached is a text file with a script written in Visual basic for excel. It allows you to use excel to drive your Vectorworks notes database, where by it runs an export from an excel file, creating: - The A column becomes the description, - The B column becomes the notes (main text content). Tabs become different sections, but as yet it just names them -1, -2,-3 etc, and these need to be changed within VW. But we are looking to resolve this. This means as a team you can use excel to edit, and input into a central data set (and use all the notes and track changes included in this). For those of you using NBS, its possible to export into excel using a few methods, then with some simple editing you can have your NBS references etc as notes (NBS used to make a tool to do this, but it stopped working with VW 2016 I think. There was little uptake on it, so NBS stopped supporting it) How to use. You need excel. Maybe it works in google sheets, I’ve not tried it yet but I will. - First turn on the developer tab. Do this via File>options>customise ribbon, and tick the developer tab. - Then open the visual basic editor (far left on my version) - Then click inset > module - Copy and paste the contents of the text file into here. - goto tools >> references and scroll down and tick "Microsoft scripting runtime" to include the libraries that you need - No need to save anything. Just close the VB editor. Every time you want to run the macro, go to the developer tab, click on macros (second left on my version), then run the macro called export. This will save a .xml file where you choose. From VW, go to database controls > choose > click the exported xml, and… all your data is now in the VW database😀 Obviously, we are taking no responsibility for messing up excel files/data files. But all the above worked well for me. I’ll post up if we get the tab naming thing working. Here are some more detailed notes about the code and external data base control, if you are using them… The long random strings in the example files are GUIDs which are unique identifiers that are used by databases to identify objects. Usually they are automatically created whenever you add a new entry to a database table. If you are importing your xml to create new items in the CAD database it probably doesn’t expect to be given guids - it will create its own as it creates each object from the xml entries However, reading the documentation it looks like they can be used by the CAD software to synchronise between its objects and those in an external database (or excel etc) and it’s own items. In which case they may be needed. There is a flag at the top of the code to turn on and off the ability to generate guids in the xml when it creates the file depending on whether the cad software needs them or not. Change to true or false (with in the code in the module) to export with or without guids. Also note that it will generate a new guid for each item every time you export the file. If you intend to use the xml to sync or update entries then you don’t want it to create new guids every time - it will likely create duplicate entries in the cad data - instead it will need to use existing guids and will need some slightly different code to this. ExportToXML2.txt
  3. The more I use the call out tool, the more I think it needs this small upgrade. Already the database callouts have two components to them, the description, and the notes. The call out just needs an option to display: -description only, -notes only, -both. All the framework for this already exists... it just needs this option to become a lot more flexible and versatile.
  4. RDS Casa

    Anyone using Database?

    I'm leaning a little about xml. !!! It seems there is something called a schema, and this can control how the xml file is imported into excel. So, if any has (or has the ability to write a schema) that tells excel how to import into excel, then excel could be the editing software, which could solve the team work flow problems? Certainly this would help for me. Whereby each section from the VW data base imports to a seperate tab in excel, named as per the section name Then within each tab, each note has a row, with the description in one column, and the note text in the next. Then assuming (?) its possible to export using the same schema, all the editing could be done in this way. And use the in-built excel track changes and comments to control revisions with colleagues? for me, I'm just currently trying to find a quick way to bring a lot of good text content into the notes database. Sorry, don't think I'm good enough to create a schema.
  5. RDS Casa

    Anyone using Database?

    Hello, I've just started to use Notepad XML 2007, to try and edit/import a lot of spec notes. It looked promising, but unfortunately the names don't come through to the organisation tree. So I spent a good while naming the notes in notepad. Lucky I stopped after an hour and tested it. It loads fine into VW, but if you then make any changes in VW, it seems to save over all the updated section names and note names, with nothing again!!!! If anyone knows a good external editor, I could build up the spec information in this, and just use VW to place the notes?? OR if any VW tech are reading this, can you get VW database controls to name the entities as per the VW control, so editing them externally is achievable? Sorry its not a useful workflow, but its more that I'm suggesting the use of an external editor to control the text content. Only I've not found a good one yet.
  6. @BG Could I ask what data base editor you use for this? I'm trying notepad xml 2007. Its ok, but it seems if you change the section or note titles in the XML editor, they are lost the next time you edit/save the notes from VW? Thanks
  7. This is visually irritating. In the annotations layer, I was using call outs. I clicked this part of option in the OIP Which cycles through the sub objects for edit. No real reason, I just wanted to see what it did to be honest. It turns part of the call out blue, presumably to identify the bit you are editing. The problem is, its stays blue after editing, and nothing I try gets rid of the blue. Worse, it even appears in viewports on sheets I did not even edit. Always in the same place. Every single sheet now has this blue scar on it. Its not there when I exit the annotations, but always appears in every annotation layer, on every sheet, always in the same place. A complete restart does not resolve this. Please can someone tell me how to get rid of it? Unfortunately I did it on a few before I realised the problem. So now I have 3 blue scars in my sheets. very irritating. Thanks
  8. RDS Casa

    Setting Elevation Benchmarks

    Hello, There is something with this tool I don't understand. The origin of the sheet layer seems to effect the bench mark tool when in "Y value relative to reference elevation" mode ??? So, If I have a line in the design space at y = 10,000. In the design layer, the benchmark tool when on "Y value relative to reference elevation" mode, outputs 10,000, as one would expect. But, make a viewport to that line in a sheet layer, and if the origin of that sheet layer is not on 0,0, it impacts the bench mark tool output when on "Y value relative to reference elevation" mode??????????? Why would it do this? I can see perfectly how changing the origin in the design layer would rightfully change the Y reading, but not the origin of the sheet layer sheet layer? Surely this is irrelevant to geometry I have placed in the design layer. I did not even realise the sheet layers can have their own origins? took me ages to find the reason I would have thought, to maintain consistent benchmark reading across viewports in multiple sheets, the benchmark tool ought really only care about the Y value of the design layer(s) the viewport (s) are looking at? See above how the origin of my sheet layer has some how shifted to y=-85, which is why my bench marks were 85mm out? This is really curious to me, and my worry here is seeing as I don't how my sheet layer origins jumped out in the first place, this means it could happen again, and this would throw out the benchmarks on that sheet, even though the geometry in the design layers has never moved. Whats the story here? Am I using this tool incorrectly? Thanks
  9. RDS Casa

    Data Tags

    Hello Does any one know if its possible to use Data Tags in sectional viewports within the design Layers? I can only get them to work in the annotations layer, which only exists on sheet layers? am I doing something wrong here? My models are rarely complete enough to go straight to the sheets layers; there is almost always an explode and clean up in the design layers first for sections and elevations. Thanks
  10. Thanks @Boh, I shall try this. Certainly it will help by the look of it. Thanks again
  11. Shame. Undermines the point of a database, I mean, may as well copy/base from a word document otherwise. Thanks for reply
  12. Did this ever happen? I can't find the option to re-link to database changes? I also added a request to the functionality today... simply to have an optional tick box in the object info palette to display only the database description, not all the notes.
  13. I don't think this is currently possible (PLEASE do tell me if it is). Its kind of simple ... Just a tick box on the call out tool Object info Palette, that means it can display the description, rather than the note text. That's got to be easy, right? ! This is so that the note text in the database can carry detailed specification information, but the displayed description carries only its description reference. In most cases I only need the reference (eg. "F1.312 Coursed Rubble stone") the detailed spec information can then be displayed using the General Notes tool somewhere else. The general notes tool already has the option to use the description as the left hand column, under "General Notes Display". And then, Vectorworks referring to a .xml file controlled by ODBC control can be used as a powerful spec writer. I don't have to use NBS Without this, it 2 databases talking to each other. Thankyou.
  14. RDS Casa

    Wall Components in Worksheet

    Hello @C.Miguel, Just to report some progress. Good suggestions by @JMR in the forum string linked in my previous post. In short, add the database control: =COMPONENTNAME(1) to the header, the number in brackets denotes the component name it will call up. so my spreadsheet at the moment has headers that run: =COMPONENTNAME(1) =COMPONENTTHICKNESS(1) =COMPONENTNAME(2) =COMPONENTTHICKNESS(2) =COMPONENTNAME(3) =COMPONENTTHICKNESS(3) =COMPONENTNAME(4) =COMPONENTTHICKNESS(4) =COMPONENTNAME(5) =COMPONENTTHICKNESS(5) =COMPONENTNAME(6) =COMPONENTTHICKNESS(6) etc. This lists out all the components as per the original forum post. Albeit in a horizontal line, one row per wall object (which is then summarized to display one row for each wall type in the document). It produces a quite intense worksheet when you have a lot of wall types and a lot of components. Hope this helps.
  15. RDS Casa

    Wall Report

    Thanks @JMR Interesting.... yes, I can get each column to report the next component, thanks. But still not list the components in rows. What this does allow me to do however is to create one row for each wall type, and then list out the components successively in that row, using the IF command to put a blank cell in for walls with less components. Its a very wide worksheet though! The information is there, and is generated automatically and quickly. The output is not so Contractor friendly. But lets see how they take it. Thanks.

 

7150 Riverwood Drive, Columbia, Maryland 21046, USA   |   Contact Us:   410-290-5114

 

© 2018 Vectorworks, Inc. All Rights Reserved. Vectorworks, Inc. is part of the Nemetschek Group.

×