Ramona you have it down correct.  The first instance gets pushed down and then, on the second click, the new value is put in at the top of the StatusBox.
The value, if it is to long to fit in the StatusBox, will automatically wrap to the next line.  That maybe what is causing the problem.  You can see it is working in your last picture when you made the width larger.
I don't have an explanation for it not working for you.  I just tried it using your exact code in a new db and it works just fine and as expected.

Try shutting down Access and restarting it.  Also maybe do a Compact and Repair.

Thanks for the tips Scott.  I will try that! :)

Hmmm.  Updated Office, Restarted Computer, and Compact & Repaired Database - Still the same thing.

Not sure what you did, but I copied your code EXACTLY and resized the text box to the exact same spot, and it comes out like this for me...

I think I know what you did. You changed the properties of the text box from plain text to RICH TEXT.

vbNewLine isn't what you need for rich text. You'll need the BR tag.

Rickard you are a Genius, Although technically Scotts suggestions, could have been the problem too!
I am on vacation watching A Lot of your videos, while creating my own Database Template.  So I am adding in Tools, Designing, Setting Properties, etc for certain tables, fields, forms etc.  I wanted all of my Note Fields to be Rich Text, so I added it to my Blank Table, Form, & Continuous Form.  I've since deleted and readded the StatusBox, and wah la, it works!  Thank you.

I would like to set up a StatusBox on all of my forms, never know when you will need one.  Does the StatusBox (Text Box) have to be Unbound?  Or can I just add it to my template as a field?  (With no Rich Text option). lol  This was the first time even tried to use a StatusBox so I am not sure.

I agree Ramona brilliant!  Richard what lead you to deduce that it might be Rich Text? Just experience of something visible?
What would the syntax be for the BR Tag? Why would vbNewLine NOT work?