text message, best practices

[markjkubicki]

I have an ACCESS project, which has a LOT of Forms/subForms. Often there will be user prompts, and this would be typical.

        gsMsgText = "You have assigned 0-10v control to a fixture that may potentially be used for EM purposes." _
            & vbCrLf & "Certain jurisdictions require the fixture to comply with UL924" _
            & vbCrLf _
            & vbCrLf & "Do you want to add a UL924 requirement?"
        gsMsgTitle = "UL924"
        gsMsgResponse = MsgBox(gsMsgText, vbYesNo + vbDefaultButton2 + vbQuestion, gsMsgTitle)

My Q. is:
Is this an OK way of handling the info, or should the actual "texts" be stored in a table and the code be revised to lookup the text (rather than it being hard-coded)?
Which is better practice?

[June7]

If you want to be able to change the message in future without having to modify code, use table. Otherwise, hard-coded message is fine.

[Welshgasman]

I think with info like that, you would be better off with a table?

[markjkubicki]

thnx!

this is trivial but... is there a standard convention for this type of table?
i'm thinking:

- one table for all text on all forms

- with multiple fields: FormName , Msg_no, MsgTTl_text, MsgTxt_text (allowing for multiple entries for any one form)

[Welshgasman]

I would have thought MsgNo and MsgText would be enough?

[markjkubicki]

works for me... thnx !