I was up til two last night, tweaking a small Microsoft Access application I was prototyping to show to some end-users this morning for their feedback.
<"techie twaddle">I'd built an initial screen with a subform linked to a big union query - 11 unions in fact - which would give the user a snapshot of the project status with all the key statistics on it. Worked perfectly on my Access 2000 setup. But when you open the beast in Access 2002 as used at the client site, something dreadful happens to the query and you show the users a nice blank subform. The query itself seems to be totally trashed and you can't open it in design mode any more. Bad news, because you've lost all your SQL. The fix seems to be to write another (non-union) query which uses the union query as a view, and link the form to the non-union query. You have to rewrite all the SQL first, of course. <"/techie twaddle">
Fired it up, it was bust, a ten o'clock meeting, and I would be demonstrating (to three people who'd driven 80 miles to see it) a broken application that I wouldn't have time to find a fix for before they arrived.
Initial feedback was that it would be nice if the screen wasn't blank.
There were other screens which did work, and while the visitors were checking out the screenprints and writing their comments and suggestions, I was frantically finding a fix - which happily materialised in time for me to show them a kosher front-end.
Not the most stress-free walkthrough I've ever done. I'm somewhat tired. Need a drink.
UPDATE - A bad day for me at the office is like yesterday's. A bad day for Susan, a nurse, is working for an hour in the back of an ambulance on someone who's arrested - and not being able to bring them back. Or visiting and talking with a thirtysomething mother of three young children, whose cancer has just been diagnosed as terminal. I need to remind myself of that occasionally. Working in IT isn't exactly Helmand province !
4 hours ago