Here's where I am at with this...
BO.Method is Customer.Update.
Script is on a Pre-Process 4GL Action.
Define Variable curr-cust as rowid.
DEFINE FRAME a
ttcustomer.name
WITH 1 DOWN USE-TEXT.
For each ttCustomer exclusive-lock.
Do:
MESSAGE "Update " + ttcustomer.name + "?" VIEW-AS ALERT-BOX
QUESTION BUTTONS YES-NO UPDATE kill-it AS LOGICAL.
IF kill-it = No
THEN DO:
/*still working on the action for condition 'kill-it = No'*/
END.
END.
ENABLE ALL WITH FRAME a.
PAUSE 0 BEFORE-HIDE.
WAIT-FOR WINDOW-CLOSE OF CURRENT-WINDOW.
RELEASE ttCustomer.
END.
This procedure passes Validation without a problem but throws the following 4GL Stop error when run...
Error Detail
============
4GL STOP condition: The Server application has returned an error. (7243) (7241)
Stack Trace
===========
at Progress.Open4GL.DynamicAPI.Session.runProcedure(String requestID, String procedureName, ParameterSet parms, Boolean persistent, Boolean internal_Renamed, Int64 procId, MetaSchema localSchema, Int32 stateModel)
at Progress.Open4GL.DynamicAPI.Session.runStatelessProcedure(String requestID, String fullProcedureName, ParameterSet inparams, Object procId, MetaSchema localSchema, Int32 stateModel)
at Progress.Open4GL.DynamicAPI.PersistentProc.runTheProcedure(String requestID, String procedureName, ParameterSet parms, MetaSchema schema)
at Progress.Open4GL.DynamicAPI.PersistentProc.runProcedure(String procedureName, ParameterSet parms, MetaSchema schema)
at Epicor.Mfg.Proxy.CustomerImpl.Update(CustomerDataSet ds)
at Epicor.Mfg.UI.Adapters.CustomerAdapter.Update()
at Epicor.Mfg.UI.App.CustomerEntry.Transaction.Update()
The problem seems to be in the "ENABLE ALL WITH FRAME a." as I can turn it on and off by commenting out this line.
Any suggestions?
Thanks,
NB
--- In vantage@yahoogroups.com, "Nathan" <bonner.n@...> wrote:
>
> Dale,
>
> I am not having much luck getting this to work from within a BPM. Any other thoughts?
>
> Thanks,
>
> NB
>
> --- In vantage@yahoogroups.com, "Dale Schuerman" <dale.schuerman@> wrote:
> >
> > Nathan,
> >
> >
> >
> > This is the progress code. I have not tried it in a BPM. If No is
> > answered it leaves program.
> >
> >
> >
> >
> >
> >
> >
> > MESSAGE "Ready to begin the XXXXXXXXXX processing?"
> >
> > VIEW-AS ALERT-BOX QUESTION BUTTONS YES-NO UPDATE ok-beg AS
> > LOGICAL.
> >
> >
> >
> > IF not ok-beg THEN DO:
> >
> > RETURN.
> >
> > END. /* IF not ok-beg */
> >
> >
> >
> >
> >
> >
> >
> > Hope this helps.
> >
> >
> >
> > Dale E. Schuerman
> >
> > Senior Consultant
> >
> > Epicor Certified Consulting Partner
> >
> >
> >
> > RAM Software Systems, Inc.
> >
> > 972-669-0763 x233 (voice)
> >
> > 972-669-9603 (fax)
> >
> > mailto:dale.schuerman@
> > <BLOCKED::blocked::mailto:dale.schuerman@> (email)
> >
> > http://www.ramsys.com <BLOCKED::blocked::http://www.ramsys.com/>
> > (website)
> >
> >
> >
> >
> >
> > From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
> > Of Nathan
> > Sent: Friday, January 29, 2010 10:24 AM
> > To: vantage@yahoogroups.com
> > Subject: [Vantage] Progress Program for Dialog Box
> >
> >
> >
> >
> >
> > Vantage 8.03.408B(s)
> >
> > Hi,
> >
> > Looking for a Progress program in the Epicor Library or some custom 4GL
> > code that will give me the option to prompt users for a "YES/NO" or
> > "OK/CANCLE" response as part of an Update Pre-Process.
> >
> > Anyone have anything like this or some sample code I could start with?
> >
> > Thanks,
> >
> > Nathan Bonner
> > bonner.n@
> > totalplastics.com
> > 269.553.5838
> >
> >
> >
> >
> > ########################################################################
> > Attention:
> > This email message is privileged and confidential. If you are not the
> > intended recipient please delete the message and notify the sender.
> > Any views or opinions presented are solely those of the author.
> >
> > This email message has been scanned for Viruses and Content and cleared
> > by MailMarshal SMTP
> >
> > For more information go to http://www.ramsys.com
> > ########################################################################
> >
> >
> > [Non-text portions of this message have been removed]
> >
>