Option Compare Database
Option Explicit

Private Declare PtrSafe Function GetSystemMetrics Lib "user32" (ByVal nIndex As Long) As Long

Private Const SM_CXSCREEN As Long = 0
Private Const SM_CYSCREEN As Long = 1

Private Sub Command0_Click()
    Dim screenWidth As Long
    Dim screenHeight As Long
    
    screenWidth = GetSystemMetrics(SM_CXSCREEN)
    screenHeight = GetSystemMetrics(SM_CYSCREEN)
    
    MsgBox screenWidth & " x " & screenHeight
End Sub

I don't know if that behaves if you have multiple monitors with different screen resolutions, but it works if theyre the same :P

Command0_Click . . .

Hey it's just example :P. I'm a good boy, I use real names on the real stuff lol.

Thank you Adam

ChatGPT just gave me the same code.

Alex, keep Adam honest with naming his buttons

Yeah, I always name my buttons.

Here are my main naming conventions;
    Buttons:               btnMyControl
    Labels:                lblMyControl (If referenced in code)
    Textboxes:          txtMyControl (Unbound)
    Combo Boxes:       cboMyControl
    List Boxes:            lstMyControl
    Check Boxes:        chkMyControl
    Option Buttons:     optMyControl
    Option Groups:      fraMyControl

Sami that's where I got it :p threw it in quick to make sure it worked before I posted.

Yes Adam I also test EVERYTHING I get from ChatGPT Doesn't always get it right first time.

Glossary: Naming Convention

p.s. Leszynski FTW

I always prefix my modules with 'mod'.

For example:
    modGlobal
    modImages
    modFunctions

Once the user's monitor's resolution is known, what needs to be done to set the database window, forms, or reports to match in comparison with the resolution that it was designed in? Howpe this make sense.

Richard did not cover this, but if you watch Access Developer 41 it is just the next step