Yeah, I'd buy that explanation (PartPlant AddRow still a db level .p trigger). Hopefully over time they will get around to fully exposing all methods and properties for VB code use and manipulation.
The after_partadapter method I described below will work until then. A PartPlant record will exist (and you can then set your defaults) once Case AddNewPart is directly followed by a Case Update. Use the If statement based var counter technique to determine when that is true (and to avoid repetitively setting your defualts more than once).
Rob Brown
The after_partadapter method I described below will work until then. A PartPlant record will exist (and you can then set your defaults) once Case AddNewPart is directly followed by a Case Update. Use the If statement based var counter technique to determine when that is true (and to avoid repetitively setting your defualts more than once).
Rob Brown
--- On Tue, 5/6/08, bw2868bond <bwalker@...> wrote:
From: bw2868bond <bwalker@...>
Subject: [Vantage] Re: Default Part Mainenance Fields
To: vantage@yahoogroups.com
Date: Tuesday, May 6, 2008, 6:47 PM
More than likely the PartPlant record is added as a result of a
database update trigger which are compiled encrypted .p files and the
dataviews and adapter methods are not involved....
.02
--- In vantage@yahoogroups .com, Robert Brown <robertb_versa@ ...>
wrote:
>
> There are trans methods to force notification but I'm not familiar
with them (and assume the programmers who wrote part entry suppressed
addrow for a reason).
>
> You'll have to trick it. Set up an aftermethod event trigger on
partadapter. Inside (before the case statements), set up a variable
to act as a counter with initial value 0. Set the variable to 1 on
Case AddNewPart (check the literature to make sure that is the real
name of it).
> Inside Case Update, do an if (var) = 1 then (do your defaulting to
PartPlant as at least one PartPlant record row(0) must now exist for
the new part), Else (var) = 0 End If.
>
> There is always a way.
>
> Still, seems like it would be more effective to just set up some
template items and base the process on people instead of code.
>
> Rob Brown
>
> --- On Tue, 5/6/08, laidig.systems <laidig.systems@ ...> wrote:
>
> From: laidig.systems <laidig.systems@ ...>
> Subject: [Vantage] Re: Default Part Mainenance Fields
> To: vantage@yahoogroups .com
> Date: Tuesday, May 6, 2008, 7:54 AM
>
>
>
>
>
>
> Unfortunately the EpiViewNotification event on PartPlant doesn't
fire
> upon NotifyType.AddRow. It only fires upon NotifyType.Initiali ze,
but
> when i set the backflush flag in initialize, vantage runs closes
down.
>
> --- In vantage@yahoogroups .com, Robert Brown <robertb_versa@ ...>
wrote:
> >
> > Try using an EpiViewNotification event on PartPlant. That will
> insure it is there before you start pushing your company's default
> values into the appropriate fields.
> >
> > Better yet, why not create (perhaps several) 'template' parts and
> copy from them when creating new parts?
> >
> > Then you can manage/change part set up policy by changing the
> templates (instead of having to edit vb code).
> >
> > If you simply must do this via vb code, at least consider using a
ud
> table (set up with your default values in appropriate type fields -
> and well documented!) , bring the ud table into Part Entry as an
FKV,
> and then use the EpiNotify event to trigger the appropriate series
of
> copied values from ud fields to their corresponding PartPlant
fields.
> >
> > That would give you the best of both worlds as you could extend
it,
> set up a user role (or userID) security controlled epiButton to
> > trigger a reverse copy of PartPlant values back to the ud table
> record fields.
> >
> > Part Entry would then also be your maintenance app for
your 'templates'.
> >
> > Rob Brown
> >
> > --- On Mon, 5/5/08, laidig.systems <laidig.systems@ ...> wrote:
> > From: laidig.systems <laidig.systems@ ...>
> > Subject: [Vantage] Default Part Mainenance Fields
> > To: vantage@yahoogroups .com
> > Date: Monday, May 5, 2008, 4:02 PM
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Is there a way to default fields on the part maintenance
> form in the
> >
> > plant tab? I am trying to default the backflush field on the
plants
> >
> > tab when a new part is created. I can't seem to do this with
> >
> > customizations/ BPM upon save of the new part because the
partplant
> >
> > table gets created after the part is created. If i try to default
it
> >
> > when the user clicks "new part" it errors because there is no
plant
> >
> > record yet for this new part. Any suggestions?
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Be a better friend, newshound, and
> > know-it-all with Yahoo! Mobile. Try it now.
> >
> >
> >
> >
> ____________ _________ _________ _________ _________ _________ _
> > Be a better friend, newshound, and
> > know-it-all with Yahoo! Mobile. Try it now.
> http://mobile. yahoo.com/ ;_ylt=Ahu06i62sR 8HDtDypao8Wcj9tA cJ
> >
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
____________ _________ _________ _________ _________ _________ _
____________ __
> Be a better friend, newshound, and
> know-it-all with Yahoo! Mobile. Try it now.
http://mobile. yahoo.com/ ;_ylt=Ahu06i62sR 8HDtDypao8Wcj9tA cJ
>
____________________________________________________________________________________
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ