Did this article resolve your question/issue?



How to initialize global variables at the startup of AppBuilder?

« Go Back


TitleHow to initialize global variables at the startup of AppBuilder?
URL Name000039351
Article Number000161038
Question/Problem Description

How to initialize global variables at the startup of AppBuilder, so that any code executed inside AppBuilder will see those variables?

Steps to Reproduce
Clarifying Information
Error Message
Defect/Enhancement Number
Launching AppBuilder is actually running _ab.p under the hood. So you can wrap that procedure call by your own code that will set the proper variables:
  • Create a .p file that initialized the desired variables (those variables need to be defined as SHARED, e.g. "DEFINE SHARED VARIABLE myVar AS CHARACTER.")
  • Once those variables are set, run _ab.p
  • Call that .p file instead of launching the AppBuilder
Last Modified Date4/9/2013 1:36 PM
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.