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



I have no desire to beat on a dead horse, but if you are going to be sending messages anyway, why not just pop-up a window saying "The new customer number is: "12345" " when they click the add button. The new customer number is assigned quickly by the trigger program, so no user delay will be experienced.

(My fear is that if your trigger chases down all the child files that can be affected today, that design would fail tomorrow when the gunslinger from out of town adds a new child file and doesn't know he is supposed to tell you about it.)




On 9/2/2011 1:18 PM, Terry Anderson wrote:
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.)



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.