| **Navigation:**  [[abc library reference.htm|ABC Library Reference]] > ReportManager Class > ReportManager Properties >====== TimeSlice (report resource usage) {{c6h0009.jpg|C6H0009.jpg}} ====== | [[targetselectorcreated report target active .htm|{{btn_prev_n.gif|Previous page}}]][[abc library reference.htm|{{btn_home_n.gif|Return to chapter overview}}]][[usemrp ipd multiple request packet support  1.htm|{{btn_next_n.gif|Next page}}]] |
|  ||

|  | **TimeSlice** | **USHORT** |

{{blk2blue.jpg|blk2blue.jpg}}

The **TimeSlice **property contains the amount of time in hundredths of a second the ReportManager tries to "fill up" for each processing "cycle." A cycle begins with an EVENT:Timer (see //TIMER// in the //Language Reference//), and ends about TimeSlice later. For example, for a TimeSlice of 100, the ReportManager processes as many records as it can within about 100/100 (one) second before yielding control back to the operating system. To provide efficient sharing of machine resources, we recommend setting the TIMER to something less than or equal to TimeSlice.

**Implementation:**

The Init method sets TimeSlice to one (100). The TakeWindowEvent method continuously adjusts adjusts the number of records processed per cycle to fill the specified TimeSlice--that is, to process as many records as possible within the TimeSlice. This provides both efficient report processing and reasonable sharing of machine resources, provided the TIMER value is less than or equal to the TimeSlice value. This leaves the user in control in a multi-tasking environment, especially when processing a large data set.

**See Also:     **[[init  initialize the reportmanager object .htm|Init]], [[takewindowevent  a virtual to process non field events reportmanager .htm|TakeWindowEvent]]