As a network/systems administrator I'm definitely in wraith808's corner on this. I've seen many an Access based nightmare, and am thus a big fan of SQL.
But I will give you this one:
Access's brilliance is that it leverages any moderately intelligent person into data-driven application development.
Access's downfall is that it leverages any moderately intelligent person into data-driven application development, even those who know nothing about application development.-JohnFredC
Any time I use it the tied hands effect the WYSIWYG affords makes me want to tear my eyes out almost immediately. Only saving grace is that you can at least switch to a (semi) proper SQL Query prompt and get something done. But even that's a bit clumsy.
I've scratch written many of our internal systems, and while it did take more time to do it around a SQL db ... Once it was done, it was done. Scaling issues aren't a problem, the server just handles what is thrown at it. Which is good because I had a lot more time back when most of this stuff was done. So now as the data volume increases and usage picks up, I don't have to worry about it turning into a fire-drill because the db decided to max out and explode. Getting to the 50,000 record stability/performance turning point really isn't that hard to do these days.
I guess I've just never actually seen a
good Access based application. *Shrug*