>>>>>If this value is being used in a lot of files in the app, it sounds like a good excuse for a PUBLIC variable..
>>>>
>>>>It may be better to use application object property instead.
>>>
>>>Why (just curious)?
>>
>>You have just one global object and access its properties rather than creating public variables for most used things.
>
>So anywhere you use it you use _application.MAXRXS rather than MAXRXS.
>
>It may be more OOP but it doesn't seem to make much difference (except a longer variable reference) to me..?

It is a 'style' issue. Personally, I prefer object because I don't want to use somewhere local variable of the same name and forget to declare it properly; and I always forget/confuse how to declare variables so I decided to use LOCAL variables only.