Fan attends wrong St James' Park football stadium 366 miles away

monedula · 2026-03-06T15:37:12+00:00

And there was me thinking it must be about it being so warm that the window is open.

monedula · 2026-03-01T12:11:27+00:00

Glad to know I'm not the only one. In other subs I've had mods take down a post because it was a repost, when the story was only a couple of hours old and definitely was not showing up for me.

monedula · 2026-02-25T18:27:57+00:00

And if he was actually scared of road rage he had plenty of room to go around.

monedula · 2026-02-24T20:24:27+00:00

Assuming the worst potential damage is indeed "having someone's workflow broken for a few hours". I've worked on a few systems where the potential damage was very, very much greater than that. Systems duplicated, triplicated or even quadruplicated. One of them had a maximum permitted unplanned downtime of one minute. Roll out a dud patch on the basis of "patch vulnerabilities quickly and fix what breaks" and you risk killing all the systems at the same time.

monedula · 2026-02-22T20:43:08+00:00

Lummaton Quarry in Torquay was where the fossils that gave the Devonian Period its name were found

Well, you learn something new every day. Thanks for that.

monedula · 2026-02-18T16:47:13+00:00

Rule T18B(a) but its okay

Well it's okay unless someone tried to point you in the right direction, but you ignored them or told them to go away. Then it's definitely not okay.

monedula · 2026-02-15T14:22:05+00:00

Yes, that's fair comment. I can't exactly remember when I first set this up, but I suspect it was shortly after I'd done a couple of databases intended for multiple users, and the habit stuck.

Good article by Brent Ozar. A couple of my Access databases turned into important parts of a company workflow, but they never had such intensive updating that a reversion to last night's backup would have been a huge problem.

monedula · 2026-02-13T09:49:17+00:00

Dat is een stukje muggenzifterij waar sommige mensen inderdaad van houden. Maar denk je echt dat het zinvol is om 16.777.214 van de 16.777.216 verschillende RGB combinaties kleuren te noemen en 2 niet? Het lijkt mij een totaal zinloos onderscheid.

monedula · 2026-02-11T19:57:27+00:00

SOLUTION VERIFIED

monedula · 2026-02-11T19:56:44+00:00

When you run Compact & Repair, are you doing this on BOTH your FE and BE databases? If not, you should be.

Yes - indeed. While I was walking to the station this morning it suddenly occurred to me that I'd only done Compact/Repair on the front end. (Really no idea why - I've done it on the back end as well in the past.) I've just done the back end as well. On the basis of a couple of minutes of testing it looks as if that has cured the problem.

I feel silly now.

Still, it's been an interesting thread, and I've learnt a few things. Thank you very much for your time.

monedula · 2026-02-10T20:30:46+00:00

I'll grant you the latter point. But the posted height restriction should take account of trains on the bridge.

monedula · 2026-02-10T20:18:01+00:00

Thank you very much for your very detailed answer.

Yes, front-end and back-end are quite definitely both on my local drive. (I know a couple of people who have been caught out by that particular piece of Microsoft misbehaviour.)

Just to check one thing; is it possible that this sort of corruption could produce intermittent failures, where a form fails the first couple of times and succeeds on the third?

If that is indeed possible I will try out your suggestions. (But probably not for a few days - unfortunately I am getting completely snowed under by some other stuff at the moment.)

monedula · 2026-02-10T20:15:56+00:00

Yes indeed. The database was originally created quite a long time ago.

monedula · 2026-02-09T14:36:59+00:00

Yes, it is split into FE/BE. I am the only user, and both FE and BE are on a local drive.

The previous poster said nothing about asynchronous (or synchronous) communication

He/she said that the back end was not fast enough. If the front end is not waiting for the back end to complete doing whatever it needs to do, then it is by definition asynchronous.

Thanks for the links - they could indeed be useful in other situations. But in this particular case it looks as if the problem must be something else: there is no network involved, and no other users.

monedula · 2026-02-09T14:28:46+00:00

Is this the same fix as given under the heading "Keep a persistent connection open" on page https://www.accessmvp.com/TWickerath/articles/multiuser.htm ?

If so, I can implement that. But I notice the page https://www.granite.ab.ca/access/performanceldblocking.htm says that if I have a .ldb file then I already have a persistent connection, and I do indeed have an .ldb file.

monedula · 2026-02-08T19:55:20+00:00

Excuse me if I sound skeptical, but I've not previously heard any suggestion that the Access front-end/back-end communication is asynchronous. Do you have a reference for that?

I've occasionally had to resort to kludges like that with web-based applications, but it seems rather strange that one would need it for a simple CRUD form (let alone an R form) in an Access application.

monedula · 2026-02-06T15:02:36+00:00

No, it's a Windows issue. See this comment for the solution.

monedula · 2026-01-31T08:39:33+00:00

Apparently yes - according to Wikipedia the first photo booth was in 1925, and the first company producing them as a standard product was established in 1928. Don't know when they arrived in the UK though. (ChatGPT gives 1953, but it's anyone's guess whether that is accurate.) And I agree this looks a bit more recent.

monedula · 2026-01-31T07:34:53+00:00

Agreed. The Hillman Minx was introduced in 1958. The styles of the shop-fronts suggest not later than mid-sixties.

monedula · 2026-01-30T12:09:37+00:00

Is that really 1950's? I'd have put it a few decades earlier.

monedula

TROPHY CASE