• Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
  • Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!
Collapse

You are not logged in or you do not have permission to access this page. This could be due to one of several reasons:

  • You are not logged in. If you are already registered, fill in the form below to log in, or follow the "Sign Up" link to register a new account.
  • You may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
  • If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.

Previously on "debugging documents"

Collapse

  • cojak
    replied
    Originally posted by Addanc View Post
    Could try opening it with Open Office, Star Office (ancestor) always used to be better at recovering info from Word documents than MS Word.
    Oh yeah, I've done that before now - I forgot about OO.

    Leave a comment:


  • Sysman
    replied
    Originally posted by Addanc View Post
    Could try opening it with Open Office, Star Office (ancestor) always used to be better at recovering info from Word documents than MS Word.
    I've used Open Office and even hexdump to get at stuff that won't display.

    Leave a comment:


  • Addanc
    replied
    Could try opening it with Open Office, Star Office (ancestor) always used to be better at recovering info from Word documents than MS Word.

    Leave a comment:


  • cojak
    replied
    I'm not a dev techie - I don't use Word for anything complicated, the most I'd c0ck up would be styles and tables...

    Leave a comment:


  • norrahe
    replied
    apparently they said it was a 10k page doc, what cojak said is the only other options he could think of.

    Still not the end of the world, he's got another interview with them anyway.

    Leave a comment:


  • NickFitz
    replied
    I could pretend to know a lot about it, or I could point you at Troubleshooting Word 2007 Documents More Easily Using VBA in the MSDN Library

    Although my first answer would probably be "I'd call IT and ask them why the hell they'd removed the Script Debugger from the Office installation."

    Bonus MSDN Library hint: if you click on the "low bandwidth view" link at the top right of an article, the library suddenly becomes fast enough to be usable

    Leave a comment:


  • norrahe
    replied
    ta!

    mr Nor got asked that in a phone interview and was a bit flummoxed as the natural answer would be use de-bugging tools.

    It may have been throw any type of question at said interviewee.

    Leave a comment:


  • cojak
    replied
    What is there to debug, unless you're using macros?

    If there was a file corruption, I'd probably cut and paste into notepad and then reset style in a new doc.

    Or select all and clear styles completely and reformat.

    Or maybe there's some secret squirel code that we mortals don't know about...

    Leave a comment:


  • norrahe
    started a topic debugging documents

    debugging documents

    this question came up in an interview recently

    How would you debug a word doc without debugging tools? Apart from using word for everyday docs I'm not too familiar with this.
Working...
X