I think that when you call UD forms, LFO works a little differently.
Last time I did this (for a BAQ Report), we used ContextValue rather than ValueIn and then had to modify the UD form to receive the LFO as well with a Form Load event.
private static void BAQReportForm_Load(object sender, EventArgs args)
{
// Add Event Handler Code
if (BAQReportForm.LaunchFormOptions != null)
{
// Grab LFO passed from parent form:
string PassedValue = BAQReportForm.LaunchFormOptions.ContextValue.ToString();
}
}
Last time I did this (for a BAQ Report), we used ContextValue rather than ValueIn and then had to modify the UD form to receive the LFO as well with a Form Load event.
private static void BAQReportForm_Load(object sender, EventArgs args)
{
// Add Event Handler Code
if (BAQReportForm.LaunchFormOptions != null)
{
// Grab LFO passed from parent form:
string PassedValue = BAQReportForm.LaunchFormOptions.ContextValue.ToString();
}
}
--- In vantage@yahoogroups.com, Jose Gomez <jose@...> wrote:
>
> I have the following on an button click event on MES
>
> dim lfo as LaunchFormOptions = new LaunchFormOptions()
> lfo.IsModal = true
> lfo.ValueIn = edvLaborDtl.dataView(edvLaborDtl.row)("JobNum")
> ProcessCaller.LaunchForm(oTrans, "UDEnd", lfo)
>
> It is launching the form, but the value is not being passed into the form
> for some reason. Any idea what could be going on?
>
>
>
>
> *Jose C Gomez*
> *Software Engineer*
> *
> *T: 904.469.1524 mobile
> E: jose@...
> http://www.josecgomez.com
> <http://www.linkedin.com/in/josecgomez> <http://www.facebook.com/josegomez>
> <http://www.google.com/profiles/jose.gomez> <http://www.twitter.com/joc85>
> <http://www.josecgomez.com/professional-resume/>
> <http://www.josecgomez.com/feed/>
>
> *Quis custodiet ipsos custodes?*
>
>
> [Non-text portions of this message have been removed]
>