That does not do a repaint of the "database screen". That is referring to this window
As stated it is to refresh objects in that window that have been added, renamed, or removed via code.
I believe you mean it is not "repainting" the form. Refreshing is updating the data on the screen. You could try forcing a form.repaint, but you might be chasing the real issue. Try creating a new database and importing everything into that. If that fails you can try a database decompile...
In your approach it requires you to name your controls with a matching value in the option value. "B21 must have a value of 21". This requires a little bit of work in ensuring you named and valued them correctly.
My original suggestion is short, but requires diligence because the controls...
Pretty sure this is a "WHERE" not an "AND"
Case 1
strWhere2 = " AND qryIncExp.[Hide] = FALSE"
If not it makes a join that does not make any sense.
SELECT qryincexp.accountid,
qryincexp.accountname,
qryincexp.faccounttypeid,
tblcombo.data AS Type...
As I pointed out if done in the after update
Me.Controls(Me.Selalpha)
is almost guaranteed to return an object in the Controls collection just not very likely to be the one you want and likely not an option.
where
Me.SelAlpha.Controls(Me.Selalpha)
is guaranteed to return one of the options in...
Here is a demo with the correct syntax showing why the OPs original syntax will be a random control on the form and not the caption of the clicked control. It will fail if that random control does not have a caption property.
It is
Me.SelAlpha.Controls(me.selalpha.value)
not...
I do not think that syntax looks correct.
This assumes that you dropped all your controls in correct order. An options group has a controls collection like you show so in your case the first dropped control is "A" and has an index of 1.
So to get the caption of the clicked control
If...
This is just one of many ways to structure the interface. You can use a tab control on the form to create more real estate. You could put only Summary data on the dashboard and force a pop up for details. You can use continuous forms instead of datasheets for increased formatting.
Added call details so all functionality should exist
1. Create customers
2. Create customer properties
3 log payment status (bad check, missed payment...)
2. create a call and assign a property / customer
3. assign an appointment to a call
4. add service information to an appointment
So you need another subform to show the services for that appointment. If you want all of that on the dashboard you can shrink things down to make room an add the "Services" subform. The tricks is to show and hide that subform only for calls with assigned appointments. If not that form is...
Surely not. It only prints the first character of any string
characterRequired; Variant. Character code specifying the character or string expression whose first character is used to build the return string. If character contains Null, Null is returned.
?string(10,"ABC")
AAAAAAAAAA...
So another example of a future feature that will be needed. Eventually your call list will get extremely large with old calls. That list will no longer be useable.
I can envision an option group at the top of the list to filter what you want to see.
Calls needing appointments
Calls with...