I'm a little confused, but probably because you are too and questions often don't make much sense when the one asking is confused.
"Is it possible?" Almost anything is possible. What it refers to in this sense is beyond me.
Let me see if I can make some statements that are true and see if any help you at all.
(Like "" & "Raj Poot" & "") Or (Like "" & "Malak" & "")
can be used as part of the criteria. It would be a very curious way to express the desire to match either "Raj Poot" or "Malak", but it would work.
Bear in mind though that while this may fit into the Criteria
box in a Query (QueryDef object), it doesn't work directly in SQL. SQL format requires a match to be specified such that both sides of the comparison are stated. EG. [MyField] = 'X'
. Just specifying "X" will not work.
"" & "X" & ""
will result in exactly the same string as "X" so why would anyone in their right mind add the two useless empty strings. The only reason I can think of is that they copied something else and didn't understand what they were doing. This happens. It's not wrong. It's just not a great way to proceed. Where possible, it's advisable to understand what something does before trying to use it.
It also makes no sense to use Like "X"
when the "X" string contains no wildcard characters. It's functionally equivalent to =
. Thus, your filter code above could equally be written as ([MyField]='Raj Poot') Or ([MyField]='Malak')
(Note the Quotes (') used are the appropriate ones for SQL). There's even another way which is better for comparing against a list of values - [MyField] In('Raj Poot','Malak')
.
If that doesn't answer your question then I'm afraid you'll have to write it in such a way that it makes actual sense.