×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
a.. From: Booth Martin <booth@xxxxxxxxxxxx>
b.. Date: Thu, 01 Sep 2011 11:59:55 -0500
c.. List-archive: <
http://archive.midrange.com/rpg400-l>
d.. List-help: <mailto:rpg400-l-request@xxxxxxxxxxxx?subject=help>
e.. List-id: RPG programming on the IBM i / System i <rpg400-l.midrange.com>
f.. List-post: <mailto:rpg400-l@xxxxxxxxxxxx>
g.. List-subscribe: <
http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@xxxxxxxxxxxx?subject=subscribe>
h.. List-unsubscribe: <
http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@xxxxxxxxxxxx?subject=unsubscribe>
--------------------------------------------------------------------------------
Have you considered writing a small program that has only the job of assigning customer numbers, then, using the *before trigger, just replacing whatever number the incoming record has with the newly assigned number from your program? That way there will never be a conflict to deal with, and a whole lot of field training that never needs to be done? (No need to teach the branches all of the rules for assigning customer numbers - just tell all branches to always use 999 as their new customer number.)
***********************************
... I would be very, very, very carefully with this very, very, very strange idea, how should the requesting programm understand what's happening???
D*B
midrange.com
