Rebuild Times Macro giving me trouble - help! 2

[DragonTSD]

thread559-230655

This is directed at Handleman but I will field it to all. This is my first time posting so please forgive any procedural missteps.

First of all, let me say thank you for the RebuildTimes Macro, it's a really useful piece of coding. Secondly, I'm having trouble with it...hahaha. I am trying to run it on a large assembly (~17000 components). The macro seems to quit of its own accord; it's happened three separate times now and it always seems to occur in depth "2", but not always on the same Excel cell, about 3 hours after I initialize the macro. I keep Task Manager open to verify if the macro is done running and all three times the processor has stopped processing data with no error messages.

In my experience, when the macro is done it rebuilds the top-level assembly, reports the two total rebuild times, save time, and file size, then reformats the cell widths; this is not happening. I'm running a 64-bit system, 3.33GHz Core 2 Duo with 8GB RAM. I have made sure that large assembly mode is off, that all components are resolved and that all add-ins necessary are added-in (routing, specifically).

I'm asking for help because I don't really know what to do next. Have any of you seen the macro fail or stop processing data after several hours? I've looked at the VB code and there doesn't seem to be a practial limit to the size of assembly it will process. Is there some other limiting factor to running a macro for several hours that I don't know about?

Any help would be greatly appreciated, thank you.

 

[CorBlimeyLimey]

I can't help with the macro, but have you tried using the Assembly Visualization tool with the SW Rebuild Time property enabled?

 

[handleman]

I never tried it on a 17,000 component assembly... That macro was written before Assembly Visualization was available. I'm not sure if it will do what you need or not, but if it will then it'll do it much quicker than that macro. It's pretty brute-force. You may be running into some type of memory limit. I would guess that since it is stopping on a different cell on different runs. Sorry, I don't really have a whole lot more on this one!

-handleman, CSWP (The new, easy test)

 

[DragonTSD]

CorBlimeyLimey,

Thank you very much...I didn't even know that feature existed...very nice though, it should serve my puposes nicely.

Handleman,

That's sort of what I figured...it is using every last scrap of RAM. no worries, Assembly Visualization solves my problem.

Thanks guys