Application Global Variables in functions

[Pat Bremkamp]

I've started using the Application Global Variables in the Project Properties and I like the ability to have various parameters in pages and components without having to do another SQL lookup. I also like that they can be typed instead of all having to be character. They are working fine. A few of the ones I use are

ChartColors = "2010 AFD8F8 2011 F6BD0F 2012 8BBA00 2013 E9967A 2014 8FBC8F 2015 429EAD"
ChartStartYear = 2010
HSTTaxable = "false"
HSTTaxRate = 12
GSTTaxable = "true"
GSTTaxRate = 5


I would like to also use these in User Defined functions. According to the write-up, all I have to do is

dim projProp as p
projProp = a5_getWebProjectProperties()

Then I should be able to use
projProp.ChartColors to get the string.

Using debug(1), I can see that projProp is getting assigned a whole bunch of properties, including the ones I listed, but when I try to use
projProp.ChartColors, it gives me the error subelement not found.

Anyone know what I'm missing in my syntax?
Thanks,

[Jim Coltz]

Re: Application Global Variables in functions

It looks like all the applicationGlobalVariables are stored in the project properties as a list and not as individual elements.

From the interactive window using your example:

dim projProp as p

projProp = a5_getWebProjectProperties()

?projProp
+aexFiles.
applicationGlobalVariables = ChartColors = "2010 AFD8F8 2011 F6BD0F 2012 8BBA00 2013 E9967A 2014 8FBC8F 2015 429EAD"
ChartStartYear = 2010
HSTTaxable = "false"
HSTTaxRate = 12
GSTTaxable = "true"
GSTTaxRate = 5
autoBackupFolder = ""
+calendar.
convertXPSToPDF = .T.
+css.
+cssLibraries.
+designTime.
+email.
+fileDownload.
+helpTable.
+jsLibraries.
projectStyle = "GrGray"
+reportServer.
+repository.
+textDictionary.
useMicrosoftXPSPrinterForPDF = .F.
+workQueue.

?projProp.applicationGlobalVariables
= ChartColors = "2010 AFD8F8 2011 F6BD0F 2012 8BBA00 2013 E9967A 2014 8FBC8F 2015 429EAD"
ChartStartYear = 2010
HSTTaxable = "false"
HSTTaxRate = 12
GSTTaxable = "true"
GSTTaxRate = 5

?projProp.chartstartyear
ERROR: Property not found 
projProp.chartstartyear subelement not found.

One way to do this, if you really need to, I don't know if it's the best way or not, is to evaluate the string to assign the variables.

for each foo in projProp.applicationGlobalVariables
  evaluate_template(foo.value)
next

?chartcolors
= "2010 AFD8F8 2011 F6BD0F 2012 8BBA00 2013 E9967A 2014 8FBC8F 2015 429EAD"

?HSTTaxable
= "false"

With that being said. If you're using these in a web app then they are already available to your custom functions in the AppVar namespace and you don't need to do anything but reference them. See the image below of a UDF running in dialog component. Note that they don't work in working preview, but do in live preview so beware of that limitation.

Appvar.PNG

[Pat Bremkamp]

Re: Application Global Variables in functions

Thanks Jim,

I guess I was overthinking this. When they said pages and components, it seemed they were excluding functions. As you suggested, I just tried using AppVar and it works beautifully.

[Steve Workings]

Re: Application Global Variables in functions

I don't see a simple non-kludgy way to use the AppVars in reports - say, as calculated fields in the report.

For instance, I'd like to declare an AppVar of

dim CompanyName as C = "My Company, Inc."

Then, at its simplest, set up a calc field in the report:

calc->av_Company = AppVar.CompanyName

That, of course, does not work. I suppose I could build a UDF that leverages what Jim shows here and draw from that.

Any thoughts?

[Peter.Greulich]

Re: Application Global Variables in functions

This looks interesting. Are appvars a kind of replacement for session vars?

[Clipper87]

Re: Application Global Variables in functions

Peter,

session vars are bound to a session & sessions can expire causing the session vars to expire as well. Appvars don't expire.

[Peter.Greulich]

Re: Application Global Variables in functions

Wow. So they are "forever". That makes sense. I would have to think of the ramifications of that.

[Pat Bremkamp]

Re: Application Global Variables in functions

While there are some detrimental ramifications (love that phrase), it is a great place to put parameters that rarely change. In my case, I put in the colors that I want the chart to display for each year. Once per year, I add a year and a color. Then, I use that in about 6 different charts without having to open a connection and get it out of MySQL. Another is tax rates. When they change, I change them here and know that they are changed everywhere they are needed.

I also use it for the old [PathAlias.whatever]. For example, when I upgraded from V11 to V12, I had both versions running for a while, so the webroot was in a5v11 for one and a5v12 for the other. So, I have a parameter for imagedir = "c:\a5v12\a5webroot\images". When I go to 13, just change it here.