Our ERP system runs on SQL Server and it's both case sensitive and uses spaces in table and column names. Yes, you have to pay careful attention.

>I learned to love underscores when I was on a VAX... and stayed so in all cases when the thing named could lose case. Naming things in camelcase is all fine if they're guaranteed to keep the case; if the system loses it, you get a word which looks like one of those long german or hungarian composite words (elektromotorotekercselés was 12m long and 1m high, on a fence - means "rewinding electric motors").
>
>I could go with either, for all those cases when having spaces inside is impossible (hey, Cobol allowed dashes inside, that wasn't too bad), but since it's usually a mix since people on the team tend to come with different habits, the trouble is not so much readability, it's trying to remember which one was used in each case. Was it VeryLongWord or very_long_word? Ummmm... Thankfully, this led to invention of intellisense :).