RE: Prevent a record from being written using a trigger program.

Booth,
I don't think that would work in this instance. The division still
needs to know the customer number is so they can the create packing
slip, bill of lading and ASN. The third party program also updates
other files like the ship to master.

I think the best way for me to go, would be the suggestion of letting
the third party program update the files then use my trigger to delete
the records if the customer number the user entered was not in a file of
corporate sanctioned numbers. I would also need to send a message or
pop up a window letting the user know what happened.

Thanks to everyone who responded! I get a lot of good ideas and things
to think about from this list!




Terry Anderson
Programming Manager
Grede LLC.
Switchboard 1.251.867.5481 ext 212
Direct Line 1.251.809.2312
Fax 251.867.0525
Cell 1.251.363.4975



----------------------------------------------------------------------

message: 1
date: Thu, 01 Sep 2011 11:59:55 -0500
from: Booth Martin <booth@xxxxxxxxxxxx>
subject: Re: Prevent a record from being written using a trigger
program.

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.)