Joe, many thanks !! The problem was indeed the appearance condition set to max 6 caracters. I now have placed two fields called "call" on top of eachother.
one set for max 6 caracters with font size 16 one set for more than 6 caracters with font size 12 All my cards are printed fine !! Thanks a lot. Phil ON4VP (now trying to understand 'layers') ----- Original Message ----- From: "Joe Glockner" <[EMAIL PROTECTED]> To: "ON4VP" <[EMAIL PROTECTED]> Sent: Monday, December 30, 2002 12:27 PM Subject: Re: [DXBase] label designer, call won't print > Good morning Phil! > > Well, it doesn't matter at all which one is on top or on the > bottom.. The reason for this is that the APPEARANCE CONDITION > code that you put in "for each CALL field textbox" will decide > "which one is to be used - and when". > > The Appearance Condition for the CALL textbox that is for > a callsign with "more than 6 characters" is: > > Len(CALL)>6 > > > and > > > The Appearance Condition for the CALL Textbox that is for > a callsign with "less than 7 characters" is: > > Len(CALL)<7 > > > > Phil, I am sitting here at the computer and am on-line - so if you > want to pick my brain - go ahead and ask me! > > 73 de Joe WA6AXE > > > > ON4VP wrote: > > > > Yes Joe, > > > > I think you solved my problem. > > I copied a field to a new design and the appearance condition was set to max > > 6 caracter due to the font size being big (like 16). > > > > Thanks for pointing this out. > > I'm in the running now and will follow your lead. > > > > I will make two 'call' fields on top of eachother, one with small printing > > (for long callsigns) and one for regular 6 caracter callsigns with bigger > > text size. > > > > 1) which one has to sit on top of the other ? > > 2) can you send me the exact syntax for both fields to put into conditions > > variable > > > > Joe, many thanks and happy newyear > > > > Phil ON4VP > > > > ----- Original Message ----- > > From: "Joe Glockner" <[EMAIL PROTECTED]> > > To: "Phil ON4VP" <[EMAIL PROTECTED]> > > Cc: <[email protected]> > > Sent: Monday, December 30, 2002 12:37 AM > > Subject: Re: [DXBase] label designer, call won't print > > > > > Phil, > > > > > > If, by chance, you "copied" one of the files that uses > > > "Appearance Conditions" - that would answer the problem.. > > > > > > I myself have made many labels/QSL cards that use "TWO" CALL > > > fields (on top of each other) .. The one CALL field is used > > > for Callsigns that are "LESS than 7 characters" and uses the > > > FONT size of 12 .. the other CALL field is for Callsigns that > > > are "GREATER than 6 characters" and uses a FONT size of 10.. > > > > > > This way I could let the program make the decision as to which > > > CALL FIELD to USE ... The "conditional coding" for these two > > > CALL fields can be found by: > > > > > > (1) Left-click on the one CALL field and then Right-click on > > > that CALL field -- when the menu comes up - choose > > > > > > Appearance Condition > > > > > > > > > In that you will see something like: > > > > > > Len(CALL)>6 > > > > > > > > > ..... NOW ... > > > > > > If you DO NOT want the selection of TWO Different CALL text boxes, > > > just DELETE one of them and then REMOVE the "Appearance Condition" > > > from that remaining CALL Text Box.. > > > > > > > > > I hope that his helps Phil! > > > > > > 73 de Joe wa6axe > > > > > > Phil ON4VP wrote: > > > > > > > > Jack, > > > > > > > > I've tested more : when I even make the label field for the stations > > call > > > > VERY BIG and place the field very distant from any other fields, the > > call is > > > > not printed on the card from the moment it is more then 6 caracters. > > > > > > > > WA6DER is printed, WA6DER/P not ... > > > > > > > > Any ideas > > > > > > > > ----- Original Message ----- > > > > From: "Jack" <[EMAIL PROTECTED]> > > > > To: "Phil ON4VP" <[EMAIL PROTECTED]>; <[email protected]> > > > > Sent: Sunday, December 29, 2002 6:05 PM > > > > Subject: Re: [DXBase] label designer, call won't print > > > > > > > > > Phil, > > > > > > > > > > When placing QSO field variables on the card design, there were a > > couple > > > > > choices. One was to use the callsign from user options. This would > > > > result > > > > > in only one callsign ever showing up on the card for your callsign. > > The > > > > > other method is to use the OprCall variable. In this case, whatever > > > > > callsign was in the Operator callsign field for each QSO would be the > > one > > > > > that shows up on the card. > > > > > > > > > > Hope this helps, > > > > > Jack > > > > > > > > > > ----- Original Message ----- > > > > > From: "Phil ON4VP" <[EMAIL PROTECTED]> > > > > > To: <[email protected]> > > > > > Sent: Sunday, December 29, 2002 11:47 AM > > > > > Subject: [DXBase] label designer, call won't print > > > > > > > > > > > > > > > Hi, > > > > > > > > > > I made some nice looking cards and all prints out qiet nice but with a > > > > > regular callsign in the 'call' field. > > > > > > > > > > but ... > > > > > > > > > > when I have a call with another prefix like PA/W4RT or KP4/N3EE or > > > > > when I have a special suffix like W5ER/M or KB2ERT/QRP or AA7YY/P > > > > > > > > > > the callsign is not printed on the cards. > > > > > > > > > > I've checked and I'm almost shure that the fields are wide enough to > > cover > > > > > all letters in the field. > > > > > What could be going wrong ? > > > > > > > > > > Phil ON4VP > > > > > > > > > > > > > > > --- StripMime Report -- processed MIME parts --- > > > > > multipart/alternative > > > > > text/plain (text body -- kept) > > > > > text/html > > > > > The reason this message is shown is because the post was in HTML > > > > > or had an attachment. Attachments are not allowed. > > > > > Please post in Plain-Text only.--- > > > > > _______________________________________________ > > > > > DXBase Reflector - Please visit us on the web at www.dxbase.com > > > > > - - - - - - - - - - - - - - - - - - - - - - - > > > > > To UNSUBSCRIBE please visit: > > > > > http://mailman.qth.net/mailman/listinfo/dxbase > > > > > > > > > > > > > > > _______________________________________________ > > > > > DXBase Reflector - Please visit us on the web at www.dxbase.com > > > > > - - - - - - - - - - - - - - - - - - - - - - - > > > > > To UNSUBSCRIBE please visit: > > > > > http://mailman.qth.net/mailman/listinfo/dxbase > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > DXBase Reflector - Please visit us on the web at www.dxbase.com > > > > - - - - - - - - - - - - - - - - - - - - - - - > > > > To UNSUBSCRIBE please visit: > > > > http://mailman.qth.net/mailman/listinfo/dxbase > > > > > > >
