> On 10-Oct-2005 01:36:48, Helen wrote:
> To do what you want to do, you would need to be in the situation whereby,
> at the time you write that PART_STOCK record, you have already created the

> WAREHOUSE record (if the trigger is firing from PART) or you have already
> created the PART record (if the trigger is firing from WAREHOUSE). The
> problem with doing this in a trigger from either of the primitives is that

> triggers can't take input parameters, so you have no way to tell the PART
> trigger the warehouse id, or to tell the WAREHOUSE trigger the part id.

Thanks so much for your detailed answer. I was able to fix this problem
when I realized what I was doing. I was attempting to create one trigger
that did all of the items I needed, and I had it at position 0 in the fire
order. When I realized that I could create a trigger at position 1 in the
order, and then break up what was required for this, it began to work
without any issue.

As for the technique of creating records that may never have values, you are
correct. However I will go with something that is probably more data that I
need to create for now while I'm dealing with all of this new technology,
and attempt to refine that later.

Thanks again for your thoughts.

Regards,
Myles

===============================
Myles Wakeham
Director of Engineering
Tech Solutions US, Inc.
Phone (480) 451-7440
www.techsol.org