sc*******@gmail.com wrote in
news:11**********************@j73g2000cwa.googlegr oups.com:
David, please forgive me. Am I to understand your post to saying
because you have never had to such a task, it is not necessary?
No. I'm saying that in 10 years of regular Access application
development I've never encountered a circumstance where I needed
trailing spaces for any purpose. You provided an example (searching
for a trailing space) that I'd never thought of because none of the
search interfaces I create work in that manner. Even yours ought to
handle "search string *" if you want the space to be included.
Presuming that you're appending a "*" already, it's not really an
issue, as the double-up "**" causes no problem with the LIKE search.
Your situation is not the kind of problem I'd worry about. My users
have a hard enough time even *seeing* spaces onscreen, let alone
using them in searching.
I would also note that I know of no search interface that honors
trailing spaces without some special characters added. Google won't
do it even if you use quotes. Since Google is the most familiar
search interface on the planet, I'd suggest you use it as your
model.
That doesn't preclude allowing a special method for searching for
the trailing space, but trying to code for handling it by default
seems like way too much work for a requirement that virtually no one
actually has.
--
David W. Fenton
http://www.dfenton.com/
usenet at dfenton dot com
http://www.dfenton.com/DFA/