First Off:- Pat Hartman, if you happen to read this message, I would like to Thank you for solving the normalisation query I had. I can't find the original thread to thank you on there.
Anyway, down to this problem. I have a field that contains ## as part of the content within the field. An example would be 'Leased##'. To change the contents of this field are not an option so I have to find a solution to this query issue.
I have a query that looks at various parts of the table in order to find its data, part of this includes a line
Like "*" & "##"
This obviously searches with the relevant column for any content that ends ## despite what the prefixed text is. It appears that as soon as I put ## in, despite the fact I have enclosed it within double quotes, it does not return any results. If I were to search on Leased## it returns the results. There are too many option that end in ## to specify them all in the query definition individually. I did a trial and look for the value of "/" in another field, and it did not return any either. In both cases I know the data exists in the relevant fields.
The only thing I can put it down to is the fact it is searching for a symbol regardless of the fact that is enclosed within quotes.
Is this the case, is there a way around it?
Kindest Regards
Anyway, down to this problem. I have a field that contains ## as part of the content within the field. An example would be 'Leased##'. To change the contents of this field are not an option so I have to find a solution to this query issue.
I have a query that looks at various parts of the table in order to find its data, part of this includes a line
Like "*" & "##"
This obviously searches with the relevant column for any content that ends ## despite what the prefixed text is. It appears that as soon as I put ## in, despite the fact I have enclosed it within double quotes, it does not return any results. If I were to search on Leased## it returns the results. There are too many option that end in ## to specify them all in the query definition individually. I did a trial and look for the value of "/" in another field, and it did not return any either. In both cases I know the data exists in the relevant fields.
The only thing I can put it down to is the fact it is searching for a symbol regardless of the fact that is enclosed within quotes.
Is this the case, is there a way around it?
Kindest Regards
Last edited:
