The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
I told a couple of clients "no", but wound up having to do what they asked anyway.
One of them I put off for six months before implementing their customer-hostile feature.
The other wanted me to make a change to their production system while I was at their site -- I tried to insist on not doing it until I got back to the office and folllowing the proper procedure, but they insisted.
I'm waiting for the naysayers to ask why on earth you would consider using Access for anything. Just the other day I came across a system still using Access 97 databases for the backend. This is a fairly popular (in my niche) inventory system...It may be popular, but it really sucks as it can only ever provide values at a point in time, not for a point in time like all the others I've dealt with. Of course my manager forces me to spend days trying to match a report that was printed a week prior.
Sorry to have hijacked your question...I think Database is the right forum. Of course you could always just submit in QA.
Good idea, but not my call. It would probably work, but I refuse to put any more time into interfacing with a system using Access 97 databases ...I mean, c'mon, at least move them to 2K!..or better yet, rewrite the application to use SQL Server!