I know of no manual that describes the operation of that specific QRZ Logbook search box. One good way to get a feel for that feature is to experiment by entering a record variable in the search box and then selecting the spyglass icon.
Thanks for suggestion. I have just tried that, but so far been unable to se how it actually works. A bit strange that such an important function apparently is without proper description. P-T
Simple... rather primitively basic, either an exact match or nothing, AFAK Not as if c/s would appear as you type, as partially matching, or any other search options... even more obnoxious is that you must MANUALLY CLEAR the search field to get back to full L/B -or is there another way? To sum it up, search field is not a feature you'd want to use a lot. Probably, also as a non-subscriber myself, cannot perform more than 100 c/s searches /24h, no idea. Oliver
Good to hear I am the only one that is a bit frustrated about that search function. For example: - Which fields can be used for searching? Call? Country? Grid? - Does it support wild-cards? How is that implemented? Via '*' or '?' ? P-T
I think all fields. Seems to work that way. K4* will bring all K4 calls. So will K4? What have you tried that is not working?
"K4" brings up all records that contain "K4", thus also "HK4LYT" for example. How do I specify records that start with K4? P-T
What happens if you specify K4* or K4***? We've been trying to get you to experiment and then apply deductive reasoning to the results. You won't break anything by trying different variables. There is one field that is not searchable. It can be found by experimenting.
Lets look at one example. I have only these two logged for Djibouti: If I enter 'Djibouti' in the search field, I get this result: Why is not both found? P-T
