Recent content by cheekybuddha

The real question is why you need to store this info in a table (counted) when the SELECT query you use to populate it will always give you the answer in the first place, and is less likely to be out of date.

The trick is to look at the answer in SO, not just the question

so was i

I see this advice trotted out regularly, and I would suggest it's unnecessary. If anything, it risks ascribing meaning to the PK of a table which it shouldn't have - the only job of the PK is to be a unique identifier for each row of a table. Note how often folks get their knockers in a twist...

None of the code in the answer in that thread is Excel specific

Hmmm... I seem to remember there was also an Isaac who behaved much the same on UA and was also banned. :unsure:

I'm not sure Ron's suggestion is the answer. If the customer is null you should fall through to the Else anyway. I'm on my phone and can't see your image very clearly. Are you sure the subform has AllowAdditions property set to False? Could they be adding a new record via the navigation buttons?

My turn for a dumb question: how is a user meant to enter data in a control if, every time they click on it, focus moves to the next control?

Haha! So, instead of spending 15 minutes setting the tab order you've wasted 24 hours trying to code a solution that breaks anyone's natural muscle memory for navigating between fields! Just want to make sure that you are aware that you can arrange tab order using drag and drop, not just by...

Erm, isn't that an internet connection? 😉

` You may wish to consider whether you actually want to use an Arduino board going forward. Arduino was just bought by Qualcomm and the enshitification has begun. you might also be interested in the quirks of their new board

TinyInt has a max value of 255 - so useless in a table of 108000 records! Beware also, sometimes you can not join between fields of different datatypes (perhaps this is an Access limitation - I'm not 100% sure) I think any savings will be negligible

Ah, I missed the tests - thank you @Gasman and @arnel for showing the benefit of SELECT 1 (y)

This is counter-intuitive (I'm not saying it is not true!) The * here does not require the db engine to enumerate any fields - this seems like an AI mis-understanding. It is not the same as SELECT * ... Using * generally allows the COUNT() query to use the table metadata statistics for record...

Out of curiosity, which datatypes are you converting from/to ?