You're just trying to get rid of spaces?

Replace([Field]," ","")

If you want to only get rid of EXTRA spaces, that's a little more advanced.

Make a global module
Public Function RemoveSpaces(FixString As Variant) As Variant
  If IsNull(FixString) Then 'handle Null values
    RemoveSpaces = Null
    Exit Function
  End If

  Dim S As String
  S = Replace(FixString, vbCr, " ")
  S = Replace(S, vbLf, " ")
  S = Replace(S, vbTab, " ")
  S = Replace(S, vbVerticalTab, " ")
  S = Replace(S, vbBack, " ")
  S = Replace(S, vbNullChar, " ")
  While InStr(S, "  ") > 0
    S = Replace(S, "  ", " ")
  Wend
  S = Trim(S)
  RemoveSpaces = S
End Function

On your form call the procedure, do something like this
Dim X
X = RemoveSpaces(TextboxName)
TextboxName = X

Thanks Adam. I wrote the while part last night, but have you been finding those other characters in typical data entry? Shouldn't Access be filtering all those control codes out like they do extra spaces at the end of text in a text box? Do you find you have to do this after every input? Or do you have a way to do all the text boxes just before the record is saved, and from what event do you call it?

Was that somewhere in the "code vault"? If so, how could I have found it?

Well, it's not always at the end of a text box. The code searches through everything because you had extra spaces everywhere, not just at the end of the field, it could be in the middle of the text or the beginning, in which case access would leave it alone.

I would just call the procedure on the after update event of the field it's checking, or go through everything on the on close event of the form. I was under the impression this was just for a certain field that imports weird or something. If this is a problem on all of your fields, is it user error? Or you just want to apply it to everything just to keep it looking one way? I have a global mod I made a while ago around here that can set global settings in the on current/on close event, if you want to do this on just everything just do it, that may be easier.

Not in the code vault, in the brain vault (and a little google assistance LOL)

I was wondering, in your experience, if users are entering these control codes in through text boxes on forms. Yea, I expect weird stuff in imports.
If users can enter these control codes somehow, then it would be best to check the record for all entered data just before save and get rid of them. I'm not sure what you meant by "set global settings in the on current/on close event".

I haven't done it yet, but I'm guessing there's a way to loop through all the controls in a form and If...Then those that are text box or contain entered user data, to do RemoveSpaces() on each.  I'm sure Richard must have touched on this somewhere by now, but with only one-word searches being effective...

Code Vault: Loop Thru Controls on a Form

It took me a minute:
You: Well, it's not always at the end of a text box...
Me: I was talking about entering into a text box on a form, not the code you graciously wrote  (or found).

Note: In some BASIC I've worked in, control characters (ANSII dec 0 - 31) are allowed in an input statement while others don't. Has Richard addressed what and what isn't stored in text boxes?

Right, imports could have all kinds of issues come up, but even on a text box under normal daily use, the user could press space 5 times or copy and paste something with issues in it anywhere in the text box, beginning middle or ending. Just keeping it in there because there's no harm in it.