Results 1 to 4 of 4
  1. #1
    3 Star Lounger
    Join Date
    Apr 2002
    Location
    Texas, USA
    Posts
    208
    Thanks
    0
    Thanked 1 Time in 1 Post
    Excel Version 2003

    Our main application uses Excel via automation to produce financial reports. Up until recently we could always debug this process by dropping a STOP
    command within the code module for the Excel Addin. Somehow with a recent update the vendor has changed the way their product calls Excel via
    automation so that even a STOP command followed by by a line setting the Visible property to TRUE will not stop Excel.

    Any way to grab a hold of or hook into Excel when this happens? We've had some dooseys (problems) before that in the past we've found it much easier and faster to fix ourselves but we have to be able to see what line of code in the add-in that Excel is hanging up on as well as various varable values and we can't now.

    Thanks

  2. #2
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts
    You might try this:
    - Start another Office application such as Word, PowerPoint or Outlook.
    - Press Alt+F11 to activate the Visual Basic Editor.
    - Press Ctrl+G to activate the Immediate window.
    - Type the following, then press Enter:

    GetObject(, "Excel.Application").Visible = True

    This might make the hidden instance of Excel visible. It may not work, though, if the Automation code "hangs".

  3. #3
    3 Star Lounger
    Join Date
    Apr 2002
    Location
    Texas, USA
    Posts
    208
    Thanks
    0
    Thanked 1 Time in 1 Post
    [quote name='HansV' post='775191' date='14-May-2009 15:40']You might try this:
    - Start another Office application such as Word, PowerPoint or Outlook.
    - Press Alt+F11 to activate the Visual Basic Editor.
    - Press Ctrl+G to activate the Immediate window.
    - Type the following, then press Enter:

    GetObject(, "Excel.Application").Visible = True

    This might make the hidden instance of Excel visible. It may not work, though, if the Automation code "hangs".[/quote]


    Thanks Hans. Have you (or anyone else reading this post) ever heard of someone being able to do something like this with Excel 2003?

  4. #4
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts
    [quote name='edcarden' post='775309' date='15-May-2009 01:12']Thanks Hans. Have you (or anyone else reading this post) ever heard of someone being able to do something like this with Excel 2003?[/quote]
    If you mean whether I have been able to make a hidden instance of Excel visible using GetObject(, "Excel.Application").Visible = True, the answer is yes, frequently.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •