If
@arnelgp suggested "like", it is because YOU SAID -
If the Transaction_Type type contains any of these words
"Bought" Or "Purchased" Or "Selling"
Which implies, that the type might be several words long such as
"Selling single items"
"Selling old inventory"
and you do not want to have to type the entire string.
So IF the Type is just the single word, then he misinterpreted your sentence - which could be read two ways. Remember, not all posters here speak English as their native language and who knows what your statement ended up as in whatever language arne speaks if he needed to use Google Translate.
So, if you do need "LIKE" because your type code is actually a phrase rather than one word, then LIKE is the solution you need. HOWEVER, that doesn't make it right or good. Using LIKE presents the very real problem I suggested. It is not a criticism of the solution
@arnelgp suggested. You need to rethink your types and how they are used so that you don't need to use LIKE to pick out what you need.
LIKE should be reserved for searches of things like names or addresses where you really do need a fuzzy type of search. You NEVER design an application that requires fuzzy searching on something like type or category.
PS, back in post #4 you indicated that
@arnelgp 's solution didn't work. In #14 you posted a solution with LIKE which isn't what arnel used in his sample db although he never told us what he actually did. I never looked at it earlier because I can't be bothered with "try this" solutions.