kia ora,

Quote Originally Posted by foxguy View Post
...And we still had to work out all the bugs that I didn't anticipate. I don't spend a lot of time trying to work out bugs until we decide on the final version.
Foxguy, when I spotted these sentences my curiosity got the better of me & I had a look through your code

I couldn't spot any obvious errors but I didn't look to closely at the actual logic. The few general suggestions I have are:
- Try not to use specific words that VBA already uses with a defined meaning. The examples I spotted in your code were "Change" and "Doubleclick". I recommend modifying your chosen words - perhaps by dropping some vowels.
- The range affected by the Workbook_SheetBeforeDoubleClick macro could be limited using some form of "master range" in a test using application.intersect...
- To apply more of a "structured programming" approach, see if you can remove/decrease your use of "Goto". See this thread for some discussion: http://www.eggheadcafe.com/software/...nt-in-vba.aspx
- Here's another approach (http://www.excelguru.ca/node/91) for ensuring the user has macros enabled. This approach overcomes the fact that a msgbox is not shown if macros are disabled.

Quote Originally Posted by foxguy View Post
...Once you move your data over, then if we discover a bug, you'll have to send me your data or I'll have to walk you through how to debug it, and it may be quite complicated.
I like your second option of teaching Nandu (or anyone) - difficult, but rewarding


Rob