BAM and .p triggers v6.1

Correct David. Set up a separate BAM(s) to be the trigger for .p files and
only select the field(s) who's change will trigger your BAM and subsequently
your .p.
Also, remember when testing .p files to restart Vantage on the computer
being tested between .p revisions or you will be left scratching your head
for why your change did absolutely nothing.

Aaron Hoyt
Vantage Plastics

-----Original Message-----
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]On Behalf Of
David Gartner
Sent: Wednesday, September 26, 2007 11:57 AM
To: vantage@yahoogroups.com
Subject: [Vantage] BAM and .p triggers v6.1


We are going to V6.1 before year end. The hardware expenditure to V8, when
we really want the CRM functionality alluded to in V9, is too great. Not
to
mention the burnt sensation from the 6.1 "CRM release" I still feel on
occasion. Anyway...

I want to run multiple BAMs based on certain tables. If I am monitoring
all
the fields I need for one table under one action item, then I only to
select
the trigger field on additional .p BAMs, correct?

Thank you,
David

[Non-text portions of this message have been removed]






[Non-text portions of this message have been removed]
We are going to V6.1 before year end. The hardware expenditure to V8, when
we really want the CRM functionality alluded to in V9, is too great. Not to
mention the burnt sensation from the 6.1 "CRM release" I still feel on
occasion. Anyway...

I want to run multiple BAMs based on certain tables. If I am monitoring all
the fields I need for one table under one action item, then I only to select
the trigger field on additional .p BAMs, correct?

Thank you,
David


[Non-text portions of this message have been removed]