Are you using any triggers or referential integrity?

When you run the debug and it works on record 123, which is consistently
skipped when you do not run debug, then how are you updating record 123
when you are not running debug?

A common mistake made when people first use triggers or referential
integrity and then hope that it works when they update the file using Excel
or something is that they assume that these utilities will use a library
list.  They often don't.  Most people test their trigger by signing into
their application and get their library list and environment all set and
they pressing a function key to get a command line.  From there they use
UPDDTA or some such thing.  I suppose that is a better test than just the
original maintenance application but it definitely doesn't cover the issue
of library list, etc.

Rob Berendt
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin



                    "Andrew Goade"
                    <agoade@hubgroup.       To:     rpg400-l@midrange.com
                    com>                    cc:
                    Sent by:                Fax to:
                    rpg400-l-admin@mi       Subject:     RE: RPG ILE Write
                    drange.com


                    03/18/2002 01:40
                    PM
                    Please respond to
                    rpg400-l







Yes, the same records constantly get skipped.  There is relatively minimal
logic in the program.  It basically moves info from one data source to
another.




                    Evan Harris
                    <spanner@ihug.co.       To:     rpg400-l@midrange.com
                    nz>                     cc:
                    Sent by:                Subject:     RE: RPG ILE Write
                    rpg400-l-admin@mi
                    drange.com


                    03/18/2002 12:29
                    PM
                    Please respond to
                    rpg400-l






Andrew

If you back out the changes and run it again do the same records get
skipped ?

This might give you a lead on whether its your program or some kind of
external effect that your program hasn't taken into account (environment
problem vs logic problem)

hth
Evan Harris


>For the records it doesn't write normally, it writes them in Debug.
>Basically, I have a record, let's say it's record 123.  I make a table
>change to 123, and it flows through my process.  However, my record
doesn't
>write to my file.  Now, I put my process in debug.  Again I make a change
>to 123.  When I break at the write and F10 through it, the record now
>appears in my file.  Now let's say that I enddbg and make a change to
>record 456.  It flows through my process and writes to my file.  This is
>not dependant on debug.  It will happen this way before or after I
>start/stop debug.


_______________________________________________
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l
or email: RPG400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.





_______________________________________________
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l
or email: RPG400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.







As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.