Hi, Sivaprakash -

PB applications are single-threaded by default... there is no "background" thread in a normal PB app. Everything executes in the main GUI thread.

However, it is possible to create a non-visual object and have PB instantiate and execute code in this NVO in an alternate execution thread. These are called shared objects (this is completely different than shared variables).

There is currently very little helpful information/documentation available on PB shared objects and multi-threading. In my spare time for the last several months I've developed an example PB application that can perform multi-threaded database retrievals using a shared object and written an accompanying tutorial. The app will very soon be submitted for review and publication in the CodeXchange section of the Appeon Community. The tutorial will also be submitted for publication in the Tech Articles portion of the Articles & Blogs area. I'm hopeful I can submit both before the start of the new year, so watch for them in early 2022 if you think this might be helpful to you.

Multi-threading in PB is possible, but it is not trivial or easy to accomplish. I would categorize it as an advanced topic, but yet it is not rocket science... there are simply several very important factors and considerations you need to be aware of and scant resources to help you out. You can look in PB Help for the topic "SharedObjectGet" for an overview of what is involved.

John

Hi BKR ;

   This question is not related to any particular DBMS. The key is to use a secondary process to perform the data retrieval and printing (or PDF generation for that matter). I do this quite often using this feature ...

http://chrispollach.blogspot.com/2019/12/socket.html

  This allows for a secondary App thread for the above work to proceed with the immediate return of control back to the main PB App for the user to continue with their other business transactions. Note that you could also perform this secondary task as a batch PB App running on the DBMS server. This could be via inserting a row into a DB Table and having a Trigger run the external PB App batch print from there too (another idea).

Food for thought.  HTH

Regards ... Chris

do you have the printer setup to spool instead of print directly?  it is a windows printer setup setting.  if you have print directly then you wait for the printer to finish.

you could build a report server application - the users send a report print request and the reporting application retrieves the data and sends it to the printer.