Hi Mathew:
I do this in my workorder program. I have a main workorder table: wkmaster and the transactions table: wktrans (for work performed on the workorder). There are numerous other tables of course such as wkequip (for equip worked on) and wkparts (for parts used), etc.

I have a print button on a form to print the current work order. When I want to print a single workorder (the one currently displayed on the form), I have all of my tables setup and the relationships set first of course in the form's DE, then I issue the following code in the click method of the print button:

LOCAL lcwkrec
lcwkrec=this.parent.txtwkmaster_cwknumber.value
REPORT FORM ;
  wkmasterworkorderexistreport ;
  FOR wkmaster.cwknumber=lcwkrec ;
  NOCONSOLE ;
  TO PRINT

I have a report form created that groups on cwknumber in wkmaster and subgroups on cwknumber in the wktrans table. I put the workorder number in the page header, the main work order information from wkmaster in the group heading and I put the information from the child tables in the detail band. It works great. Hope this helps,
Tracy


>I am trying to move a legacy build FoxPro for Windows app to VFP6. This is an enterprise app that handles receiving, inventory management, workorders for p/u, delivery, and services, storage, and interfaces with Peachtree accounting for A/R. As a newbie to VFP, I will probably be asking this forum for advice quite often.
>
>I would like to know if Report Designer can be used to create work orders (as a one to many report) that will pull info from the currently open form that is being used to create the workorder and print only that workorder. Currently printing is handled by a .*prg where we are formatting the printing by line commands.
>
>Not all workorders are single page. The header and footer need to print only at the beginning and end of the print job with the work details in between.
>
>I began to visually format the report, and that is not a problem, but it just seemed that I might not be able to control this the way I need to.
>
>Thanks,
>Matthew