Jeff
Using the coverage profiler, check if CURPOS is mentioned in
your program. It could happen just for this customer's application.
HTH, E.
*------------
Cathy: I finally got a chance to look into this. I took a good frx and
the only change I made was to change the value of a label and it
reproduced the bad behavior. The only difference (other than the
horizontal position and value in the label) was CURPOS. CURPOS of the
good report is set to T for the last record in the frx and all others
are F. The CURPOS of the bad report is set to T in the first record and
all others including the last record is F. I changed the first record
to F and the last record to T and the report ran correctly.
I looked into what CURPOS was and didn't fully understand it.
If this is causing the problem, what is setting CURPOS incorrectly?
This appears to only be affecting one customer's application.
Thanks!
Jeff
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
