Do I even have to spell this out for anyone?
I worked with a team that did so many access-to-web projects that we had a canned “Why Access Sucks for More than your Desktop” document ready to send as part of our first response. I forget the specifics, it's been so long (thank God!), but we had a clever acronym like the “5 Ds: Data Integrity, Distributed Accessibility . . .” I wish I had a copy of that just in case . . . it was well written and had tons of cited sources.
I'm not even going to discuss the details of my current frustration; suffice it to say that it's after midnight and I'm not doing anything close to .Net -- my general rule is that only cool .Net stuff occupies my attention after 12 midnight, but an emergency came up for a customer and so here I am. I'm just taking a break before I wrestle with Access anew. This is just one of those things that working for a small company entails . . . there's the Access customer from time to time (although we've grown them into SQL Server and a split DB architecture -- steps in a positive direction!). The Ldb files, data compaction and corruption, access specific security, replication, the list goes on and on. I can't leave out On error resume next.
Like Bob Reselman's Coding Slave asks: do you spend more time with code you hate than with the people you love? Tonight I sure do. It's funny to consider I'll be enjoying TechEd stuff in a few days, but I've got these MS Access hurdles to overcome before I can get there. TechEd is my light at the end of the tunnel. I don't recall seeing any Access database classes on the TechEd agenda . . .
Happy .Netting (and not Accessing)!