3 ms·

Let me rant on something here. I work in finance, Excel is my everyday. We do a lot of manual monkey work (copy pasting stuff around a lot), when we "automate",

by kfk 13y ago

Let me rant on something here. I work in finance, Excel is my everyday. We do a lot of manual monkey work (copy pasting stuff around a lot), when we "automate", we use the adamant (can't find a better word) VBA. Now, you see how not helpful is this error message? Ok, try that when you are writing a macro in VBA. You literally start regretting the day you were born. Nothing beats Python stack traces...

web007 13y ago
From that article, something I haven't seen before: To verify the error message that you receive in Excel 2007, press Ctrl+Shift+I. The following number is displayed in the lower-right corner of this error message dialog box: 100202 It's no stack trace, but should be helpful in searching for proper error codes vs generic text.
- kfk 13y ago
  Except I am on Excel 2003. The company is slowly moving to 201x although (can't remember the version, the email subject was "digital toolbox" and thus I directly deleted it).
  - roel_v 13y ago
    So do you work with a 2003 version of Python?
    - rsynnott 13y ago
      Python 2.3 still had stack traces.
  - kfk 13y ago
    Nice try. Not my choice to work with Excel 2003 although. Also, I hate the ribbon interface.