The on-leave statements use progress/openedge abl. You can put them in a .p file or in the on-leave window, pretty much the same capability from each. Putting them in a .p file can be a bit easier as you just have to save the file after making changes, but doesn't give you much difference in functionality.
You can pickup a progress reference guide from progress, download for free. http://documentation.progress.com/output/OpenEdge102b/pdfs/dvref/dvref.pdf
The other item you can get from Epicor is the Product Configurator Technical Reference guide. You can get this via your Epicweb account.
Jim Kinneman
Encompass Solutions, Inc
You can pickup a progress reference guide from progress, download for free. http://documentation.progress.com/output/OpenEdge102b/pdfs/dvref/dvref.pdf
The other item you can get from Epicor is the Product Configurator Technical Reference guide. You can get this via your Epicweb account.
Jim Kinneman
Encompass Solutions, Inc
--- In vantage@yahoogroups.com, "Gibby" <guyguy50@...> wrote:
>
> I was wondering if anyone knows if it is avaible somewhere to find a syntax resource for on-leave statements. Beyond the epicor training books that is. I want to know what the entire scope of the language used for the on leave are, or even if anyone knows what language they are using.
>
> Thanks,
>
> ~Gibby
>