large (200k) html file with nested tables does not load into MS Word

I'm using standard cfcontent disposition headers (ie:"application/vnd.ms-word") to create a large web page to send to Word, but the page (which loads fine in html) either does not load at all in Word, or, it takes Much too long (minutes) to load. I have tried:
- saving the file and loading from disc
- stripping out generated javascript
- removing headers and footers
- testing the resulting html for properly formed tables and such
- bypassing the fusebox stucture
- stripping out hidden tags
- stripping out whitespace, tabs and CRs
.. got it down to about 150k, but...
Does anyone have any experience in this? I'm reusing existing code, so I'm stuck with the level of table nesting (yeah, yeah, I know, use stylesheets for presentation) and with the amount of data. This is a composite report for printing and saving, which explains the size. I really don't want to rewrite a dozen or more existing reports if this problem is not just because of the size and can be resolved by setting a param. At least I'd like to know what the limits are if I have to work around limits.
Thanks for sharing any experience you may have.
- jack

Are you creating any objects in your table? I have found that if you try to open up a document with a lot of inputs, textareas, etc will take a very long time for it to open. I would suggest that you rem out the cfcontent tag and see if you recieve any errors.

No there were no errors or malformed HTML when viewed (without the cfcontent tag) as HTML, that was why it was sooooo annoying.

Solution...
I beat it to death and the final answer was indeed that the existing templates that I was importing had form tags and input tags in them... When they displayed, they looked nice, but it KILLED Word to try to understand them. I could hear a lot of disk thrashing as Word needed way more memory than the 256meg on the machine. So, the result was to go into all the templates and conditionally comment out all the >FORM and >INPUT tags when I needed to import them for printing.. Time went from several minutes (if ever) back to a few seconds as it should have been.

Thanks, Kudos to Ebot, right on the money!
- jack