I do concur with Ivan. Having a single space in a field is most likely not
a good idea. Most systems do TRIM() fields which will turn your space into
a NULL. Furthermore, you place yourself at the risk of, when updating the
field, if you do not account for the space that is already there you will
have a space in your string and risk overflowing the field (think phone
numbers that are an NVARCHAR(10)).
With all due respect, I can think of no reasons you would want to do this
and plenty where you would not.
From: firstname.lastname@example.org [mailto:email@example.com] On Behalf
Of Ivan Peev
Sent: Friday, September 07, 2012 6:47 PM
Subject: Re: Lookup Plus - Default value as a single space
Is this theoretical question or you have real business scenario where the
space should be used as default value?
In general it is not good idea to use space-only as default value anywhere
in any system. The reason for this is many systems will do Trim of the
value, before checking if it is empty. And in the case of space-only, this
field will be determined to be empty.
On Thursday, September 6, 2012 4:32:22 PM UTC-4, Tim Huemmer wrote:
When using the Lookup plus component, there is a trick to get the No Match
and NULL values to be output as a NULL value. This involves hitting the
space bar in these fields on the grid when editing the component's
My question is, if hitting the space bar causes the value to be NULL, how
does one get the default value to be a space?
Thanks in advance!
You received this message because you are subscribed to the Google Groups
To post to this group, send email to firstname.lastname@example.org.
To unsubscribe from this group, send email to
To view this discussion on the web visit
For more options, visit https://groups.google.com/groups/opt_out.