@ud and @ub updated

[Kenneth Brody]

Quoting Dennis Malen (Tue, 10 Apr 2007 19:22:57 -0400):

> I now have the results after having used the debug utility. It did not
> give us an answer to the problem but raised more questions.

You also haven't answered the questions that were asked -- such as
what were the lines of processing that were executed.

> Before I describe what happened when we used the debug utility I think
> it is important that you be aware of the following:

I don't see why answering questions that have not been asked is more
important than answering the ones that have been asked, repeatedly.

> We first put an "end" on the first line of auto proc. We then went into
> "B - IUA" (non quikstart) and the @key worked without updating the
> record. When following the same procedure in "H - IUA - Quikstart" the
> use of the @key updated @ub and @ud.

Sounds like you forgot to compile the modified automatic processing.
If you recompile the modified auto prc (and the input, just to be
sure that you are running the same thin in dclerk and rclerk), and
both clerks no longer update @ub/@ud, then it is probably something
in the automatic processing that caused the record to be modified
and @ub/@ud updated.

> 1. We removed the end statement in auto proc and then proceeded to turn
> the debug on at the first line of the @key processing. We entered "B -
> IUA".

[... snip description of standard processing flow, through @key's END ...]

> 4. It then went back to auto proc and before it read the first line
> (which is a commented out "end" statement) we pressed ENTR while in
> debug mode to get to the next line and it updated @ub and @ud at that
> point.

Translation:  When processing ended, the record was written, and
@ub/@ud were updated because the record was modified.

[...]
> Conclusion: There seems to be an issue when reentering auto proc for the
> second time. While considering the second entry to auto proc it is also
> important to keep in mind the problem with quikstart and nonquikstart
> that was described above.
[...]

Conclusion: Something in your still-undisclosed processing modified
the record, causing @ub/@ud to be updated.

Have you run without the auto processing?  (Yes, you have.  You said
above that putting an "end" as auto's first line caused @ub/@ud to
no longer be updated.)

Further conclusion:  your automatic processing does something to
modify the record, causing filePro to update @ub/@ud.


Request for the third (or is it fourth?) time:  When you step through
the debugger, what statements are executed?

--
KenBrody at BestWeb dot net        spamtrap: <g8ymh8uf001 at sneakemail.com>
http://www.hvcomputer.com
http://www.fileProPlus.com