Well I've done some more research as you suggested. Here's what I've found. If you create a brand new form and place a single button on it with the following code in the click event it will work fine.

clear
fileloc = 'd:\foxpro\pagmodel\counts'
use fileloc + '\turns' in 0 alias turns order int_id
use fileloc + '\intersection_master' in 0 alias intersection_master
select intersection_master
set relation to int_id into turns
set skip to turns
set reportbehavior 90
select turns
set filter to between(hour(_time),7,9) and int_id = intersection_master.int_id
select intersection_master
report form rptTurns for int_id = 597 and between(hour(turns._time),7,9) to printer prompt preview noconsole

However if you then change the form to be a top level form, it will exhibit the behaviour I described. i.e. the toolbar will not function. Adding the NOWAIT to the end of the report form command will fix the problem but creates other problems. Changing the form back to be In Screen reverts it back so it will work.

So, the problem seems to be using the new report engine with a top level form. Unfortunately, most of my forms are top level forms. Do you know of a work around for this situation?



>>When using the new report engine as in

>>set reportbehaviour 90

>>it seems to be necessary to use the NOWAIT phrase in the report command as in
>

>>report form rptTurns for recno()=thisrec and between(hour(turns._time),7,9) to printer prompt preview noconsole nowait

>>Leaving the NOWAIT out prevents the toolbar from becoming active and stalls the program.
>
>That doesn't sound right: have you tested with a simpler scenario?