QSL Manager fails to respond to Callsign Entry

[n2so]

Hello everyone...
I am a new user of Log4OM and this is my first Post on this forum. I have sucessfully imported my log from my previous logging program containing 40,000+ QSOs and I am currently running version Log4OM 2.33.0.0. I have been able to upload recent QSOs to LoTW, eQSL and Club log and have updated my log with confirmations downloaded from LoTW and eQSL. I am sucessfully using the WSJTX and N1MM interfaces to log new QSOs and the Keyer program is operational.
I recently received a batch of QSL cards from the Bureau as well as several via direct and I am in the process of responding to those QSLs. After viewing several YouTube videos as well as the written manuals I sucessfully printed my first QSL label without too much difficulty. My problem is that the QSL Manager seems to have now stopped working. When I enter a QSO call sign in the searchbox nothing happens and no QSOs are listed. I have confirmed that the QSO does indeed appear in the Main Log window. I have tried several QSL card callsigns without sucess. I have searched the forum for similar problems and found none.

[KI5IO]

Charles,

What search confirmation have you selected for your 'paper QSL search'?

Have you chosen any options for the Sent/Received values?

Those choices are 'sticky' for each of the 'Search Confirmation' choices which makes it easier and saves a couple key clicks when you use QSL Manager.

I only upload/download to/from LOTW and then manually handle the occasional QSL cards that show up.

I also simply use "Yes" and "No" for dealing with my QSLs (LOTW, paper, etc..). I'm old-fashioned and don't want to fiddle with the "Requested" options that the ADIF Group recommends.

.

[n2so]

Thanks so much, Nolan. In the "via" box in the received column I had previously entered "bureau". (From my first lookup which was a bureau card). When I removed it the information for the call sign look up appeared instantly. You are right, the options are sticky. I really appreciate your taking the time to attach a screen shot so I could see the problem.