Why?

George Simon george at worldest.com
Thu Jul 1 07:33:00 PDT 2004


To clarify the previous post a little bit, the error occurs ONLY from
*report when using the normal automatic table and calling the "getlong"
table from automatic processing.  If I remove the line calling the "getlong"
table from automatic processing and call it from the output processing table
(compare) running *report, I DO NOT get the error.  If I call the table from
@once, I DO NOT get the error.  If I cut down the automatic table to only
the dummy field definitions needed to run the report, I DO NOT get the
error.
I DO NOT get the error from *rclerk, no matter where the table is called
from.
I ONLY get the error when using the 1,249 line automatic processing table to
run the report AND the table (getlong) is called from that automatic table.

George Simon (IT Department)
American River Logistics, LTD
614 Progress St.
Elizabeth, NJ  07205
Phone:(908)354-7746      Fax:(908)354-7491
mailto:george at worldest.com
http://www.americanriverintl.com/



-----Original Message-----
From: filepro-list-bounces at lists.celestial.com
[mailto:filepro-list-bounces at lists.celestial.com]On Behalf Of George Simon
Sent: Thursday, July 01, 2004 10:23 AM
To: Kenneth Brody; George Simon
Cc: filePro mailing list
Subject: RE: Why?

I posted the entire called table.

I ran a report using an automatic table consisting of only 23 lines.  All of
these lines were dummy field definitions needed to run the report.  No other
processing done from automatic except to call the "getlong" table.
When I run the report this way, I do not get the error.
So it must be something in the other 1,226 lines of code that breaks it, but
only when the table (getlong) is called from automatic processing.  If I
call the table (getlong) from the output processing table (compare) using
the normal automatic table, the error does not occur.

George Simon (IT Department)
American River Logistics, LTD
614 Progress St.
Elizabeth, NJ  07205
Phone:(908)354-7746      Fax:(908)354-7491
mailto:george at worldest.com
http://www.americanriverintl.com/



-----Original Message-----
From: Kenneth Brody [mailto:kenbrody at bestweb.net]
Sent: Thursday, July 01, 2004 9:35 AM
To: George Simon
Cc: George Simon; filePro mailing list
Subject: Re: Why?

George Simon wrote:
>
> So you are saying that automatic processing could run the code differently
> when running from *report than when running from *clerk?

As I've said several times earlier in this thread:

  But *clerk is still working on 1 record at a time, and *report is still
  working on sets of records (even if the "set" consists of 1 record) and
  is doing break levels and grand totals.

> OK, I'll do this for you, I'll run the process with an automatic table
that
> has only the dummy field definitions and the line that calls the process.

Thank you.

And don't forget to strip the called table down to just the lines that
you have posted here.

--
+-------------------------+--------------------+----------------------------
-+
| Kenneth J. Brody        | www.hvcomputer.com |
|
| kenbrody at spamcop.net | www.fptech.com     | #include <std_disclaimer.h>
|
+-------------------------+--------------------+----------------------------
-+

_______________________________________________
Filepro-list mailing list
Filepro-list at lists.celestial.com
http://mailman.celestial.com/mailman/listinfo/filepro-list



More information about the Filepro-list mailing list