You know its time to close excel...

[mvidas]

...when you open a new workbook and its named "Book133" or "Sheet164"

[Norie]

And you know it's time to stop adding worksheets using code when you end up with Sheet291.:)

And then you realise you shouldn't be using the code in the first place.

[mvidas]

:) :)
To be fair it has been because of a bunch of testing an addin I made to query a couple things, and using Workbooks.Add(-4167) :) But I'll bet it's been a few weeks since I've restarted excel or my computer

Also, (anyone) feel free to add more followups to the thread title

[XLGibbs]

....when you actually find a reason to use the 64 nested IF's in XL 2007. Of course, there would never be such a reason other than severe delusions.

[Norie]

How about when you actually think 1m+ rows etc are a good idea?

[XLGibbs]

How about when you actually think 1m+ rows etc are a good idea?

That is the exact problem. I have analysts in our department that really think this 17 billion cell per sheet concept will actually help them. I have tested 2 columns 1 million rows with a simple formula to add this row to the one above, and it moves at the speed of...smell.

Of course these are the same people that think Access can store an infinite amount of data (like the 120 million rows of data one of our tables). Even better was when they tried to import our 120 MM row, 210 colum table directly into a pivot table. "Hey, why is this screen white and my computer basically crashed?"

Like I tell them all the time. It is a PICNIC error.


(for the unitiated...Problem In Chair, Not in Computer)

[shades]

Actually, it would have been good to get the columns up above 366 (hence 512), and that would have been sufficient. Getting one year's worth of columnar data is handy, especially when it doesn't work to transpose (I have about 4,000 rows of items for each day's data).

[matthewspatrick]

...when you start assigning named ranges to different parts of your house :)

[Anne Troy]

(for the unitiated...Problem In Chair, Not in Computer)

ROFL!!!

Nice stuff, guys. :)

[TrippyTom]

don't forget about the infamous ID-10-T error. :cuckoo:

[geekgirlau]

... when you describe your children as elements of an array

[Belch]

... when 95% of all the Microsoft Excel automatic error reports are from you.

P.S. In our office we had to upgrade to Excel 2007 just for the 1m+ rows - we needed 100,000 on one sheet - so it's not all useless :)

[malik641]

...when your eyes can't take it anymore

[Brandtrock]

...when the Statistics functions start to make sense.

[Oorang]

When you start making plans to write your own Static Code Analysis Tool, because you think you can do better?

[shades]

When an Excel guru makes more sense than your spouse.

[herzberg]

...when you have recurring dreams of arcane VBA code, nicely highlighted in their default colours.

No joke. Once, I fell sick when doing an important project and all I could see my near-delirious dreams were: a For Each...Next loop and CheckCell.Column; I took medical leave for the next two days. :grinhalo:

[matthewspatrick]

This would be a fun loop:


For Each Bottle In TheCase.Bottles
If Not Bottle.Empty Then Bottle.Contents.Drink
Next


Cheers :beerchug:

[mvidas]

Don't forget to add this in there :)If TheCase.Count = 0 Then
Call A_Cab(Destination:="Pub")
End If

[Oorang]

...when you have recurring dreams of arcane VBA code
Man I hate it when that happens. Sometime's it works to my advantage, like I will fall asleep thinking about something complex, and I will wake up with the finished code in my head. But when it's non-productive or nonsensical and I dream about it all night... ugh:P