It's worth point out that Andrew has indirectly answered your original question: Can I create a Request whose output can be used as input to a second Request? (I realized you solved this in a single Request by creating a calculated "sub-query" data item in the dictionary.
But the answer to your original question os yes, right now with v6.06 (and even earlier versions) you can chain reports so that the output of one becomes input to the next (and the chain can contain unlimited Requests).
The trick is to decide on a structure for the intermediate table (the one that will pass the data from the first Request to the second) and define those items in the Foxfire! data dictionary. The name you specify in the result name on the first page of the existing field would be used in the data item expression of each new item's definition. You will specify the name of the intermediate table in the expression for each new data item.
Then create the first Request with the filter conditions that identify the records you want to process in the second Request. Specify that the output of the first Request goes to a table with the name you chose for the intermediate table, and choose those fields you need to process the second Request.
Next, define the second Request using the new data items. You may have further filtering on the intermediate table, but you should have all the records you need for that second Request.
I realize you don't need to solve the original problem, but this may come in handy in other situations.
What Andrew was referring to when he discussed v8.1 was an enhancement that would automatically add the intermediate table's data items to the dictionary to save several steps.
I'm glad you've found ways to make Foxfire! more useful for you.
Would you be willing to write up a set of simple instructions for creating a sub-query item that we can post to our forums for future readers?
Also, I think you would be very pleased to review the enhancements in v8+ You can download a free trial copy and convert your v6.06 app very easily to try it out for 30 launches within 60 days.