You rarely ever would want to allow both null and ZLS in the same
field, especially if they kind-of mean the same thing. In SQL Server
it's easy to put a Check Constraint to avoid the problem.
The Access link information doesn't mean much to me; I would
exclusively look at what the SQL Server table allows.
How you got ZLS in your field is anyone's guess, not knowing your app.
One possibility is that the user enters <space>, which Access in its
infinite wisdom may truncate to a ZLS.
-Tom.
>I have some text fields in several linked SQL Server 2000 tables that
>intermittantly have either a zero length string placed in the field or
[quoted text clipped - 15 lines]
>bugged. Could anyone please shed some light on this for me? I am
>totally baffled.
Gord - 31 Jan 2007 12:48 GMT
>How you got ZLS in your field is anyone's guess, not knowing your app.
>One possibility is that the user enters <space>, which Access in its
>infinite wisdom may truncate to a ZLS.
I suspected that too, recalling how often users will "empty" a cell in
Excel by hitting the spacebar and then wonder why it doesn't act like
an empty cell. However, Access itself doesn't convert ' ' to ''. I
opened a SQL server linked table in spreadsheet view, typed a space
and saved the record, and the column was <NULL> when I checked it on
the SQL server. It is possible that some bound controls may behave
differently, I suppose....
> You rarely ever would want to allow both null and ZLS in the same
> field, especially if they kind-of mean the same thing. In SQL Server
[quoted text clipped - 28 lines]
> >bugged. Could anyone please shed some light on this for me? I am
> >totally baffled.