![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Speed is of the essence - Export to Excel Topic Summary: Created On: 26-Feb-2004 16:38 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
We have a process that requires exporting requirements from a module to an Excel spreadsheet. The process exports seven columns of information for each object and in excess of 10,000 objects/rows (using Excel wasn't my first choice but is a requirement in itself). As you can imagine, this is a time consuming DXL script. Currently, this takes a little more than two hours to run (dual 1mHz processors with 1G mem). The script performs these basic functions:
- Filters requirements for export (simple using 'Filter f' and set functions) - With OLE, creates an Excel application and required autoobjects - For each filtered object, - For each respective attribute - setCell - Save file - remove autoobjects Would this process be faster running as a macro from Excel? Or, simply, is there a faster method? Thanks -=[ Bob Padilla ]=- Ciena Corporation |
|
![]() |
|
![]() |
|
Robert,
Having your automation create a .csv or .txv text file of the exported data would be MUCH quicker than any scenario where DOORS is driving Excel through OLE/COM automation. Excel could then load the resulting .csv or .tsv file. Doing the programming from the Excel side would not solve your performance issue. I have done some really nifty things using OLE/COM, but it is just slow by nature. ------------------------- Michael Sutherland michael@galactic-solutions.com http://galactic-solutions.com |
|
![]() |
|
![]() |
|
Thanks for information. Good ideas, just have to rewrite the process now.
Again... Thanks!!! One other question... How do you preserve indentation when posting to this site? |
|
![]() |
|
![]() |
|
Robert,
To preserve indentation when replying use the "Attach Code" button. Also, if you are going to write DXL code please read the "Guidelines for Memory Managment in DXL" I re-wrote some DXL code with using the Guidelines and found my code to execute significantly faster. DXL is a memory pig. It take the memory and does not give it back until after DOORS is closed (I'm surprized nobody has ever mentioned that). So, as you run your code look at the task manager and watch the memory usage skyrocket. Writing more memory efficient code could help your situation also. |
|
![]() |
|
![]() |
|
Yup! I know about the DXL memory issues. I always try to write as efficiently as possible.
Thanks for all of the assistance! |
|
![]() |
|
![]() |
|
Also, if you are going to write DXL code please read the "Guidelines for Memory Managment in DXL" Does any know where I can get this document? Cheers Peter ------------------------- Peter Dawson Engineering Tools Support Group Boeing Australia Limited |
|
![]() |
|
![]() |
|
Here are a few minor speed enhancements I've found. Don't forget to undo them after you turn them on. Especially the undo limit change.
------------------------- David Pechacek AAI Services Textron dpechacek@sc-aaicorp.com David.Pechacek@gmail.com |
|
![]() |
Telelogic DOORS
» DXL Exchange
»
Speed is of the essence - Export to Excel
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.