TATWORTH:
eddy556: I still keep finding scenarios which a table would be perfect for
So use a table! I suggest that you check the rendered HTML using the W3C XHTML tests at http://validator.w3.org/
There are incidentally some simple tweaks you can do to make ASP.NET pages 100% XHTML compliant - please see http://xhtmlfix.codeplex.com/
I have been informed by accessibility experts at the RNIB that the use of tables for positioning does not prevent the page from being accessible.
Yeah as much as its wrong to say sometimes it is easier to use a table when you are against the clock. I wish I had enough time to go through the tweak, save, refresh, crossbrowser test cycle to make a simple piece of layout work but sometimes a table -is- simpler.
Personally since I found that fancy forms css article though I have not felt that tables are a situation this falls under.
Take a common scenario for example where you want a section of form (which you would put in a table) and then a break for a header and then another section. If you are using a table you have to take extra pains to make sure the labels column of each section is the same width or your alignment will be off.
Also whether you use a table generator or code the rows and cells by hand there is a lot more to be done so its going to take longer. Well not this time because you have already gone with the table option! :P
Anyway if you know about standards compliant design then only you can decided which level of involvement you want to take. It is forgivable to throw the odd table in there and the real point that most developers are getting at when they say no-tables is dont make those horribly deeply nested table based designs that were around when frontpage was king.