Event for after form displays, before entry in tbox control?

[twgonder]

Here's another little stumper I've gotten myself into.
I searched, but no go.

I'm working on a logon form.
There isn't a data source.
The first field to enter is the "User ID"

I need to test a lot of conditions to see if the system is available before the User ID is entered,
and if not available, I want to show that in the caption of the form (where I show most errors).

But... I can't find an even that allows me to run a procedure after the form displays, but before the first textbox has any entry.
All the stops I've tried (there have been many) happen without the form being displayed.


Even enter and got focus for the textbox.

Where?

[June7]

I tested GotFocus for textbox. Form is visible when event runs.

[twgonder]

@June7 Very strange, it doesn't for me on Access 2021. I'll try again, maybe because I was in the debugger watching the code?

P.S. I did try without using the debugger, and I was able to change the caption, it just didn't update, or display the form, while stepping through the code.
Other similar changes while the form has displayed normally work and show an immediate change in the open object pane.
It probably has something to do with User ID being the first control.

[Welshgasman]

Why not just do it before you show the form?
Then if conditions are not met, you show a form that explains what is wrong, else show the logon form.

[moke123]

How are you opening your logon form? Autoexec or startup form from the backstage?
I would run whatever it is your doing from a sub called from an autoexec and have the sub open your form.

[twgonder]

@ Welshgasman This brings up a good question I've been waiting to ask, and I hate asking it here, as I'll be accused of topic creep, but since you asked...

When you find entry errors in a form during entry or at before update (and you don't want to use the Access cryptic messages), is it common practice to pop-up another form, use a message box or a customized programmed message box to display, or have a textbox or label hidden that appears with the errors in the current form? Since I'm implementing foreign language conversion for label names and error messages, I'm avoiding "hard coding" the text and have a function to return the translation value.

[Micron]

is it common practice to pop-up another form, yes - as a custom message box

use a message box or a customized programmed message box to display, yes

or have a textbox or label hidden that appears with the errors in the current form? I say No.

[CJ_London]

I would say whatever works for the situation - if there is only potential for one error, use a message box, if multiple errors you could use a custom popup to display all the messages. As a user I would find it very irritating to get a message box 'error A', I fix that then get another message 'error B', etc

Another method is to highlight in some way (conditional formatting perhaps) each control where there is an error then use a message box to tell the user that the highlighted controls need fixing.

Depends on what the potential errors could be, but if a required value, I often use the format property to display a message whilst the control is null e.g. to display 'Required' for a text value the format property would be @;[Red]"Required" - then the before update message won't appear, unless the user ignores the prompt

[Micron]

if multiple errors you could use a custom popup

Agree with the multi-prompt thing, but you don't need a form for this (not saying you shouldn't). Have done multi-line message box detailing the missing values a few times. In such a form, I would always leave the labels attached/associated with the controls to be validated. That way, you can easily get the label caption since the label caption is usually less cryptic than txtCustPrimePhone. Changing bg colour at the same time is an option as well.

[moke123]

I do the label thing like micron as its usually descriptive and can be hidden if necessary.

Public Function ValidateForm(frm As Form, TagCharacter As String) As Boolean
'validated controls must have a label. Ok to use a hidden label if needed.


    Dim ctl As Control
    Dim flg As Boolean
    Dim strout As String


    flg = True


    For Each ctl In frm.Controls


        If ctl.Tag = TagCharacter Then
            If Nz(ctl.value, "") = "" Then
                flg = False
                ctl.BorderColor = vbRed
                strout = strout & Space(10) & "* " & ctl.Controls.Item(0).Caption & vbNewLine
            Else
                ctl.BorderColor = vbBlack
            End If


        End If
    Next


    If flg = False Then
        MsgBox "The following field(s) must be completed:" & vbNewLine & strout
    End If


    ValidateForm = flg


End Function

[twgonder]

I do the label thing like micron as its usually descriptive and can be hidden if necessary.

...

This is a great idea for when loading the form, put all required fields in a red border text box. I don't use the tag property. Is there a simple way to see if data is required for a control? (I'm still foggy on how Access relates field types, length, required and format from a table into the text/combo boxes of forms).

[moke123]

I don't use the tag property. Is there a simple way to see if data is required for a control?

yes, use the tag property and loop through the controls.

[twgonder]

yes, use the tag property and loop through the controls.

I'm not sure what you mean by using the tag property.

[Welshgasman]

I'm not sure what you mean by using the tag property.

Each control has a property called Tag ?

Look on the Other tab of any control, bottom field.

[moke123]

I'm not sure what you mean by using the tag property.

I believe we've discussed the tag property before.