Happy New Year!
I'm loathe to tell you how to do this because I feel that I will be loading the gun with which you will shoot yourself in the foot further down the road!
You need to concatenate your Tempvar values into the SQL string:
' ...
TempVars!Name = .Fields(INum2).Name...
Sorry, I'm not thinking very clearly!! 😬
Increasing the detail height will not work here because it is a continuous form, and you will only see one record (the others will be below)
Actually, it doesn't look like you have a subform control.
I'm not sure why you have only one row displayed unless you have filtered the RecordSource, ????
Try this in the Form_Resize event:
Private Sub Form_Resize()
Const w As Long = 28440, h As Long = 11835
With Me
' Set the inside width to exactly 28440 twips
If Not .InsideWidth = w Then .InsideWidth = w
' Set the inside height to exactly 11835 twips
If Not .Detail.Height...
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.
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...
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?
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...