Missing line

[Bruce Easton]

"Simple report output"

Considering my unanswered question a while ago, and then Jose's, I'm not 
sure what you mean by that.

Please, in addition to answering Ken's questions, please confirm 
***that, for the line on the format where data doesn't show for the 
record, you are NOT using dummy fields***.

Because if you are using dummy fields (arrays or not), the problem then 
may involve processing to include auto/output processing (and can be an 
issue that is logic and/or data related).

On 8/2/16 3:35 PM, Jose Lerebours via Filepro-list wrote:
> OK, so the next things are
>
> Q. are you using indexes?
> Q. are you using selection table?
>
> If using any of these, is the record shown in IUA using the same 
> index/selection table?
>
> If using index and it "does not find" the record in IUA, try 
> rebuilding the index.
>
>
> On 08/02/2016 03:32 PM, Richard Kreiss wrote:
>> Jose,
>>
>> You are over thinking.
>>
>> Simple report output.
>>
>> Sort 1 - primary break 4 digit #
>> Sort 2 - member # break 2 aging printed at this break. Totals held in 
>> dummy fields. No arrays.
>>
>> After the missing first record everything prints properly
>>
>> Richard
>> Sent from my iPhone
>>
>>> On Aug 2, 2016, at 12:13 PM, Jose Lerebours via Filepro-list 
>>> <filepro-list at lists.celestial.com> wrote:
>>>
>>> One thing comes to mind ... Say if you have an form where output is 
>>> done via use of dummy variables such as
>>>
>>>
>>> *aa    *ab    *ac   *ad
>>>
>>>
>>> and these are in turn associated or populated by use of an array 
>>> like output(280,*):aa or similar - The values are populated by 
>>> another dummy variable like ln(2,.0) ( output(ln)="  " ... ) so, if 
>>> counter is set at wrong level, you can have the problem you 
>>> describe, especially so if the counter is conditionally set.
>>>
>>> Also, if you are printing a detail or summary type of form may have 
>>> an effect since the missing record may or not trigger a break on 
>>> your report thus not printing at all.
>>>
>>> A snapshot of what the form looks like (as defined) may help but 
>>> then again, tough to do via list.
>>>
>>> Regards,
>>>
>>>
>>> Jose
>>>
>>>
>>>
>>>> On 08/02/2016 02:28 PM, Richard Kreiss via Filepro-list wrote:
>>>> Just the first record for some of these codes not all.
>>>>
>>>> Richard
>>>> Sent from my iPhone
>>>>
>>>>>> On Aug 2, 2016, at 9:28 AM, Kenneth Brody <kenbrody at spamcop.net> 
>>>>>> wrote:
>>>>>>
>>>>>> On 8/1/2016 2:06 PM, Richard Kreiss wrote:
>>>>>> A report which breaks on a code number doesn't print the first 
>>>>>> record selected for that code.
>>>>> It doesn't print the first record for every code, or just for the 
>>>>> first code?
>>>>>
>>>>>> This is an A/R report and it happens for the same code but 
>>>>>> different person.
>>>>> So it works for some people, but not others?
>>>>>
>>>>>> There is no print command in the code as all other records print.
>>>>> The fact that the other records print does not preclude the 
>>>>> existence of a "print" command.
>>>>>
>>>>>> Any suggestions as to what to look for?
>>>>> I would start by verifying that there is, in fact, no "print".  
>>>>> (And if there is, figure out why the first record doesn't execute 
>>>>> it.)
>>>>>
>>>>> -- 
>>>>> Kenneth Brody
>>>> _______________________________________________
>>>> Filepro-list mailing list
>>>> Filepro-list at lists.celestial.com
>>>> Subscribe/Unsubscribe/Subscription Changes
>>>> http://mailman.celestial.com/mailman/listinfo/filepro-list
>>> _______________________________________________
>>> Filepro-list mailing list
>>> Filepro-list at lists.celestial.com
>>> Subscribe/Unsubscribe/Subscription Changes
>>> http://mailman.celestial.com/mailman/listinfo/filepro-list
>
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> Subscribe/Unsubscribe/Subscription Changes
> http://mailman.celestial.com/mailman/listinfo/filepro-list
>



---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus