ThisApplication.ActiveDocument fails?

[mrattray]

I have a macro that is called from a loop cycling through all the sheets in a drawing and exporting information from the titleblocks to a property matrix that is then exported to excel. These macros have run jus fine and have not been modified for a few months now. I now have a drawing that's a bit larger than most, 66 sheets. I've ran this macro through it several times before but now it decided that it doesn't like a certain sheet. It fails with an "Automation Error" on the oDoc=ThisApplication.ActiveDocument line on sheet number 61. What could cause that? What does it mean? Did Inventor loose itself? I haven't a clue where to even start looking for the problem.

[ekinsb]

Can you send me the drawing and a minimal version of your program so we can try and reproduce the problem here?  You can send it to brian.ekins@autodesk.com.

[mrattray]

Brian,

I'd be delighted to have your help on this. I've tried minimalizing the program, but then I can't reproduce the behaviour. I have a suspicion that the problem has to do with a hidden prop set with over 650 props I'm using to transfer data with. I started a pack & go to get an idea of file size and it told me something like 40MB uncompressed. I don't mind sending you that much data if you don't mind recieving it. Otherwise, I'll have to play with it until I can get a minimalized verison that displays the behaviour or find the bug.

Thanks,

Mike

[ekinsb]

Hi Mike,

I'm ok getting a large data set.  I assume it's just Inventor files to exercise the program rather than a lot of code.  It's the code that the most important to minimize. 

-Brian

[mrattray]

Brian,

I just discovered that our attachment limit here is only 10MB. Like I mentioned before, when I slim it down too much I can't reproduce the behaviour.  The smallest I can get it to where the error still occurs is 22.5MB packed and zipped. The bulk of the file is just the drawing itself, there isn't a whole lot of code involved. Is there an FTP site or something you can direct me to?

Thanks,

Mike

[mrattray · Accepted solution]

Well it turns out that reordering the trouble sheet from 61 to 60 somehow fixed the problem. It runs fine now.