Announcement

Collapse
No announcement yet.
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Unable to open asdoc tables in word

    Hello people! As the title already states I cannot open asdoc tables anymore in word. Instead, I get the following error message once opened:

    Word was unable to read this document. It may be corrupt. Try one or more of the following: Open and Repair the file. Open the file with the Text Recovery converter.

    So far, I tried each option given on word but did not solve my problem.

  • #2
    I don't use asdoc, which is from SSC, as you are asked to explain (FAQ Advice #12). It is a versatile command, but I never want to do what it does, so I stop there. Also, I am no kind of expert on MS Word.

    But some comments are still possible!

    This kind of problem post is very difficult to debug. No data example, no Stata code, a file we can't see, software (MS Word) that many of us never use (believe it or not).

    What you could do is

    0. Try looking at the file in other software. If you try to open it in a text editor or try to type it in Stata you may see a mess of characters but occasionally it is obvious that it is garbage and/or that it is some other kind of file. Many file formats start with a preamble of meta data or overall summary information. In Stata before type first

    Code:
    set more on
    so that the file doesn't just shoot past.

    1. Post simple reproducible code using asdoc and some mutually accessible data (e.g. a dataset you give us or one bundled with Stata). Tell us whether you can open the result in Word. Other people with access to asdoc and MS Word can check too.

    2. Check the filename extension(s) you used. For example, with other commands there is a default file type that is output yet people think or hope that giving another extension is enough to change the file type. As a silly but concrete example, Stata's own graph file format has a default extension .gph but using any other extension in a saving() option will just change the name of the file, not its internal format. I have no precise knowledge on whether that might apply here.

    3. Report more details on your use of Word. It will do no harm if you specified the version of Word you are using and the operating system. Small and even large problems can emerge in trying to open files produced by or for one version of Word in another.

    Those are guesses in the dark based on what you say.

    Comment


    • #3
      Originally posted by Nick Cox View Post
      I don't use asdoc, which is from SSC, as you are asked to explain (FAQ Advice #12). It is a versatile command, but I never want to do what it does, so I stop there. Also, I am no kind of expert on MS Word.

      But some comments are still possible!

      This kind of problem post is very difficult to debug. No data example, no Stata code, a file we can't see, software (MS Word) that many of us never use (believe it or not).

      What you could do is

      0. Try looking at the file in other software. If you try to open it in a text editor or try to type it in Stata you may see a mess of characters but occasionally it is obvious that it is garbage and/or that it is some other kind of file. Many file formats start with a preamble of meta data or overall summary information. In Stata before type first

      Code:
      set more on
      so that the file doesn't just shoot past.

      1. Post simple reproducible code using asdoc and some mutually accessible data (e.g. a dataset you give us or one bundled with Stata). Tell us whether you can open the result in Word. Other people with access to asdoc and MS Word can check too.

      2. Check the filename extension(s) you used. For example, with other commands there is a default file type that is output yet people think or hope that giving another extension is enough to change the file type. As a silly but concrete example, Stata's own graph file format has a default extension .gph but using any other extension in a saving() option will just change the name of the file, not its internal format. I have no precise knowledge on whether that might apply here.

      3. Report more details on your use of Word. It will do no harm if you specified the version of Word you are using and the operating system. Small and even large problems can emerge in trying to open files produced by or for one version of Word in another.

      Those are guesses in the dark based on what you say.
      Hey, Nick

      I looked more into the 2nd possible explanation for my problem, but it did not solve my problem. I did, however, realized that asdoc was unable to produce tables Granger causality-test tables but regressions worked. Thus, I suspect that my issue was more related to the software being unable to produce Granger test tables. Nevertheless, thank you for your support!

      Comment

      Working...
      X