on 3/4/03 3:44 AM, Jesse Guardiani <[EMAIL PROTECTED]> wrote: > Not sure where you're going with this. A '*' in the third field is not a > wildcard. It's a modifier. An '*' in the first or second > field will ALWAYS be treated as a wildcard as long as you're using the > wildcard modifier. There's nothing confusing about that.
I think I figured out where the confusion came from. You've already mentioned it, and in fact I think we visited this same point a week ago - but in all the confusion I forgot. You may be right about the reason for still keeping the @ modifier, but that aside I was trying to figure out how it could really be possible that @ and * would do the same thing IN YOUR CODE, which I finally realized was what you were probably really saying. This all comes back to the fact that wildcards can not be used with records that could list in the popup. (Last time we visited this issue I pointed out this was one possible reason to keep the separate domainmap file, although again I am not really dissappointed.) And because of that, * and @ are basically the same. Now that all that confusion is aside, I think I also figured out what the * modifier really means since it does not really mean just "enable wildcard", because there are exceptions to that. It means suppress the popup list! There are no exceptions to that. As a side-effect when the popup list is supressed is the only situation in which modifiers can be supported. Just those thoughts for now. Since this puts everything else in such a different perspective for me, I think it means I will be far less confused now. More later. I have to install your latest yet again! I tend to make at least one mistake every time, but it is getting easier. -Kurt
