>>>>>>>>>>>What is the simplest explanation as to why these are needed? Why not just set regular variable values? So what if they are constant and don't change?
>>>>>>>>>>
>>>>>>>>>>Security of the source code so that reverse engineering of an application won't give back that code.
>>>>>>>>>
>>>>>>>>>Good additional point.
>>>>>>>>
>>>>>>>>Give back what code?
>>>>>>>>
>>>>>>>>It would show "10" instead of "My_Constant" in the source. Is that a big security issue? Enough to not put it in a variable? It can only be done for constants, so constants are the only things that would be protected. Is that a valid security reason to use DEFINE?
>>>>>>>
>>>>>>>You got it wrong. When your source code is Re-foxed, the constants will remain as is (I'm guessing), e.g. you would not get your code as it was written originally with #DEFINE.
>>>>>>>
>>>>>>>That was Denis point, as I understood it.
>>>>>>
>>>>>>What part did I get wrong? That only the constants are protected?
>>>>>__
>>>>>
>>>>>Oh, it's getting in slowly ...
>>>>
>>>>I didn't get that. Are you trying to be clever? How is all the source protected if I use one DEFINE?
>>>__
>>>Jay,
>>>
>>>What I'm getting is the impression that you don't even read what others post.
>>>You immediately respond that you do not agree
>>
>>That's bull. I read all the posts and asked what it meant. Jump off the high horse you seem to be on.
>
>correction. You cannot read posts of those you put on your twit filter <g>

Sure I can. That's the beauty of it. I can read through responses and read if I choose to. But normally, I don't' have to see the name or hear their drivel if I don't want to.