>>> getting a little long winded!
>>>
>>>Silly, but not so silly...
>>>
>>>I went looking into the table for said records, to see if they were deleted in error. Unfortunately, no... They were not there..
>>>
>>>thanks for all of your ideas,
>>>
>>>mike
>>They were not there ? Wasn't it a cursor ? You looked at workordr I guess. But I meant Jobstoprint. Deleted there, set deleted is on while scan...endscan but set deleted off in reporting (report use Jobstoprint or workordr?). And no code in between ?
>>Cetin
>
>Once the scan/endscan loop is done, this is the rest of the code.
>
>sele JOBSTOPRINT
>** run report
>report form wk_ordr2 to print noconsole
>return
>
>That's it., All she wrote...
>
>This all happens in code, no user intervention, except to pick the parameters for the report.
>
>Since I get all of the numbers, i.e. no missing ones, the numbers must be in the jobstoprint cursor.
>
>As stated previously, they are not appearing in the workordr table. That is the crux of the problem.
>
>Mike
Mike,
Also it seems that I acted as a blocking agent on this problem. Would you post as a new thread so better ideas might come in.
Cetin