![]() |
Telelogic System Architect (steve huntington) | ![]() |
Topic Title: VBA display dialog window Topic Summary: Created On: 21-Jun-2006 10:53 Status: Read Only |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
I'm fairly new to System Architect, but am developing some VBA add-on components for one of my colleagues. One of these components is a search facility to search through data on a diagram.
A list of search results are then displayed, but I want to be able to allow the user to select one of the search results and click a button to display the full details. My question is this - in VBA how can you launch a System Architect window that will display the specified record's full details? Hope this makes sense! Thanks Dan |
|
![]() |
|
![]() |
|
Greetings,
I would like to use the VBA feature to create reports. Can you provide direction on customizing reports? Thanks, Debi |
|
![]() |
|
![]() |
|
There seems to be two subjects to your question: |
|
![]() |
|
![]() |
|
Thank you for replying. Attempting to create Word templates using VBA. When you do not see a particular type of word report that you would like to generate from the tools drop down menu. For example if you created a report using Explorer Relationship Report you would then create a word template that would extract the selected diagram in a deliverable format. (currently coping & pasting the diagram). Would you use VBA to do this or some other method to create a word document?
Thanks, Debi |
|
![]() |
|
![]() |
|
Hi Debi, All of our Word reports are custom built using VBA. We are moving beyond this though. |
|
![]() |
|
![]() |
|
Duane (and other heavy hitters!), ------------------------- Thanks, MattS |
|
![]() |
|
![]() |
|
Matt,
Support is limited in terms of documentation and Googling. In fact I found the documentation not only dishevelled and the examples convoluted with irrelevant code, but I found that some of it was written so badly that they forgot the names or labels they gave properties from one page to the next. So a step by step example produced more confusion than it did help. The database schema does not seem to have changed significantly at all. In fact we previewed the SA XT which is yet to be released and despite it being web based, the schema is exactly the same. XT is .ASP based by the way, using XML and so on (for those interested). I chose direct access over the SA object model for the following reasons: 1. It avoided being tied to a particular language or application. This allows scope for growth into other areas, for example, Java. 2. We could achieve much faster results, in fact we reduced one report from 10 minutes to 2 to 2 and a half minutes by not iterating through the object model. 3. The object model's methods are inconsistent in the way they behave and badly documented. 4. The object model insisted that SA be open during reporting and often meant that diagrams needed to be opened on the screen to gather information. There was one way around this I found before moving to recordsets, but it was long-winded and required moving from the smallest items to the top level to gather info. Currently we are using ADODB recordsets and 98% of the time we only read from the database. The only occasion we write is in overnight job to release definitions that remain locked at the end of the day and some tools to check in diagrams. If another database is set up and a link provided to the Encyclopedia's database, then you can build read-only views to query and further reduce the risk of anyone writing to the database unintentionally from outside of the system. Our move to WordprocessingML is going to produce some cool benefits. We are looking at XSLT (Transforms) to convert the data into web pages and so on. So not only are we not tied to the VBA paradigm but our reports will be available to be transformed into many structures and architectures. They can be consumed by any XSL/XML technologies. Perhaps even RSS??? It also means that our reports will be able to be consumed by later technology using XSLT's and we won't caught with a defunct VBA environment producing our documents. We are excited by the possibilities. ![]() Edited: 18-Aug-2006 at 04:39 by Duane Hennessy |
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.