ok - so the gut feel was correct:

quote:

TextBox.AcceptsReturn Property

Gets or sets a value indicating whether pressing ENTER in a multiline TextBox control creates a new line of text in the control or activates the default button for the form.

Property Value

TRUE if the ENTER key creates a new line of text in a multiline version of the control; false if the ENTER key activates the default button for the form. The default is true.

Remarks

If the value of this property is false, the user must press CTRL+ENTER to create a new line in a multiline TextBox control. If there is no default button for the form, then the ENTER key will always create a new line of text in the control, no matter what the value of this property.
The deal is a follows - with VB in this scenario - even if you have AcceptsReturn set to FALSE, one can still enter a carriage return using ^ENTER ... but I haven't managed to have Forms reproduce this behavior yet - im still trying and I will get there - just not in the near term ... will this be a problem, ex. if you have a default button configured - you will never be able to hit enter into a MULTI-LINE textbox. Single-line textboxes this all doesn't matter anyways. And like I say - all this just until I do manage to get it working.