Fw: @ud and @ub updated

[Kenneth Brody]

Quoting Dennis Malen (Wed, 11 Apr 2007 13:32:23 -0400):

> Ken,
>
> I am not sure this is what processing you are looking for other than
> what I provided early on.

You told us that eliminating the automatic processing causes the
"problem" to go away.  You have not told us what is in the automatic
processing, which is a vital piece of information, since is the
automatic processing, and not the three lines of input processing
you have repeatedly shown us, that is causing your problem.

So far, everything points to your automatic processing doing something
to modify the record, forcing @ub/@ud to be updated.  However, we can
only guess, as you have still not posted any code other than those
same three lines of input processing.

> The email sent on 04.06.07 provides the @key processing which concludes
> with an "end" statement. See below.

You have told us that running those lines, and those lines alone, will
not cause your problem.  You have also said that running those three
lines, plus the automatic processing, does cause your problem.  Posting
the same three lines again doesn't help find what you are doing to
cause the problem.  Posting all of the code that gets executed is the
only way anyone can help you find your problem.

> If that is not what you want do you need to see each line executed when
> the debug was turned on?

To quote my previous requests:

    04/09/2007 19:48:02

        Run with the debugger on, and single-step the entire @KEY
        process.  What lines are executed?

    04/10/2007 16:49:13

        Now, when you turn the debugger on, and press the key that
        starts your @key routine, what are the lines that get
        executed?

    04/10/2007 20:40:19

        You also haven't answered the questions that were asked --
        such as what were the lines of processing that were executed.
        [...]
        Request for the third (or is it fourth?) time:  When you step
        through the debugger, what statements are executed?

So, I ask once again:

    When you step through the debugger, what statements are executed?

> If so what would be the best method to capture those
> lines for you?

Whatever method works best for you, as long as you show all of
the code that gets executed.

How many lines are there?  Perhaps simply posting the entire auto
processing would suffice?

> Additionally, I thought that the distinction of how the non quikstart
> and quikstart IUA was a significant distinction.

You still haven't answered the question posed by JP and myself --
are you running the same processing in dclerk as well as rclerk?
(ie: did you recompile the modified auto and input tables?)

[...]

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