How to move only labels and not textboxes when designing a form

[CJ_London]

But first, in the current versions of access, or with common utilities that people use, is there an reason to NOT use the tag property for storing the translation codes?

very much doubt tab property will disappear. As for storing transaction codes - depends how your translation code actually works, there are many different ways of managing translations, my method doesn't use tags.

Has Microsoft added any optional "user" fields to the objects, so that users can have their own protected area for this kind of storage? If so, how can those be made visible?

No

you can have tags store more than one value if you need to use them for different things - store as a csv or use a pipe or other character. Then a bit of code to split it - will need error handling if one control has one element and another has two. An example might be something like this air code

function gettTagvalues(byVal tagStr as string, tag1 as string, tag2 as string)
on error resume next

    tag1=split(tagStr,",")(0)

    'if no second element assign a zls to tag2
    tag2=split(tagStr,",")(1)
    if err then tag2=""

end function

[Micron]

I doubt that property would ever be removed given the aftermath that would result. It's possible to have csv type tags & retrieve the nth value in the tag string in code. A table is probably better for more complex and wide spread use of values used for things like language options.

Validation in the sense used means at least ensuring required fields are filled in. One can also validate that values are correct; e.g. field contains a date or a value between upper and lower limits for example.

EDIT
Hmm, sometimes I don't see that comments have already been addressed.
I think that has something to do with where I land when following an email link - I don't know. I guess at least my last post supports what was already mentioned.