No need to export the layer. One potential solution would be creating a temporary Formula Field using this expression
If NAME = "__" then "" else NAME Then label on the formula field I hope this helps Armando On Tue, Feb 5, 2013 at 2:27 PM, David <[email protected]>wrote: > ** > > > I've always used Multiple Fields Labels - using [NAME] and [ALTERNATE > NAME] fields for the ccStreet.cdf layer. (I can't use the Navteq streets > because they don't align well with Census Blocks.) > > The labels look like this: > > Main St > US Hwy 1 > ___________ > > The problem I'm having is that, when a street doesn't have anything in the > [Alternate Name] field, Maptitude 2013 displays two dashes for the > [Alternate Name] field like this: > > Oak St > _ _ > _____________ > > ...which puts the street name far from the street line. > > When a street has no name, each segment is labeled like this: > > _ _ > _ _ > _____________ > > ...which increases clutter dramatically. > > Does anyone have any ideas for supressing the dashes? > > If I remember correctly, previous Maptitude versions didn't show the > dashes and would collapse into a null [ALTERNATE NAME] field. > > One temporary solution that I have found is this: > > Export ccStreet.cdf for the map area to a .dbd file. > > Add a field called NamePlusAltName. > > For streets with no alternate name, fill the field with the [LABEL] field. > > For streets with alterate names, fill the field with the formula: LABEL + > " / " + Proper([ALTERNATE NAME]). > > That works fine but it is a lot of extra steps for every mapping project. > If I could process the entire street database, that would work but but it > bombed out at 36% with dberr 909 and dberr 19 (I'm guessing a file size or > record limitation). I may try again by breaking up the files but would be > very receptive to alternative ideas. > > > -- Armando Scalise
