Re: RPG COMP HiLoEq

Absolutely!  Although in this particular instance I am inclined to first support the question being asked that led to the discussion:

The program in question does not behave as everyone here agrees is the way it will behave.  Something else is going on and the concern is that if they don't figure it out the real problem will remain.

Here's when it does NOT behave as expected:  UserA and UserB update a record at exactly the same time.  Very unusual occurrence, perhaps 2 or 3 times a year.  The error is discovered now, in 2020, and the program has been in production for 20+ years.  Clearly this is not a the-village-is-burning level question.

What does happen when UserA and UserB  collide?  UserA updates the correct record, UserB updates the next previous record. Looks like a need to recreate the actual scenario because something isn't as it seems.

I asked the question originally because I wanted to be dead-ass sure that COMP worked the I "knew" it does.   When I am the wrongest is when I am convinced I am the rightist.  So I asked.

Thank you everyone for the confirmations; it helps.

On 5/18/2020 11:20 AM, Jon Paris wrote:

I am SO happy we got rid of that horrible crap in RPG IV. It will however remain a mystery to me as to why those programs still exist - let alone get maintained rather than converted!