I have a form that is used to enter search criteria relating to car warranty claims.
One of the fields is an unbound text box that allows the user to enter a specific keyword.
The problem I have is that Access removes any trailing spaces from any entered word and there are times when the space means the difference between a few correct 'hits' and lots of incorrect ones.
For example, if the user enters "FIRE", they will get results that include "FIREPROOF", "FIRELINE" (a brand), and so on.
They want to be able to enter " FIRE ", to just get cases where the word appears in the middle of a sentence, but this gets changed to " FIRE".
I've tried using the Before and After Update events to capture the entered value, but both return the word after the trailing space has been removed.
I've found a few people reporting the same problem online, so I'd be surprised if nobody has come up with a workaround for this 'feature'.
The workaround for now is to enter "FIRE *", as the wildcard allows the space to be retained, but we have a new manager and he's insisting I find a way to save the users from the 'hassle' of having to do this i.e. he keeps forgetting to do it.
Is there some other event I could use that would capture this value before Access removed the space?
One of the fields is an unbound text box that allows the user to enter a specific keyword.
The problem I have is that Access removes any trailing spaces from any entered word and there are times when the space means the difference between a few correct 'hits' and lots of incorrect ones.
For example, if the user enters "FIRE", they will get results that include "FIREPROOF", "FIRELINE" (a brand), and so on.
They want to be able to enter " FIRE ", to just get cases where the word appears in the middle of a sentence, but this gets changed to " FIRE".
I've tried using the Before and After Update events to capture the entered value, but both return the word after the trailing space has been removed.
I've found a few people reporting the same problem online, so I'd be surprised if nobody has come up with a workaround for this 'feature'.
The workaround for now is to enter "FIRE *", as the wildcard allows the space to be retained, but we have a new manager and he's insisting I find a way to save the users from the 'hassle' of having to do this i.e. he keeps forgetting to do it.
Is there some other event I could use that would capture this value before Access removed the space?