Rod

Well, I think the distinction is that computed fields and editable fields do things kinda differently. In a computed field, the nulls will remain (unless @Trim is used). In an editable field, the nulls are automatically trimmed (apparently it's assumed that consecutive separators equate to user input error or something)...

So, what to do...at a high level, here's one approach:

If all the values are on a single document, create a table or grid mechanism. Computed fields for First, Middle, and Last names. An "Add" button to bring up a dialog box or something to add a "row". A "Delete" button to bring up a dialog in which the row to delete can be selected. An edit button (first dialog is to select the row, second dialog to actually edit that row).

That removes the auto-trim behavior of editable fields from your form. The null values will remain in the computed fields.

Hope that helps.

Rod

Side note: "Trim" in LotusScript is the one that removes only whitespace. They added "FullTrim" to duplicate the behavior of @Trim.

"Microsoft;Sun" ".NET;Java"

Now if I make .NET a null... hm. Everything still looks the same.

;-)

Too vague?

This has only effected me in when I wanted to show a table where null entries are present. When this was the case I had two options to preserve the null options in a multivalue field.

1. The multivalue field that needs to store the null values is not on form. For example if the field is constructed back end and saved to the note then the null value is preserved. The key to this working is to remember that the in memory and backend documents store different values and you can copy the value of the in memory field to another field on the backend document not saving the original field.

2. Translating the null values to another character so that Notes would register it a valid entry in the list and preserve the order.

I know both these methods are hacks, but we are talking about Lotus Notes.

Regards,

Anthony

Whether or not it ever was the way you and I believe, I'm adamant that's the way it *should* be in a world of common sense.

But don't wory: Just one week ago I found out that the underscore IS a legal character to start a field name with, when I always thought it wasn't. Things like this keep happening, but not only in Notes, I assume.

Is there no way to include blank entries then?

Blank/null entries have always been removed within domino multivalue arrays. The classic test does not require programming either. Just do to the server configuration document. in the field where tou can block domain/ip addresses for inbound SMTP. enter something with a double semicolono or just do an extra carriage return. you will notice it removes null entries.

hope this helps

Just a quick test with this shows that if you put a space in as an entry it doesn't trim it so maybe try putting in a translation formula to change a blank into a space and then trim it when you concatenate them so there's not an extra space in the middle. Not the best way but i can't see another way just now.