LOGic Tips and Tricks
Table of Contents:
Page 1 DXCC Millennium Award - How to Fix Awards Search for DXCC Millennium Award
Page 2 Adding and Tracking 10-10# by State
Page 3 QSL Received Report Printing Problem
Page 3 LOGic Filtering Issue
Page 3 Select criteria -To search QSLs received between two dates
Page 3 Log Filtering solved - To show all cards checked-in during a particular period
Page 4 More on How to Add Filter Selection
Page 5 Exporting QSOs with certain Date Ranges into ADIF file
Page 6 Log Sort
Page 6 Log Sort - another method
Page 6 LOGic Label Format Change
Page 7 Sorting via QSL manager
Page 8 Replace CONTEST_ID for date range
Page 9 Replace CONTEST_ID for date range - instructions followed by comments
Page 10 IARU Contest Setup
Page 11, 12 ARRL Contest Submissions and Contest Setup
Page 13 HF spots only in Spot Log
Page 13, 14 Spot Processing Help
Page 15 Spot Log Filter
Page 16 How to Clear an Entry in Spot Log
Page 17 Multiple Log Setup
Page 18 Labels that print Contest ID
Page 19 What is QSL RCVD2 in 5.2.57?
Page 20, 21 Indexing user-defined fields
Page 22 Pacific Lat's & Long's
Page 23 VIA field and QSL Route
Page 24 Modify Multiple QSOs per Label 3-Across
Page 25 ARRL VUCC Award Tracking
Page 26 Printing Just One QSL Card per sheet
Page 27, 28 Questions Contestors using LOGic5
Page 29 Solution to Cards Needed
Page 30 How to Handle Paper Jams
Page 31 Adding a Field to a Report
Page 32 Printing Forms - How to Print Radio Memories
Page 33 How to Add Filter Selection
Page 34-43 Filter selection and Understanding of USERFIELDS
Page 44-46 Updating Userfield Process - Solved
Page 47 Printing the Prefix Table
Page 48-50 Dates in Logic
Page 51 Adding New Canadian Prefix
Page 52 How to Check Log for Empty State and Zone Information
Page 53 Two Operators With Logic 5
Page 54 How to Filter on Userfields
Page 55 Cabrillo 10M contest PROBLEM
Page 56 Digipan & Logic - How to Log a QSO into Logic from Digipan
Page 57 Map Position
Page 58 How the INFO Window Works
Page 59 DXCC Submission Report
Page 60,61 DXCC Submission Report … Other Methods
Page 62 How to Reset Contest Scoring
Page 63 Utility to Import 1010 Database
Page 64 Printing Unworked DXCC Countries
Page 65 How to add new DXCC - Ducie Island
Page 66 Improved way of sending serial numbers in CW
Page 67 Cabrillo Export
Page 68 How to Edit the TelNet and WebCluster Drop Down Menus
Page 69 How to Print Slashed Zero Ø Font
Page 70 Modifying a Userfield Value
Page 71 How to turn the Rig Control Window On or Off
Page 72 How to Change Comment Field Size in Lists Table
Page 73 Filtering Using Date/Time
Page 74 How to Clear Error in Logic 6.0
Page 75 How to Resize the Mode Field
Page 76 How to Reset Contest Score Window
Page 77 How to Manage Log Forms
Page 78 Printing Labels
Page 79 DXCC Spots Configuration
Page 80 Widening "DESCR" in spot log
Page 1 - Subj: DXCC Millennium Award - How to Fix Awards Search for DXCC Millennium Award
From: [email protected] (George E. Vincent - George K3GV)
1. Go to Tools - Setup - Log Fields, Spotting, and Awards Tracking
2. Search for DXCC
3. Go to Awards Tracking
4. Add Sub Award, Description - Y2K
5. Add Sub Award Select Criteria - YEAR(QSO_DATE)=2000
6. Exit and Update Awards Progress Info
The new DXCC Millennium Award can now be tracked as a sub award category of DXCC and a printout can be made by Band Mode to attach to the DXCC Millennium Award Application. The printout will only show QSOs made in the year 2000 and when you hit 100, print it out attach it to the application and THAT'S ALL THERE IS TO IT.
Page 2 - Subj: Adding and Tracking 10-10# and State?
From: [email protected] (Anthony A Boykin - Tony WB2JRI)
I got mine to work after pick up on a tip from Frank W2FCA. Frank's Tip was Make the Sub-award for 1010{WAS} under "STATE" not under 1010#' that was key. Putting it under 1010# and the Progress screen will give you back different data. When you do the Awards progress it will tale all 10-10# worked for each state and not one number per 50 states.
Here are the steps to make the Sub-award for 10-10 {WAS}
1. Click Tools setup Click 'Log_fields Spotting Award Tracking'
2. Do a GET for 'STATE'
3. Under "Awards Tracking & Spotting" For Description 1010#
4. For 'Select Criteria= '1010#'$USERFIELDS <== note the two single quote marks one a beginning and before the dollar sign, you can use the expression builder to validate. You can "cut & copy" the command from the email right into the Sub award, make shore no extra space when you do the "cut".
5. Save and do a 'Awards update', and your done. Look at the Progress 1 or 2 [sel] states you see the new sub-award for {1010# - WAS}. Also look at Awards Progress List it listed there also. If you run the Award.rep report be shore to include "1010# " in the extra fields you want reported. This should print one number with the call worked.
One last point how I finger out commands is to use the filter and open the "EDIT" to see what LOGic does for commands, do a Cut & Copy into what ever I am trying to do most times into the "Expression Builder" and do a 'Verify' to validate the excretion. If I don't get a syntax or missing ")" and Valid Expression {Look at Bottom-Left of your screen it flashes}.
The other thing I do is to make a Text file of these commands with short explanation of what they do and save is as "DB COMMANDS.txt" and do a 'Copy & Paste' when I need them. You be surprised how often you use the same commands in Reports, QSL Cards etc.
Page 3 - Subj: QSL Received Report Printing Problem
From: [email protected] (Dave Jacques - Dave K5DV)
One easy way to do it is to go into your log report. Click on filter icon.
Scroll down to QSL Rcvd and place an f in the value column. Continue down to
Userfields, select contains (The $ symbol) and enter the userfield:value|
For example your query should be entered
Qsl Rcvd f
Userfields $ qslrdate: 20000610|
The delimiter at the end of the date is the pipe or vertical line. Usually obtained with Shift Back Slash.
Page 3 (continued) - Subj: LOGic Filtering Issue
From: [email protected] (Arthur Tan - Art AB4RL)
To filter by a particular date. For instance to show all cards checked-in on a particular date (today for instance) go to Filter--Select USERFIELDS$QSLRDATE:20000619|
Page 3 (continued) - Subj: Select criteria - To search QSLs received between two dates
From: [email protected] (PDA - Dennis WN4AZY)
BETWEEN(TAG_VAL("QSLRDATE:", USERFIELDS), "20000701", "20000731")
Page 3 (continued) - Subj: Log Filtering Solved -To show all cards checked-in during a particular period
From: [email protected] (George E. Vincent - George K3GV)
To show all cards checked-in during a particular period
1. Go to print log.rep
2. In user-selectable field specify QSLRDATE:
(do not forget the colon) this will print the date the QSL was received on
the report
3. Under run report options in specify criteria enter
BETWEEN(TAG_VAL("QSLRDATE:", USERFIELDS), "20000601", "20000630")
Page 4 - Subj: More on How to Add Filter Selection?
From: [email protected] (Arthur Tan - Art AB4RL)
The idea is that every label I want to print on a given run will have a specific date in that field?
But when I try to filter that using Filter - Edit - ML-DATE='09/9/00' it doesn't work. Seems Logic5 doesn't accept the "ML-DATE" as a keyword.
Go to Filter then go down to USERFIELDS. In the OPERATOR field select "$" (contains). In the VALUE field type ML-DATE:20000909| (note the last character is "pipe" or Shift-Backslash and that the date must be in the YEARMMDD format). The standard rules of "date-searching" i.e. using curly brackets instead of parenthesis, etc. do not apply here (whereas they do apply to Filtering by QSO DATE).
The above example will only show QSOs with one specific ML-DATE, e.g. Setpember 9, 2000. To show a range of QSOs, e.g. from September 9, 2000 to September 12, 2000 you would do the following
Go to Filter and click on the Edit button. (Here's where it gets tricky...) You need to type in a long expression:
BETWEEN(TAG_VAL("ML-DATE:", USERFIELDS), "20000909", "20000912")
Unfortunately, you cannot create this expression from the drop-down menu selections directly and therefore you have to type it in manually. However, this does work pretty well to get a valid QSOs over a range of dates.
The LOGic Filtering facility is pretty powerful.
Page 5 - Subj: Exporting QSOs with Certain Date Ranges into ADIF File
From: [email protected] (Rob Kennedy - Rob VA2FB)
How to export QSOs made on certain dates from Logic 5 to an ADIF file.
For example, if you want to export all the QSOs made during the ARRL SSB contest (on March 5 and 6, 2000) from Logic 5 to an ADIF file, you do the following:
1. Select TOOLS -- EXPORT -- ADIF.
2. In the criteria box, type
LOG.QSO_DATE={00/03/04} OR LOG.QSO_DATE={00/03/05}
All the QSOs on March 4 and March 5 will be exported to an ADIF file. (Use OR not AND in the expression above!)
You can construct more complicated expressions using the expression builder -- Just click on the box with the two little dots on the right.
(E.G. You can export only QSOs with people with the name of "Rob" made on
March 4, 2000 etc).
Page 6 - Subj: Log Sort
From: [email protected] (C.M. Christensen - Chris ACØM)
To print a log report for just the information you want.
1. Got to file/print/log and then hit open
2. When the next screen comes up put VIA in the top field and skip the rest
3. The next screen is labeled Select Order
4. Choose CALL and hit ok
5. The next screen is called -- Run Report Options -- LOG
6. In the Select Criteria field type the following: QSL_RCVD="R"
7. Choose either screen or printer depending on where you want it to go.
This will give you every outstanding card that you have marked with and R for requested on the log screen. It will also print on the far right hand side of the sheet the information that is in your VIA field which contains the QSL route. You then know exactly what cards you have outstanding and who you sent the card to for verification.
Page 6 (continued) - Subj: Log Sort - Another Method
From: [email protected] (Frank Ayers - Frank W2FCA)
Try this:
1. Go to tools - advanced - index
2. Click on the plus to add
3. Enter "log" in the file box
4. Enter VIA for the name for the index in the index tag box
5. Have index type as normal
6. In the index expression type LOG.VIA
7. Click on the disk (for update and flush)
8. Do the reindex and pack thing.
Page 6 (continued) - Subj: LOGic Label format change
From: [email protected] (Anthony A Boykin - Tony WB2JRI)
Add the command in the label under the call
"Qsl Via " + trim(via)" and it will print 'Qsl Via UX0UN' under the call "UT5UDX" in the call sign field or any other call.
Page 7 - Subj: Sorting via QSL Manager
From: [email protected] (Arthur Tan - Art AB4RL)
This is courtesy of W2FCA. It works for me. Let me know if I can help.
1. Go to tools - advanced - index
2. Click on the plus to add
3. Enter "log" in the file box
4. Enter "VIA" (no quotes) for the index in the index tag box
5. Have index type as normal
6. In the index expression type "LOG.VIA" (again, no quotes)
7. Click on the disk (for update and flush)
8. Do a reindex, pack, and sort
Page 8 - Subj: Replace CONTEST_ID for Date Range
From: [email protected] (PDA - Dennis WN4AZY)
MAKE A BACKUP!!!
In tools/advanced\database commands.
Type
USE LOG
Then go to database files/mass change
REPLACE
contest_id
WITH
"ARRL DX"
Replace only if
QSO_DATE={^2000/3/20} AND QSO_DATE<={^2000/3/25}
Page 9 - Subj: Replace CONTEST_ID for Date Range - Instructions followed by comments
From: ?
OK Here are the instructions followed by comments:
1. MAKE A BACKUP!!!
a must in case you screw up
2. Go to tools/advanced/database commands.
select in order from top of window bar
3.Type USE LOG
when window opens in "Command window" type USE LOG followed by enter
you will then see on bottom of window Record:1/5296 (or however many QSOs you have in your log)
4. Then go to database files/mass change
select in order from top of window bar
5. REPLACE contest_id
In the "Replace this field" window choose the item you wish to replace from the drop down selection (in this case choose "contest_id"
6. WITH "ARRL DX"
in the "With Window" type the name of the contest WITH QUOTES, i.e. "ARRL DX SSB 2000" followed by ENTER
7. Replace only if QSO_DATE={^2000/3/20} AND QSO_DATE<={^2000/3/25}
In the "Replace only if window" type QSO_DATE={03/05/2000} AND QSO_DATE<={03/06/2000}
Here is what I found a this point DO NOT type the ^ before the date as Dennis did and use the date format which you use, i.e. ddmmyyyy or mmddyyyy or yyyymmdd you get the picture and make sure to use the proper bracket style (the upper case bracket next to the letter "P" on the keyboard. You can also type QSO_DATE={03/05/2000} if you don't need a range.
Then select the funny button that represents # to see how many records are to be changed. When you are satisfied select OK.
I suggest you pick a small range of files to experiment with at first. If you screw up you can deselect by specifying the contest_id description as "" (2 sets of quotes with nothing in between) it the clears the field in the records if you made an error. I was able to change all my records once I figured out about the ^ and always follow commands with enter (although I should have known that).
Page 10 - Subj: IARU Contest Setup
From: [email protected] (Arthur Tan - Art AB4RL)
1. Go to Tools--Setup--Log fields
2. Click "+" (or hit "n") to add a new field
Call it IARU MS (character, width: 10, put whatever you want in the description boxes, IARU MS stands for member society)
3. Click OK to save
4. Reopen Forms--Log--IARU contest form
Page 11, 12 - Subj: ARRL Contest Submissions and Contest Setup
From: [email protected] (Rob Kennedy - Rob VA2FB)
Well, it is pretty easy to set up the ARRL DX contests.
1. First bring up the LOG screen for the ARRL DX contest (From FORMS -- LOG). Then Click on LOG -- SETUP. At the LOG setup screen, go to the CONTEST tab. Make sure that the dates of the CONTEST are entered properly! THIS IS VERY IMPORTANT!
Also make sure that the QSO POINTS and MULTIPLIERS are setup correctly. If you are entering the ALL band category, you probably won't have to do anything. If you want to enter the SINGLE BAND category, you will have to change BOTH the QSO POINTS and MULTIPLIERS. For 10 Meter BAND (Single Band category), edit as follows:
QSO POINTS:
Default Score : 0
Expression: NOT (DXCC="K " OR DXCC="VE ") AND BAND="10M"
Points: 3
MULTIPLIERS:
Field: DXCC
Expression: IIF ((DXCC="K " OR DXCC="VE ") OR BAND<"10M","", DXCC)
Value: 1
Description: COUNTRY
MAX: 999999.00
2. Then Exit the setup screen.
3. Then run RESCORE CONTEST from TOOLS -- MISC UTILITIES. Select the ARRL DX LOGFORM.
To create the .LOG file for EMAIL submission -- Go to TOOLS -- EXPORT --ARRL CONTEST. You will be asked to enter another field -- just hit ENTER.
Save the file as (your call.LOG) -- e.g. VA2FB.LOG
You will also need to manually create a summary file in ASCII format called your call.SUM (e.g. VA2FB.SUM). For the format of this file go to the ARRL web site. The format for the summary file is not fixed in stone -- just use it as a guide. Since you will be EMAILING the .LOG and .SUM files to the ARRL, you do NOT need to sign the summary form. (I just got confirmation from the ARRL that electronic submissions are considered signed). EMAIL the .LOG file created by Logic and the .SUM file created manually to ARRL at the EMAIL address given on their web site for the particular contest! (There are different EMAIL addresses for each ARRL contest).
Page 13 - Subj: HF Spots Only
From: [email protected] (PDA - Dennis WN4AZY)
http://oh2aq.kolumbus.com/dxs/hfdx25.html
Page 13, 14 - Subj: Spot Processing Help
From: [email protected] (Peter Wetzig - Peter VK4IU)
Question: How can I prevent 6M spots from showing in Spot Log?
In my Bands table, I have NO entries in any of the blocks (for ex. where you can type 1234) for spot announcements for tracking awards. So I am not asking to track 6M.
In my Web Cluster spotting window, I have "Process all spots" cleared (also tried with this selected).
In Spot Log filter, I can filter WHAT I want, but don't seem to be able to filter what I DON'T want.
Answer: The Logic WebCluster window works by reading a file on the OH2AQ web cluster and then "parsing" it into spots for your log. If you go to
www.dxsummit.com or http://oh2aq.kolumbus.com/dxs
... both end up at the same place ...
... point at the links on the left hand side of the page and watch the bottom status line of our browser window. You should see all the file name links for each of the spot categories. They go like this ...
oh2aq.kolumbus.com/dxs/7.html for 40 meter spots
... /10.html for 30 meter spots
... /14.html for 20 meter spots
etc etc ... just follow the theme.
Some special ones are ...
oh2aq.kolumbus.com/dxs/iota.html for islands only or
oh2aq.kolumbus.com/dxs/hfdx25.html for HF DX - without 50 meters - 25 at a time.
oh2aq.kolumbus.com/dxs/client.txt the one used by DXTELNET DXplorer, spots, announcements, WWV all in one place
By default Logic brings down the most common file to suit the largest range of amateurs using Logic - .../dx25.html which includes 50 meters in the definition of DX.
When you open the Webcluster DX Summit spotting window, click on Edit and change the reference to one of the above. After you have made one or two links, the little triangle to the right can be used to "drop down" a list of the ones you have used in the past - just reuse them, by selecting and pressing enter.
What I do is ....
In Logic, update the Band table (Tools/Setup/Bands) to include all the bands and modes for which I want spots. Then I change the address in the WebCluster DX Summit or WebCluster Juliet Alpha windows to limit the spots to what I want to work tonight - 15 meters tonight (.../21.html), 20 meters tomorrow (.../14.html), the lot next week (.../hfdx25.html)
There is NO difference between the Webcluster windows - apart from the address to which they link to get the data - use either one, or both at the same time. Just remember that files like 21.html and 14.html are included in hfdx25.html. Logic will filter duplicates for you - but why waste the bandwidth.
Page 15 - Subj: Spot Log Filter
From: [email protected] (Bill - K1UQ)
Use the Spot Log filter to filter and display only what
you want ... Phone, CW, RTTY for example filter on CW, and only CW spots show up in
the Spot Log window
From: [email protected] (Peter Wetzig)
If you point at the text box, a pop up help line says ... "Search call, descr, value...". It seems to work on the basis that the whole spot line is a simple piece of text. Filter/searching something like "CW" will show any line of Mode CW and could show "VK4CW 20m Phone" as well.
Using the search/filter for CW surely does show only those lines with "CW" somewhere in the line. But ...
I just did some experiments to see if putting CW in the filter/search will prevent PHONE spots from being announced by the "woman's voice" inside the Logic spot log. It didn't - I got Phone spots announced as well as CW spots. The "filter" only works AFTER the spots have been placed to the spot log. I would see it as a "search" device rather than a "filter", in the context of the spot log, despite the use of the "filter" button image.
So, I would still do the filtering using the address on DXSummit. If I used .../digital.html ONLY digital spots would come down from the web, only they would be announced, and I would not have to change the Logic band table from session to session on the air. I could "home brew" my QRP rigs at the other end of my shack and have Logic announce any DX that may happen along while my back was turned.
Page 16 - Subj: How to Clear an Entry in Spot Log
From: [email protected] (Carl Smidt - Carl VE9OV)
Question: Some how I received a spot the other evening for 9v1yc that's
dated 11/15/00. Since the date is in the future, the spot will not
clear out. How can I delete the spot out of the spot log. If I highlight the call
and hit the delete key it says that its a read only window, which makes
sense.
Answer: This happens all the time and is very irritating, don't know if it is the server on the initiating party's side or what, but the clocks should be set correctly. Just go to options in spot log and erase it all, using the eraser icon, that should hopefully fix it.
From: [email protected] (Frank Ayers - Frank W2FCA)
You might want to make a backup of the spots log first.
Go to tools/advanced/database commands
Click open, then go to logdata, and open spots.
Type in delete for call = "9V1YC" hit enter
I just tried it on one of mine and it works.
From: [email protected] (Arthur Tan - ART AB4RL)
You can use Tools-Advanced->Database commands but you gotta careful any
time you go there!
1. Type: use spots
2. Type: delete for SPOTS.CALL="9V1YC" (this part is case-sensitive; at
the very least SPOTS.CALL="9V1YC" must be in CAPS)
3. Type: close tables all
You're done. However, note that this will clear out ALL entries for 9V1YC
in your Spot Log database, not just the one dated 11/15/00
Page 17 - Subj: Multiple Log Setup - Separate Logs
From: [email protected] (George E. Vincent - George K3GV)
1. In Windows 95/98 Open My Computer
2. Find and Copy Logdata folder
3. Paste copy of Logdata Folder in main Logic 5 folder
4. You now have a "Copy of Logdata" folder inside Logic 5 folder
5. Rename "Copy of Logdata" folder with new callsign (or whatever name you choose) - my folder is named NNNØEKE which is my MARS callsign
6. Next create a shortcut to logic.exe file on the desktop (drag file from Logic 5 folder to desktop)
7. Rename the Shortcut to anything you like to differentiate it from your main Logic 5 icon
8. Right click on Shortcut and select properties
9. In the Target Window "C:\Program Files\LOGic 5\logic.exe" appears
10. Add to this data='c:\program files\logic 5\nnn0eke'
11. Line should now read "C:\Program Files\LOGic 5\logic.exe" data='c:\program files\logic 5\nnn0eke'
12. Take note of quotes " " and ' '
13. Before proceeding further open and start your original Logic 5 program and add a QSO
14. Close your Logic 5 program
15. Open and start the new shortcut that you created
16. You should not see the new QSO that was added in the original Logic 5 program (this is a safeguard to let you know that you are working with two separate folders)
17. When you are satisfied that everything is working as it should you can
18. Select Tools Miscellaneous utilities Zap log
19. This will clear all entries associated with the old log in the new program
20. You can then setup the new log and fields for the new callsign
· I have used nnn0eke which is my MARS callsign as an example (use whatever callsign you wish to have a log for) - you will need to create a new shortcut for each callsign. This procedure allows sharing of all other Logic files and permits awards tracking for the additional callsigns. This information is intended only to supplement the information regarding Multiple Databases in the HELP file.
· ALWAYS MAKE A BACKUP !!! a must in case you screw up.
Page 18 - Subj: "Labels that Print Contest ID" AVERY - 5260
From: [email protected] (Anthony A Boykin - Tony WB2JRI)
How could I add the contest information to the Label Format "Multiple QSL Labels, 3 QSO per Label 3 Across.rep"
I noticed that the expression that you used was trim(Contest_is)+"Contest" Is all that is necessary is to add this statement to an existing format? How would I get the question to come up to ask what contest information I want to add?
Just add the Contest_id statement to the label you want. You don't need brackets () just contest_Id
The +"Contest" at the end makes it print the word Contest.
You don't need it I added it for looks so 1010_97 would say 1010_97 contest.
How would I get the question to come up to ask what contest information
I want to add?
The easy way George is to do a filter in the report. click the
"Range"button and were it has "Contest_Id" put in what you want. Now When you go to
print labels It only going to print labels from that contest. Another tip for
Contest names use a date at the end like: "1010_00 or CQWW_99. So when you use the range it easy to put in a name and date.
To do a special report for contest labels would require statement be add to the "before Run Report". So when you first run it would ask you what you want. That out of my range at this time.
Page 19 - Subj: What is QSL RCVD2 in 5.2.57?
From: [email protected] (Arthur Tan - Art AB4RL)
Arthur Tan wrote:
I was running a few reports with the new version of LOGic. Specifically when you run a report (let's say CARDS NEEDED FOR AWARD for instance) and you finally get to the "Run Report Options" (the last screen that gives you the filter options, print to printer, print to screen, etc) and you hit the filter button to do some last minute filters you see an entry called QSL RCVD2. What is that for? That box does not show up in the regular Filter choices in the Logform.
This is created in a temporary file created by the SQL in the report extract. It contains a copy of QSL_RCVD, except that it can contain S for "Submitted" for the award in question.
Actually along those same lines, what is QSO Date T (listed right under QSO Date) in the Logform Filter screen?
It contains a numeric value that represents the date and time. A timestamp in other words. It is used internally to make it easy to see how much time elapsed between two QSOs, making it easy put QSOs in chronological order, etc.
Tnx & 73, Dennis WN4AZY
Page 20, 21 - Subj: Indexing User-defined Fields?
From: [email protected] (PDA - Dennis WN4AZY)
my mistake. You need to make sure the key is always the same length. Use PADR to pad the right with spaces.
PADR(TAG_VAL("IOTA:",USERFIELDS, "C"), 6)
See notes below.
I'll fix the web page.
Tnx & 73, Dennis WN4AZY
On 14 Aug 00, at 13:14, [email protected] wrote:
Dennis, I have followed the instructions for indexing a user defined field and cannot seem to get it to work. I am trying to index the IOTA column. I double clicked on the column in the browse window as instructed and received the following information:
Name: user8
Expression: tag_val('iota:',userfields,'c')
Ok, should be upper case, but I think that's all it will take...
I used this information in index setup, however, I was not sure which File to select so I have tried LOG, LOGFIELDS and LISTS.
You want Log. That is the file that has your IOTA contacts in it.
Also, the expression received when I double click uses single quote ( ' ) and the example on the Advanced topics webpage uses double quote ( " ). I have tried it both ways.
They are interchangeable so long as they are used in pairs. See Expressions in the help.
Depending upon the file tag that I use I receive deferent a message during REINDEX, such as "invalid key length" or program error "value userfields not found" depending upon which File I choose during Index Setup. I also do not understand what the letter C means in the expression.
Character.
The bottom line is no matter what I have tried I am not able to create the index that I want for the IOTA column. Any suggestions?
On the Advanced topics web page it says to See the TAG_VAL() function documentation in Help. I have not been able to find this documentation.
It's in the section on Expressions and Functions.
Page 22 - Subj: Pacific Lat's & Long's
From: [email protected] (Carl Smidt - Carl VE9OV)
George, any longitude west of the Greenwich 0.0 degree meridian, through the US to 180 degrees (in the Pacific) is negative. Any longitude east of the Greenwich 0.0 degree meridian, through Russia & China, to 180 degrees (in the Pacific) is positive. The Marianas are west of the 180 degree meridian, (east of the 0.0 degree meridian) hence positive. Johston Island, for example, is east of the 180 degree meridian (west of the 0.0 degree meridian) hence has a negative longitude. I haven't checked very many prefixes, but there are probably several mistakes.
I just happened to find Johnston Island because it was close to the Marianas, loosely speaking from a prefix point of view, when I went looking this AM. It was positive, but should be negative, so I changed it. There are so many little islands out there in the Pacific, loosely scattered around the 180 degree meridian, that it really makes very little difference to us here in NA, bearing wise, whether the longitude is negative or positive. If you are
in Australia it's an entirely different story.
Page 23 - Subj: VIA Field and QSL Route
From: [email protected] (Carl Smidt - Carl VE9OV)
Copying info from the 'QSL Route' to the 'Address' area. Click 'Log' then click 'QSL Route', if the address is there, then go up to the top bar of the log screen
and click on 'QSL Routes' and then 'Copy address to Log'. If you only want
to copy the 'VIA' call sign (if there is any) to your log, then click 'Copy
Via to Log' and the 'Via' call sign is automatically placed in the 'Via'
field of the log. Normally, I only place the 'Via' call sign in the 'Via' block for Bureau
cards. For Direct, I copy the Via address to the 'Address' portion of the
log by the top procedure above, so it will print on the envelope that I send
out.
'Go To Via' is only used to go to the address for the Via call sign
(if there is one). Not to copy to Log!! To copy to Log, you hit 'QSL Routes'
on the top bar and THEN click, 'Copy to Via'.
Page 24 - Subj: Multiple QSOs per Label
From: [email protected] (PDA) (Dennis - WN4AZY)
How do you modify the Multiple QSO label 3 QSOs per label 3 Across to add an additional QSO and make it a 4 QSO per label format?
To make it print 4 or 5 QSOs, change this line in BEFORE RUN:
lblmult(global.report_ref.selectexp, 3)
Change it to either:
lblmult(global.report_ref.selectexp, 4)
or
lblmult(global.report_ref.selectexp, 5)
The comment says it only supports 4 QSOs, but that is incorrect I think it supports 5.
Make your rows 4 and 5 by copying ROW 3.
Note that the expressions for the fields are
day(qso_date3)
left(cmonth(qso_date3),3)
right(trans(year(qso_date3),"####"),2)
left(time_on3,4)
band3
mode3
rst_sent3
Change the field names ending with 3 to 4 and 5 respectively. For example:
day(qso_date4)
left(cmonth(qso_date4),3)
right(trans(year(qso_date4),"####"),2)
left(time_on4,4)
band4
mode4
rst_sent4
Page 25 - Subj: ARRL VUCC Award Tracking
From: [email protected] (Frank Ayers - Frank W2FCA)
Has anyone setup Logic 5 to track the ARRL VUCC Award? If so how?
Yep - you just set up an award using grid. Unlike DXCC where there are a fixed number of entities, it will add a new record in the list file for each new grid you work. You do it by going to tools\setup\fields awards tracking.
Select the grid field then select the awards tracking tab. Select the box
that says "track awards for this field". Done
Page 26 - Subj: Printing Just One QSL Card per Sheet
From: [email protected] (William Lawless - Bill K1UQ)
Some of you may be using perforated, 8.5 in x 11 in sheet card stock. This stock yields 4 cards per sheet. The standard report prints 4 cards per sheet, however if you have less than 4 to print, your entire sheet is not utilized. But it can be.
Make a second QSL card report, which consists of two cards, one above the other. Now you can print on the right half of the sheet. Once printed, tear sheet in half vertically. Or you can pre-divide the sheet into a left half & right half.
So now you can print 4 cards or 2 cards.
To print just one card, select the 2 card QSL report you just made. Only the top card of the right half prints. You can feed your printer with a "two-card-right half" or you can feed with just one card.
Now you can print 1, 2, or 4. If you need to print 3 cards, go for it, then you can print one card to use up the remaining quarter.
Page 27, 28 - Subj: 3 Questions for you Contestors using LOGic5
From: [email protected] (Arthur Tan - ART AB4RL)
1. Does LOGic 5 have a feature similar to SuperCheck Partial?
No. It does not. However, the closest thing you can do is use
Forms->Other QSOs. Keep it open while you are contesting. It's an imperfect substitute in that it will not progressively narrow down your choice of "active" contest calls but if you hit a "match" it populates the form with all your former QSOs with that station...so it kinda helps.
2. Is there a way to force a contest log to ensure (a) all required fields are in fact entered before you can ENTER the contact and (b) format of each field is filled in as it must be?
Don't know about this one but my guess is no, there is not a way to do it.
It will let you modify the data with or without verifying if the data is correct.
3. Anyone have trouble using LOGic 5 in a serial numbered contest (like Sweeps) and for one reason or another the serial numbers get out of sync, so you have to stop logging and go reset the serial start number?
Always, use Esc to clear an unwanted QSO rather than trying to go back and write-over previously entered info. Otherwise it is too easy to accidentally enter an unwanted QSO. Using Esc helps in keeping the serial numbers in line too.
From: [email protected] (William Lawless - Bill K1UQ)
BTW - - for others on this reflector who may not know - - re (1) Super Check Partial...
This is actually a feature found in several other contest logging programs which use a database of callsigns (MASTER.DAT for ex.). This partial check database should not be confused with a call sign CD database (like RAC, Buckmaster, etc). Partial Check databases comprises just those call signs frequently entered into contest logs around the world, so if you aren't an active contester, you won't wind up in this database. This adds value by limiting the database to pretty much just us active contesters.
This database is kept current by Jim Reisert AD1C (there may be others), and can be loaded into various logging programs (CT, WL, NA, etc). Once loaded into the logging program of choice, it provides a sort of look-up-table for call signs. As you begin typing a callsign, your typing is continually cross-checked against this database, with probable matches displayed on-screen. As you keep typing more and more of the call sign, fewer and fewer probable choices are displayed as the table zeros in on and displays the most probable call sign matches. This happens instantaneously, ie in real time, as you press each key of your keyboard - there is no lag. It's fast and a terrific aid when you have trouble hearing that weak signal and are getting partial call signs.
This feature can be used two ways: as Check Partial, and Super Check Partial. Here's the difference: both cross-check against this maintained database of active contester call signs, however Super Check expands its look-up by also cross-checking against your own personal log.
As for (2), I would like a way for LOGic 5 to prevent me from being able to log a contact untill all required fields have been entered. I got used to this feature in other contest programs. It ensured I complete the QSO fields before being allowed to log the entry. Conversely, in the past two Sweeps and Iota where I have used LOGic 5, I found incomplete QSOs I had "been allowed" (by LOGic 5, that is) to enter. That was disappointing to discover!
To go back to (3), I think this may be attributed to being able to enter a Q, then Erase it. I think this action screws up the serial numbering... ie the serial number generator is unaware you just deleted a Q and its S/N !! I'd have to play around to remember exact details.
Page 29 - Subj: Solution to Cards Needed
From: [email protected] (Arthur Tan - ART AB4RL)
Question: I'd like a report similar to the "Cards Needed" report but I want to see which cards I have sent out, ie, an additional column which has an "R" beside a contact for a particular entity if I have sent a card, and no "R" if I have not sent it out.
Answer: Cards Needed actually outputs the QSL status of each needed entity as you describe "R" for "already sent out" and "W" for "worked but haven't sent a card yet."
Question: If this isn't possible then a report which lists Needed Cards but doesn't list those that I have sent, ie, the same report as the Cards Needed but how do I add an exception which says only print contacts for that entity where QSL(s) doesn't equal "R" or "F" ?? Hope this is clear.
Answer: You can manipulate the report right before you print by using the Filter button. When you get the the screen that lists "Print to Screen, Printer, File, etc." it's the button to the right of all that. Alternatively, try this expression before you print:
NOT (QSL_SENT='F' OR QSL_SENT='R')
Question: Is there a neatly formatted report which lists entities needed (ie countries needed) by Band/Mode ? Each DX contest has me printing a DXCC awards progress report and showing unworked countries just to get a list of what I'm looking for.
Answer: To save paper try (1) print to screen (2) use Forms-Progress List (3) use All Band and Mode Progress report (I really like this one - it mimics the old DXCC tables of the DXCC printout from the league).
Page 30 - Subj: How to Handle Paper Jams
From: [email protected] (Anthony A Boykin - Tony WB2JRI)
My biggest problem has been printer jams aborting the print run. I then filter on QSL_SENT again, and add CALL>"lastcallprinted" to the filter.
From: [email protected] (Peter Wetzig - Peter VK4IU)
CALL>'K1ABC' AND QSL_SENT="R"
will do it if the last card printed correctly was K1ABC in alphabetical order for call.
Peter VK4IU
Page 31 - Subj: Adding a Field to a Report
From: [email protected] (Peter Wetzig - Peter VK4IU)
When you are in the report, deleting fields. Look in the Report Controls little window - you may have moved it to the toolbar - its actually a Windowstoolbar.
There is a icon with a symbol like a rectangular box with the letters abc in it. That's the button to define a field.
Click on it, and then in the report somewhere - click, drag, and click to make a field rectangle.
A dialogue box will open that allows you o enter the field name - use log.address. To the right of the Expression text box is a button with three dots. Click on it to make the field bigger, give you some tools o work with, and best of all a "verify" button to click to check your "field expression" for correctness.
When you are finished click OK and then do all the formatting activity you need.
PS: Another way is to click an existing field, Use Copy, and Paste using the Edit menu tools. Then click and drag the new field, and double click the pasted field to change the expression to the one you really need.
Page 32 - Subj: Printing Forms - How to Print Radio Memories
From: [email protected] (Peter Wetzig - Peter VK4IU)
Question: I've recorded on the form "Radio Memories" the settings on my antenna tuner for the various frequencies. I'd like to print it out as a quick reference and put it on the wall. Can't figure out how to print it. I know it must be easy...so hw?
Answer: The radio memories are stored in a database called RADIOMEM.
No special print facilities are provided, but ....
Go to Tools/Advanced/Database Commands
... usual disclaimer here - be careful, your flying solo here - back up the log FIRST! Not a great deal of risk, but!
When the windows open, in the Command window type
USE RADIOMEM
LIST ALL TO FILE MEM.TXT
EXIT
Key Presto .... look for a file called MEM.TXT in the C:\LOGIC5 directory. (May be a different drive D:, or E: and/or directory - where you installed Logic)
Use a text editor - Notepad - or double click on the file in Windows Explorer - clean it up, print it out, and plaster the walls.
Page 33 - Subj: How to Add Filter Selection?
From: [email protected] (Arthur Tan - ART AB4RL)
Question: How to simplify and pick out a "range" of addresses to print out envelope labels to be able to "tag" and then print out only the tagged ones. How do you print mailing labels without having to print them all out every time?
Answer: One thing you could do is to print ADDRESS labels BEFORE you print QSL labels.
Mark the QSOs you want to generate labels for by typing "R" in the QSL_Sent box on your logform. The "R" (Requested) gets turned into "F" (Fulfilled/Sent) after you print labels. However, if you go and print address labels first you can filter out which address labels you want to print by the QSL_SENT="R" which is the default expression anyway. Then go and print your QSL labels...
To filter by your user-defined field "ML-DATE" go to Filter, scroll down to Userfields, use $ (contains) and enter in ML-DATE:20001129| (the last character is a double-pipe i.e. shift-backslash). This will give you all the records that have today's date in the ML-DATE field.
One thing I forgot to mention in my last email is that ML-DATE must by of type Character. (You can change it at Tools-Setup-Log fields)
From: [email protected] (Larry Alkoff - Larry )
I just tried your suggestion and it works perfectly!
It actually works weather the ML-DATE is in Date format or Text format - probably because the tag is stored as an ASCII string in each case. I'm thinking about which format
to use in data entry where it makes a difference.
Page 34 - 43 - Subj: How to Add Filter Selection? AND An Understanding of USERFIELDS
From: [email protected] (Peter Wetzig - Peter VK4IU)
I would leave your ML-DATE field as a date. It helps avoid making mistakes when entering the date on a log form - keeps errors out of the log. When you are filtering treat it like text. It think that is a better way to go than risk data entry errors creeping into the log.
ML-DATE will almost never be seen as ML minus DATE because of the context in which you use it. You will use it where a "tag" or "field" is needed and Logic will not think about subtraction. The only risk is when you make an error in your expressions - and then, given Logic's attempts to "parse" the expression, will most likely fail to locate the "variable" or "field called ML, and then, given the errors, you are bound to have used DATE in an incorrect context, given the error, so almost guaranteed - not a problem.
One of the biggest issues for people in the IT industry has been the use of - or _ on the Internet. In hind site I would use _ rather than -. But no need to panic and change it.
Your ML-DATE won't appear in the filter search fields. Its a userfield tag name not a Logic defined field - only Logic defined fields appear in filter field lists.
As for the use of TAG ... your understanding is close mine.
Dennis is a programmer I guess. So he is inclined to use some terms we amateurs may find confusing. Lets have a go at explanation ...
Dennis has used the word "TAG" as a substitute for "identifier", or "label", or in our context a "userfield".
I would bet he reused a bit of programming code that was a text search tool he wrote for something else, got from somebody, or simply had lying around. Its original purpose probably had something to do with a "tag", what ever it may have been.
Alternatively - we could think of our "userfield" as having two things - 1 - the actual value, and 2 - the "tag". Our value has a "tag" so we can find it again when we want to. Do you put luggage "tags" on your bags when you fly in the US? I sure do - last time to Dayton I took 27 hours, but my bags took 43 hours.
Let us say we worked a JA in prefecture number 23, from city 2310, he was running 80 watts, and was in CQZ 25 and ITU zone 45 when the Solar Flux was 180. In my system all these values would go in the QSO USERFIELDS as text - "23 2310 80 25 45". How would I know what was what when I later want to do some analysis or award chasing.
So we give em all a "tag" - sort em out and round em up like his: WAJA:23| JCC:2310| TPWR:80| CQZ:25| ITUZ45| as a special sequence of characters all run together in a text field called USERFIELDS.
Now, how do I get at the values when I want to report, or check awards? We use a set of "tag" functions, or routines, or programs, Dennis has provided just for the purpose.
I guess the first problem Dennis faced was - what capability should the functions provide? Well, having been there, done that, he got a bit of paper, did some star gazing, asked a few people - and there's the results listed in the Help file for all to use. No magic - just the human mind solving a problem making choices. Just use Find and search for TAG.
To be able to use these userfields or tags on a log form, Dennis had to find a way to define the log form without knowing what names you would give the TAGs - you call it ML-DATE, for me its QSLSDATE. So he created a list so you could associate a "tag" with a pre-defined list of system tags on each and every log form - USER1, USER2, ... ,USER10. I bet he did the same star gazing as above and said "10 is enough. What amateur would ever want more than 10 on one log form. I'll give em 10 on every log form." I wish there were more than 10 per log form.
So ML-DATE can be associated with USER4 today, USER5 tomorrow, and even a different association on any log form you have loaded at the same time. I often have three or form log forms loaded - I have one for JA, one for US, one for VK, one for QSLing, etc etc - each has completely different associations, all loaded at the same time.
Personally I find I use TAG_VAL most often for printing in reports, or for QSL cards. MAKE_TAG I almost never use. TAG_EDIT I have used a lot while I was working out how to arrange all my userfields. TAG_EDIT would be used when you want to make mass changes to the log using the Advanced Database commands. Examples are in the Help file. Just use Find and search for TAG.
An example of my use of TAG_EDIT ...
I've just run the JA International DX contest for 2000. I have a special program that reads the output from AD1C Jim Reisert ADIF extract for CT, adds all my special values for each QSO like contest qth, my rig, my antenna, my power, solar flux for the contest etc etc. Each QSO looks like ...
<CALL:6>JI3VUB <QSO_DATE:8>20001111 <TIME_ON:4>0454 <MODE:3>SSB <BAND:3>15M
<FREQ:6>21.275 <RST_SENT:2>59 <RST_RCVD:2>59 <PR:2>24 <OPERATOR:5>VK4IU
<10CM:3>180 <MRIG:1>6 <TX_PWR:3>400
<CQTH:1>4 <CONTEST_ID:7>JA00SSB <MANT:1>4 <QSL_SENT:1>R <CQSO:1>1
<EOR>
I import the lot, do all the corrections, vias, and updates, print a report and woops ... I notice that each and every QSO has the same error for the contest QTH. I used code 4 instead of a code 6. Each contest QTH is a value in the List of Valid Values.
So ... I need to change the "value" for the "tag" CQTH in each QSO in the "JA00SSB" contest. I went to Advanced Database Commands ...
USE LOG
Click on Database Files menu, Mass Change, Replace Field Contents ...
In the Replace This Field, select USERFIELDS.
... hold the bus ... for all you guys reading along with Larry and I ...
THIS IS THE DANGEROUS BIT. I'm not kidding. THIS IS THE DANGEROUS BIT.
... yes, good, I can hear the clicking of the floppy disk drive as you go back and BACKUP YOUR LOG!
... Did you BACKUP YOUR LOG YET? You didn't! Don't worry too much - you can only lose your whole log ONCE. It comes as such a shock you will either NEVER do this again, or you will finally understand the value of a backup, and get good at recovering the log. I recommend getting good a restoring the log.
Great ... now your ready for the dangerous bit ...
Notice we are about to replace USERFIELDS - not one value, not a few tags, the WHOLE 255 BYTES OF USERFIELDS in EVERY RECORD. We have to do that simply because of the way ALL database software works - no choice, no mistakes, not bad programming - that's how its done. MS Access, Foxpro, Ingress, Oracle ... all much the same when it comes to this sort of thing.
The With text box looked like this ...
TAG_EDIT(USERFIELDS,"CQTH:","6")
... as Logic reads through your QSOs it will, for each record, pass all the text in USERFIELDS to the function TAG_EDIT. The program TAG_EDIT will (because its defined by Dennis that way) will do a text search for the value between the sequence of letters "CQTH:" and the next "|", replace it with the text "6" and then pass the change USERFIELDS back to Logic to be written to the database.
Notice we only had to pass the "tag name" and the "new value". TAG_EDIT already knew about the format - <TAG><colon><value><space><special vertical bar symbol>. We had to say "QTH:" - end it with a colon - because the USERFIELDS may contain the sequence QTH inside some other value. Putting the ":" on the end makes it a tag name and only a tag name.
The Replace Only If text box looked like ...
LOG.CONTEST_ID="JA00SSB"
... I counted the cards with the button - yep 673 cards. Click OK and it was all done in a flash.
Type Exit in the Command window.
What's the dangerous bit?
What happens if the TAG_EDIT line in the With text box is verified but without you realizing it ... yet ... is bad, in error, wrong, not what you intended. If you click OK - too late, in a flash every USERFIELD is now blank, broken, damaged, gone, not what you wanted, kaput, zippo. Well ... been there, done that ... it was an education.
What if the Replace Only If text box expression is wrong - say it's blank! ... good bye to the correct value in ALL USERFIELDS in ALL those QSOs ... and you will have no idea what the old value was. Its OK if the expression has a syntax error - Logic will not run it - its bad news if its correct, but not what you intended. Just before the log goes up in smoke must amateurs are SURE its what they want to do. Its only just after they press OK that they realize it did not do what they thought it would do. ... its usually the software's fault! - or so they say.
But ... stay calm. Its the same for the professionals. The only thing we lack is a bit of experience. So BACKUP THE LOG. Get some experience, make some mistakes. RESTORE THE LOG. Do it again ...
Backup and Restore are on the Tools Menu. Buy formatted floppies - its hard not to these days. The first time you backup to the floppy drive A:, it will just do it. The second time it will warm you that it is about to overwrite an existing backup. Only YOU know if it is OK to do so.
Each and every time I go on the air, book in QSL cards, or make changes to my log, I take a backup to "the next" floppy disk. I have 20 floppy disks, numbered 1 to 20, and I keep a log book of which one I used when. So I have to make a mistake, not realize it for about four weeks before I absolutely cannot go backwards to recover my log. I also usually record in my log book what I did to my radio log - it helps to know the differences between each backup copy.
Only YOU know which disk to restore. Keep a log book. When doing a restore, you will be asked to append or replace. Usually you will want to overwrite/replace to throw away the damaged QSOs and rebuild the entire log.
From: [email protected] (Larry Alkoff - Larry )
From what you said about the user fields storing text it appears that I could do my filtering most simply by looking for the text string 20001009. I would change the field format from date to text so that easier strings could be entered!
It's been so long that I forgot just how I generated the first set of labels. Just tried and see that my ML-DATE variable doesn't appear in the list of search fields. Could it have been there and disappeared when I upgraded to 5.3? It _does_ appear in the log form though.
It occurs to me that by naming the field ML-DATE that Logic might be taking it as ML minus DATE. Otherwise, shouldn't ML-DATE="20001009 work since 20001009 is stored as a text string even though I have defined the _entry_ of it as a date?
Tags seem to have something to do with USERFIELDS. Does that mean things like User5 and ML-DATE which used to be User4? Is a tag something like a pointer within a large field that is sub-divided by the pointer into smaller sub-fields?
From: [email protected] (Peter Wetzig - Peter VK4IU)
You have defined a Date field called ML-Date. You have tried to report on cards filtering on this date.
First thing to keep in mind is that "User fields" are stored in a field as text - that is to Logic they are not dates, just a bit of text stored in a "structured way" with other user fields in a pre-defined special text field called USERFIELDS, 254 bytes long. The only real date fields are the internal logic ones like QSO_DATE.
The implication - we, rather than Logic have to provide the algorithms to report using the field, as only we know its a date when its stored in USERFIELDS during the filter process.
Army - AE5P, suggests "quote marks around the date. ie. ML-DATE={09/09/00}".
When used like this it will only work for the real date fields like QSO_DATE, not for text in user fields - yes ML-DATE looks like a date to you - but to the Logic software its just a bit of text arranged to look like a date to us. When its placed on a log form as a separate field item, Logic can tell its a date - you told it that when you defined the field. But, once its tucked away in USERFIELDS, its just a bit of text.
Well may you ask why!.
When Dennis designed Logic, he realized that we amateurs would want to do lots of things, of which he had never thought in even his wildest dreams. So to avoid having to constantly change his code to suit each of us, one at a time, he created a general mechanism, an unlimited mechanism, to keep most of us happy, for us to use any way we wanted - USERFIELDS. He has provided a sent of "functions" to store, read, and edit these fields - MAKE_TAG, TAG_VAL, TAG_EDIT.
Yep - in hindsight, I'm sure he may have done it differently. But ... there it is, we have to work with it.
I use them for recording - 10cmflux, contestqth, qslsdirect qslrdirect, myrig, myantenna, theirant, theirrig, theirpower, JCC, JCG, Italian Provence, Argentinean Provence, Korean districts, Japanese Prefectures etc etc. I have long since run out of space in 254 bytes and had to re-design my mechanisms to limit the space used by each field. I use codes and store values in the LISTS database.
Yes they are tedious, but I can accomplish anything I need - the only logging program in which I have been able to do anything I wanted.
Wait there's more ...
When you open the filter dialogue window, in log form, in report, no difference, the panels contain simple equals, contains, less than, greater than, between, type operators. This mechanism is good for simple things like " all cards containing JCC", "all USA cards", or "qso_dates BETWEEN x and y" and simple combinations of them. But for USERFIELDS one needs to do more. In short you have to "home brew" the filter statements.
As Art AB4RL indicated in his contribution we have to use the Edit button in the Filter window and type the statements ourselves.
Have a look in the Help files for Expressions and Functions. Remember to also use the Find dialogue panel in Help. If asked a question - Index to Maximize Search Capabilities. This allows free text searching in the Help file. Try it, type TAG and see what entries are found in the index. Should find tag_val, tag_make etc.
So to filter QSOs based on a value in the USERFIELDS
1. Understand how Dennis stores dates in USERFIELDS (as text like
yyyymmdd)
1. Treat it like a bit of text (only text in USERFIELDS)
2. Be prepared to mix it with the functions provided. (find what's possible
in Help)
So for your needs try things like the following. I agree with Art AB4RL ....
TAG_VAL("ML-DATE:",USERFIELDS)>"20001011"
TAG_VAL can return a date, provided the date is stored as yyyymmdd by using ...
TAG_VAL("ML-DATE",USERFIELDS,"D"){01/01/1999}
Notice the change in the format of the stuff on the right of the symbol. The third parameter, the "D", tells TAG_VAL to return a DATE so we have to provide a DATE for comparison - the {01/01/1999}. The format of a DATE value follows that used for your PC in general. Look in Logic5, Tools/Options, Application dialogue panel for the correct format for your PC.
Last bit of experience ... its a bit slow. The record search causes a lot of code to be executed to process the TAG_VAL function for every record.
Hope it all helps. There's no magic - everybody has to use these mechanisms to make QSO selections. Tedious yes. Flexible - sure is.
My technique is to keep up to date, and print all cards and addresses marked R in the QSL_SENT field. My biggest problem has been printer jams aborting the print run. I then filter on QSL_SENT again, and add CALL"lastcallprinted" to the filter. I never Mark Cards at the end of the report run until I have collated all cards ready for the post man. then I rerun the report to screen and then mark the QSOs "F".
From: [email protected] (Peter Wetzig - Peter VK4IU)
As for Userfields ...
It's ALL in the field USERFIELDS of each record in the log. There are not really any pointers to anything.
Lets follow the trail with your ML-DATE tag.
Your created a userfield or tag called ML-DATE. You used the menu option Tools, Setup, Log Fields, Spotting and Awards Tracking which opened a dialogue box. You then added a record to the list - it's a small database just like your log, or radio memories, and its called LOGFIELDS.DBF.
By making entries in the record that describes ML-DATE you said its a date, you said there's NO list of valid values for ML-DATE, each value will be separate, and a description for Logic to show as a help message and a comment for your own use. That's all for a date userfield or tag.
When you clicked the "floppy disk", Logic wrote the data away back into the little database, and then Logic does ... well, nothing.
When designing your log forms ....
When you click "the little man" on the log form to include some userfields on the form, there is an additional entry now showing from which you can choose - ML-DATE. (That's the great bit about databases - you add a record to the little database like LOGFIELDS.DBF, and the programs don't change.
The code "behind the little man" searches the LOGFIELDS database and - key presto one more item in the list - some would say it was magic. Dennis knows it was just plain hard work.
Now that you have ML-DATE appearing on the log form (disguised as USER1-10, etc), you can make an ML-DATE entry appear for any QSO that you bring into the log form window. You can bring it into the window by any of the mechanisms available to you - new record, forward, back, filter, find etc.
Logic does that little trick by ...
Reading the QSO log record into memory. The system fields are easy - it just copies the data from the record field to the log form field item.
Userfields or tags need more work. We need a function to scan the complete text of the QSO log record text system field called USERFIELDS, and extract the value for the tag - yep, its TAG_VAL. How does the code know which ones to show? You worked with the "little man" (some people call him "the waiter") to make a list of which system field, USER1 to USER10, should be used to display which userfield or tag. The list is stored in the log form
so the program code is always the same for every log form - just like making money, do it once, sell it over and over again.
I think you may be able to see now why keeping ML-DATE defined as a "date" is a good idea. When TAG_VAL reads the value for userfield ML-DATE from the QSO log record, it makes SURE it is displayed as a date on the log. You will be UNABLE to enter a bad date - 09/31/2000 will not be in your log!
TAG_VAL will not be allowed to put an invalid date onto the log form, the log form data entry code will not let you create a bad date when you type and TAG_EDIT will make sure the date remains valid when translated to text when storing it back into the system QSO record field USERFIELD when the record is written to disk.
Once the QSO is in the window, being displayed, any values for which you have field items on the log form (system log fields or log usertags/fields) will appear. If there is no ML-DATE for that QSO, the associated field item (USER4, USER10, whichever) will show nothing.
If you type in the ML-DATE item, LOGIC will place the characters in the item and hang onto them waiting for you to finish ALL updates to the QSO. Why waste time writing records for every field change on the QSO record - better to wait until all have been done and write it once.
There are lots of things that will cause the record to be written - like click on the "floppy disk" icon, moving forward, back, clicking on the browse window. Basically, any action that would cause the "pointer" in the database to move to another QSO will cause the current QSO record to be written if any values for the QSO have been changed - system fields or user
tags/fields. There is a setting in Tools, Options that indicates, "Confirm Saving Changes" yes or no. If it is checked, "YES", the software, Logic, will ask "OK to replace the values with the changed ones for this QSO?".
Only you will know how to answer - answer YES if you really did make some changes, answer NO if you have ANY doubts what so ever. Many answer Yes because they feel the software knows best - it doesn't, only you do. When experience builds, and you gain confidence, turn it off.
So Logic just wrote our ML-DATE value for this QSO to the QSO record in the log database. It used the TAG_EDIT function to scan the text currently held in USERFIELDS, updated the value, or if no existing value was there, created the whole "ML-DATE:20000101| " string and appended it to the text in system field USERFIELDS. Notice it would take 7+1+8+1+1=17 bytes (notice the trailing space) for each QSO having a tag/value pair for ML-DATE.
So ... there is, potentially, an ML-DATE tag/value pair for every QSO.
There are no pointers to anywhere - its right there in the QSO record. Each pair, ML-DATE tag and value, exists independently of any other ML-DATE tag and value in any other QSO record. Their only links are via the definition in the LOGFIELDS little database, and the association list under the control of our "little man" on every log form and .... YOU, with your knowledge of why you created it and the intentions you have to use them in a coordinated way with log display, reports, and QSL cards and your printer.
Page 44 - 46 - Subj: Updating Userfield Process - Solved
From: [email protected] (Bill - K1UQ)
Well, it turns out the original information from Peter VK4IU was absolutely correct. But what was not mentioned until Peter's last email to me (or else I missed it in my haste to accomplish task at hand), was for me to ignore the error message I was getting when verifying the expression I had created. Imagine that - ignore the verify warning message! I did, ran the routine, and it worked in a heartbeat. And worked correctly.
To recap the issue at hand and using information derived from Peter VK4IU:
Problem:
I had worked a contest using CT. I created a text ADIF file from the CT log. I edited this ADIF file, adding user attributes for rig, power, antenna - and failed to include the user field attribute for my amplifier. More importantly, this was not discovered until sometime after importing into LOGic and after having made other log entries.
My log was therefore incomplete with no amplifier plugged into my user field for most every contact I made in CQWW 2000. Some entries for the amplifier had been entered manually during QSL process subsequent to contest (and import!). This information is important to remember I think, as the solution proved to accurately overwrite all amplifier fields in this contest, whether blank or manually filled-in with the amplifier.
My Log and Userfields:
I use all 10 userfields. One field logs the model amplifier I may have used. I setup my List of Valid Values to have a Field Name called AMP with a value of COMMANDER HF-2500. I have a Log Field setup with a Name of AMP and Field Type of Character. The ADIF Name is also AMP and I have both Import and Export checked off. My default log form has this user field enabled. Entries to this field can be auto-inserted via an ADIF import (when I remember!) or done manually using the drop-down list or by typing.
Corrective Action Overview:
As suggested by Peter VK4IU, I was trying to use LOGic Advanced Database Commands to fill-in the blank amplifier user field for QSOs from a given contest. I was following his advice, but kept getting a message saying the expression I created was in error. It turns out this error message is perhaps in error itself!
The method to be employed is to use the Advanced Database Commands to isolate the QSOs of interest (the records in the database needing to be fixed) and fixing these records by allowing a mass change to replace the contents in a desired user field.
Preparation:
1. I backed up my log - twice, using 2 different floppies.
2. I read the online information. If you haven't yet setup LOGic to make use of Help - Find to search on keywords, DO IT!
3. I read the manual. It's old, but the content for this topic was pretty much the same.
4. I read and digested Peter's last email advising me to ignore the verify warning and run the routine.
Steps Followed: (I am using version 5.3.116)
1. Go to Tools, select Advanced, then select Database Commands. This opens a window called Database Commands, and inside this window is a smaller window called Command. Both windows are blank. Please note the status line at the bottom of the larger Database Commands window. You will see an open folder icon to the left and an empty check box called Exclusive to the right.
2. The insertion cursor should be in the smaller window. If not, do so. Now inside the smaller Command window, type USE LOG
and press the Enter key. Look back at the status line at the bottom of the larger Database Commands window. You will now see Record:1/nnnn (nnnn indicates the number of records in your log, so this number will vary) located between the open folder icon and the empty Exclusive check box.
3. In the larger Database Commands window, go to the menu line and select Database Files, then Mass Change, and then select Replace Field Contents. An additional window called Replace should open. There are three places in this window where you will make entries: Replace this field, With, and Replace only if.
4. In "Replace this field" use the drop-down list and select Userfields.
5. In "With" type the expression you need to provide the replacement value. In my case I wish to replace blank amplifier user fields with the model name of my amplifier (i.e. the "value"). This is the expression I used:
TAG_EDIT(USERFIELDS,"AMP:","COMMANDER HF-2500")
TAG_EDIT is a proprietary function name by PDA/LOGic. Its allows you to edit your fields.
The field I am interested in fixing is the field called USERFIELDS. It is separated from my field name with a comma ( , ) and there are no spaces.
Please note my user field name is AMP. In the expression, you will add a colon ( : ) to the end of the field name and enclose in double quotes ( " ). So it will appear as "AMP:" (double quote, field name, colon, double quote - AND NO SPACES!)
My field name value which I want to be inserted into each user field called AMP is COMMANDER HF-2500. In the expression, the value will be enclosed within double quotes - and gets separated from the field name with a comma. Also note there are no spaces in my expression other than the one in my field name value (between COMMANDER and HF-2500).
6. In "Replace only if" type the expression you need to direct, or perhaps limit, the search and replacement activity. In my example, I wish to limit the replacement activity to only those QSOs in one contest - CQWW 2000. My name for this contest identifier (the Contest ID) is CQWW00. This is the expression I used:
LOG.CONTEST_ID="CQWW00"
The field name I wish to use to limit the search is called Contest ID. And the name for my particular contest is CQWW00. No spaces are used.
7. Click on the OK box to run.
Thanks again to those who helped me, to those who provided support, and answers, and hopefully this can get added to Tips & Tricks. Hopefully I've accurately depicted the process I used. BACKUP, BACKUP, BACKUP!!!
Page 47 - Subj: Printing Prefix Table
From: [email protected] (Arthur Tan - Art AB4RL)
Question: How can you print a hard copy of the prefix table with all of the appropriate Logic headings at the top of the pages and showed DXCC, COUNTRY NAME, PREFIXES,
LOCATION, DIR, 3RD PARTY, CQ Z, ITU Z, and CONT?
Answer: This will output all the info from the Prefix table into a text file.
Go to Tools->Advanced->Database commands
Type
USE PREFIX
LIST ALL TO FILE PREFIX.TXT
EXIT
The file PREFIX.TXT will not be in C:\LOGic5. However, it's column width is extremely wide. You might want to look at it in a browser. You also might want to edit it using a text editor before you print it out.
Page 48 - 50 - Subj: Dates in LOGic
From: [email protected] (Peter Wetzig - Peter VK4IU)
... I too wondered what the "^", keyboard "Shift-6" was for in the date constant. So I looked it up ...
Logic is written in a database system called Visual FoxPro. One used to call them "languages" but that is too restrictive these days. I prefer system - it is now a Microsoft product. MS Access is their "user" friendly (hi hi) database package supplied with MS Office, and Visual FoxPro is their database tool intended for use in developing programs like LOGic.
Just as text strings need to be surrounded by "quotes", date constants in Visual FoxPro - anywhere you need a specific date in an expression - have a format exactly as you describe, surrounded by "curly braces" - "{ and }". The question is - what is the format for the months, days, years within the curly braces?
{dd/mm/yy} or {mm/dd/yyyy} or {yy/mm/dd} ... you get the picture, it varies from country to country.
The actual format of the stuff between the braces is dependant upon "flags", "indicators", "settings", for the PC upon which you are working - look in Start, Settings, Control Panel, Regional Settings. Also look in LOGic under Tools, Options, Application - which references the Regional Settings in Control Panel. It can also be changed, "on the fly", within the program by using statements like "SET DATE TO BRITISH" or "SET DATE TO AMERICAN" or "SET DATE TO ANSI".
A problem - if you were Dennis at PDA, and you needed to develop a report, based around dates, that worked in any country - how would you code the date format? Sure, using program code, one could examine the settings in Control Panel and do all the coding necessary. But the programs become - bigger, fatter, slower. Is there a better way?
The good folks who provide Visual FoxPro thought of a way to do it smarter. They created the "strict date format" - "{^yyyy/mm/dd}". No guessing, no variations, no difference around the world - it's always, literally - yyyy/mm/dd. Post Y2K - it's the format of preference. You have little to remember - it's always the same.
The Visual FoxPro library routines used by the programs in LOGic, know a date is coming if they see a "left curly brace", and that a "strict date" is coming if it is followed immediately by a "^". If no "^", the date is expected in what ever format the Regional Settings or program code has "set", and you had better know what it is if you expect correct results. July 6 and June 7 may be confused with each other.
So, anywhere in LOGic, where you need to specify a date in an expression, you can use {^yyyy/mm/dd} or {"PC date"} - where "PC Date" is in that specific format set for your PC. I would use {^yyy/mmm/dd} for the reason that if we exchange reports or tools, they will work every where - well, that's stretching it a bit, but you get the picture, I hope.
Now for the tricky bit ....
Go to the Logic Help file, click on Find. Maximize Search Capabilities if asked.
In the "1.Type the word..." text box at the top type "left curly brace", that is {.
In item "2. Select..." text box, click on "{^".
Then double click on the What's New item in text box "3.Click ...".
Scroll down to the list of changes for Logic 5.2 - in there you will see that Dennis introduced the new "strict date" format with version 5.2 for us all to use, to avoid the differences in dates between countries.
... {^09/12/2000} could look a bit like all calls since December 1909, but I wonder what it did with the 2000 for a day??
To test this sort of thing, use Tools, Advanced, Database Commands and in the command window type "? {^09/12/2000}" and press enter - for me it gave a NULL date, and "? {09/12/2000} gave me 09/12/00 which is correct for my system. I tried a few other "invalid dates" and got a NULL date. Interesting ...
Subj: ....more on Dates in LOGic
From: [email protected] (Peter Wetzig - Peter VK4IU)
I just spent a bit more diagnostic time on dates in LOGic.
It appears that the Options, Database Commands console ignores the Control
Panel settings when displaying dates.
Try the following ...
? {^2000/12/09}
... my system printed 12/09/00, which was NOT what I expected - Control Panel is set to dd/mm/yyyy. I tried ...
SET DATE BRITISH
? {^2000/12/09}
... gave 09/12/00 as I would expect.
SET DATE AMERICAN
? {^2000/12/09}
... gave 12/09/00 as I would expect - now that I know what's going on.
So those of you in the USA will get what you expect. Those in Europe and other places may get a little confused by the behaviour of Visual FoxPro.
Always using the strict date format of {^yyyy/mm/dd} in LOGic would seem a
good idea.
Page 51 - Subj: Adding the NEW Canadian Territory of Nunavut to the PREFIX TABLE!
From: [email protected] (Rob Kennedy - Rob VA2FB)
Not too long ago, a NEW Canadian territory of Nunavut was created. The old NWT (VE8) was split into two. To the EAST is Nunavut (VY0) and to the WEST is part of the OLD NWT (VE8).
Here is how to add NU to Logic (if it already NOT there).
1. BACKUP your LOG!!
2. CLOSE ALL LOGFORMS.
3. Edit the LIST of Valid Values. Click TOOLS -- SETUP -- List of Valid Values.
4. Click Get and type VE into the top field. Scroll down the list and make sure that there is NO entry for NU in the list of Valid Values for VE_PROV. If it is already there go to step 7!
5. Click ADD. Select VE_PROV as the field. Type NU as the value. In the description Box type NUNAVIT.
6. SAVE!! and EXIT the FORM.
7. NOW UPDATE THE PREFIX TABLE -- Click on TOOLS -- SETUP -- PREFIX..
8. Check to se whether Nunavut is already there. Click on Get and type VY0AA. See if a record for Nunavut appears. If it is there then do nothing. You are done!
9. Click on Get and type VE8AA. The record for VE8 NWT should appear. RIGHT CLICK on the ADD icon to DUPLICATE the record. In the PREFIXES box type VY0. In the LOCATION field type VE PROV:NU| NUNAVUT.
10. You should probably change the LAT and LONG etc for BOTH the VE8 and VY0 records but I do not have the details.
11. SAVE and EXIT.
Page 52 - Subj: How to Check Log for Empty State and Zone Information
From: [email protected] (Xavier Pedrerol)
Use the following filter expression to check log for QSOs that do not have State or CQ assignments
click on 'Filter' button from your Log Form, now on 'Edit' and paste the following expression:
for the first one: DXCC='K '
for the second one: EMPTY(TAG_VAL("CQZ:",USERFIELDS))
for the third one: EMPTY(STATE)
and all of above: DXCC='K ' AND EMPTY (TAG_VAL("CQZ:",USERFIELDS)) AND
EMPTY (STATE)
Page 53 - Subj: Two Operators With Logic 5
From: [email protected] (Jacques, K5DV)
The xyl and I both use Logic. We each have our own database. Per Dennis, I installed a second installation in a different directory. We created 2 icons for the desktop. One called my version ("C:\Daves Logic\Logic.exe"INSTANCE=K5DV) The second called my xyl copy ("C:\Libbys Logic\Logic.exe"INSTANCE=WB6AXD).
Obviously, this is the path located in the Properties of the shortcut. The Daves Logic and Libbys Logic are where the two installations of Logic are. Each operate as totally separate Logs (Databases) and will run at the same time with NO problems.
The only hassle is every time you update Logic you have to do it twice.
Page 54 - Subj: How to Filter on Userfields
From: [email protected] (Arthur Tan - AB4RL)
In the FILTER screen scroll down to Userfields. Change the OPERATOR to "$" (Contains) and the VALUE to whatever the name of your user defined field. For instance, if you have a user defined field called ANTENNA and one of the choices is YAGI and you want to filter for all instances in your log where the ANTENNA field is filled in with YAGI then the format in the VALUE field would be ANTENNA:YAGI|
Page 55 - Subj: Cabrillo 10M contest PROBLEM
From: [email protected] (PDA) (Dennis - WN4AZY)
A number of customers have sent Cabrillo logs to the ARRL without the Received Serial# in the log.
If you made your own log form, here's how to fix it.
Go to Log/setup/contest/general. In Report Expression 1, and this to the end of the existing expression:
+ TAG_VAL("VE PROV:",USERFIELDS)
On an unrelated matter, be sure to enter the contest name and category. The ARRL understandably cannot accept a log without this.
Page 56 - Subj: Digipan & Logic - How to Log a QSO into Logic from Digipan
From: [email protected] (Peter Wetzig - VK4IU)
... start Digipan, make sure it is running.
... start LOGic, make sure Log, Digipan Interface is checked.
Then use Digipan in the usual way. See a call sign in the text, double click on it, and Logic will be sent a DDE packet at the same time as Digipan puts the call in the text box. Ditto for RST, Name, QTH etc. Just use the tools of Digipan and LOGic will be sent the data as Digipan records it, LOGic will follow Digipan.
Digipan is the data server, LOGic is the listener.
Page 57 - Subj: Map Position
From: [email protected] (Dean Craft - W4INK)
…with map positioning the thing that you must remember to "not" do, is to "minimize" the map before closing LOGic. Minimizing the map before closing LOGic will place the next map opening (after LOGic restart) in the lower, far right corner of the screen.
The map can "have" or "can not" have the focus when closing LOGic and LOGic will always restart with the map positioned as it was when LOGic was closed. Restarting LOGic will place the map back in the desired position but focus will be on the logging screen. I believe also that it was necessary to set the size etc. of the map and actually close the map (thus saving?) it once. The positioning and map size will remain constant even through multiple LOGic restarts and rebooting.
If; however, you minimize the map and then close LOGic, the map will be placed in the far right lower corner of the screen when LOGic is restarted. This holds whether "...always on top..." is selected or not.
I believe it is normal within Windows, but noted that with "...always on top..." selected, you cannot shift the focus from the map to logging by simply clicking on the (or a) logging window nor can you change the focus by clicking on the icons located on the START bar at the lower edge of the screen. You must minimize the map in order to change the focus back to the (or a) logging screen.
…the long and short of it is that indeed, you can have the map sized and positioned exactly as you want it and have it open when starting LOGic. It will be opened without focus. As long as you remember to not close LOGic with the map minimized instead of simply not having the focus, everything works perfectly.
Page 58 - Subj: Here's How the INFO Window Works
From: [email protected] (PDA) Dennis WN4AZY
If a state is logged, that is used.
Otherwise, if a DXCC containing a "-" is logged, that is used. We use a - when the DXCC typically cannot be determined from the callsign.
Otherwise, the call is used. This typically gives info on a region of a country--the large ones, anyway.
If the call contains a /, and both sides of the slant contain a valid prefix with letters and numbers, the shortest is used. If they are the same length, the first is used.
Page 59 - Subj: DXCC Submission Report
From: [email protected] (Arthur Tan - AB4RL )
As you step through the AWARDS report, LOGic asks you for the tag you used to mark cards as submitted. Most people (as per the manual) use DXCCSUB: Enter whatever you use. Finally, right before you print the report you will see QSL_RCVD $ "SFWRU"
To *not* see the already submitted cards just delete the "S" so that the expression reads QSL_RCVD $ "FWRU" Indeed, you really only want to see cards that you have confirmed but have not yet submitted. Therefore, the expression becomes QSL_RCVD $ "F" (S=submitted; F=confirmed; W=worked; R=requested; U=unworked).
After you print LOGic will ask you if you want to mark Fulfilled cards as Submitted. I don't usually do this until I get confirmation back from the DXCC desk that all my cards are okay. So I hit "no" at first and when I get my cards back I run the report again and then chose "yes."
Page 60, 61 - Subj: DXCC Submission Report … Another Method
From: [email protected] (C.M. Christensen - Chris ACØM)
This will work well if you are only interested in Mixed mode entities that have never been credited on any band or mode. If, however, you are submitting cards for band countries and mode countries, and want to keep the number of cards you are submitting to a minimum, the process is much more complicated.
To locate every card you have not submitted on a particular mode you must run an AWARD report for each mode that is of interest to you (rtty, phone, cw, mixed, etc.). Then for every band you are interested in you must do the same thing. Every report should be set up for AWARDS.REP, DXCC, the band or mode you want, DXCCSUB:, BAND/MODE and QSL_RCVD="F".
Even after doing all of this you are still not home free. Here is why. If you need a particular entity on rtty for example and you also need it for a new band entity on ten, logic will not necessarily find the ten meter contact on rtty. It may in fact find a 15 meter rtty contact to submit for a new rtty entity and a ten meter contact on cw for a new ten meter entity. You end up sending in two cards to get credit for the rtty and ten meter contact even if you have a card in Logic that shows a ten meter contact on rtty. I have not idea why it works this way but it does.
… Response From: [email protected] (Arthur Tan - Art AB4RL)
What I usually do it to select the the particular band AND mode (see the second screen entitled SELECT BAND AND MODE that you see while running AWARDS.REP). This will filter down to only 10M RTTY contacts for example.
However, all this does take time because you pretty much have to run a report for (1) new mixed mode QSO's regardless of band/mode (2) new CW, PHONE, RTTY QSO's, one mode at a time (3) new band QSO's, one band at a time and (4) new BAND AND MODE QSO's, one BAND+MODE combination at a time.
I organize my QSL's alphabetically by prefix (not necessarily by DXCC country). When I run the the four reports described above, I just pick through my QSL box, pulling out particular cards. There will always be times when you already pulled a card out for an all time new one on CW and it happens to be a new one on 80M CW as well for instance.
From: [email protected] (Bob Mattaliano - Bob N6RFM)
For cards I am going to submit, I open the USERFIELDS log form. I then place in the big window on the upper right a tag, "DXCC:Y" or "DXCC:M". This allows me to distinguish between single/multiple QSO cards. When I decide to send cards to the DXCC desk, I use a filter command to gather only those QSO's marked with the tags above. It's then a simple matter to export the file to Excel and sort these in any order, make the font bigger, whatever. I did get a note back from the DXCC desk complaining that the default type size for the LOGic printout is too small. That's why I use Excel. Anyway, when the cards come back I REPLACE the DXCC:Y or DXCC:M with DXCCSUB. That way I can easily track what I have submitted versus plan to submit. Yes, I know that there likely is or should be an easier way.
Page 62 - Subj: How to Reset Contesting Scoring
From: [email protected] (Arthur Tan - Art AB4RL)
After you select and open the contest logform you want to use there is an extra menu called "Log" on the toolbar above. Drop down that new menu and select "Setup." Alternatively hitting the function key F5 is a shortcut to drop down the menu. Once you get into Setup, select the tab titled "Contest Setup." Then fill in the "Contest Start Date" and "Contest End Date" then click OK. Then go to Tools->Misc Utilities->Rescore Contest and pick the logform that you just used.
It then will clear out the Contest Score window. Finally go back to Forms-> and select the proper logform once more. Now Contest Score should be accurate and track your progress during the contest.
Page 63 - Subj: Utility to Import 1010 Database
From: [email protected] (George Vincent - George K3GV)
There is a utility to import 1010 database form available on the internet.
See http://hds.net/win1010dl.htm. Download the 1010.TXT file and unzip it. Run Import 1010 from tools/misc utilities.Placing this expression in Copy From Prefix Table looks up the callsign from the description field in the 1010 list, and automatically logs the 1010 number.
MAKE_TAG("1010#:", GETLISTVALUE("1010#", LOG.CALL))
You need to have 10 -10 Number as one of your fields on your logform. Access Copy From Prefix Table from "Log ->Setup"
Page 64 - Subj: Printing Unworked DXCC Countries
From: [email protected] (George Vincent - George K3GV)
Do the following to print Unworked DXCC
1. Select File>Print
2. Select Report to Run >AWARDS.REP
3. Select Award >DXCC
4. TAB thru the screens and check Print Unworked Entities
5. Select >FINISH
6. Select order >Award Value
7. In the Run Report Options - AWARDS Window type QSL_RCVD $ "U"
8. Choose OUTPUT to Screen and print
9. If you are happy with PRINT PREVIEW > then print
From: [email protected] (Michael D. Rand - Mike 4Z1MR)
I like to have a list at my rig showing all the DXCC countries from which I have not received a QSL card. {Perhaps I worked a country but never received a card (the QSL_RCVD field is marked "S" or "R" in my log.)
If that's what you're looking for, simply revise item 7. above to read:
7. In the Run Report Options - AWARDS Window type:
QSL_RCVD $ "U" OR NOT QSL_RCVD $ "F"
Page 65 - Subj: How to add new DXCC - Ducie Island
From: [email protected] (George Vincent - George K3GV)
Effective 16 November 2001 a new DXCC Entity will be added. In order to update your LOGic files you need to do the following.
Caveat - as always MAKE A BACKUP of your files (log) before you start
1. First of all, go to tools/setup/lists of valid values
2. Then add the following record. Be sure to add new records, not change any existing record
3. Click the Add button to add a record!
4. In Field Name > select DXCC
5. In Value > type VP6-D
6. In Description > type Ducie Is.
7. In Comment > type OC-182
8. Update and flush buffers (blue disc icon next to + button)
Now add these records to the prefix table:
1. Go to tools/setup/prefix table
2. In DXCC pfx > Select VP6-D from the drop down list
3. In Prefixes > type VP6,VP6DI
4. In Dxcc Field > type Ducie Is.
5. In Location Field > type Ducie Island
6. In Comment Field > type OC-182
7. In Lat Field > enter -24.50 (remember the minus sign)
8. In Lon field > enter -125.00 (remember the minus sign)
9. In CQ Zone > enter 32
10. In ITU Zone > enter 63
11. Check Third Party? Box
12. Check ARRL Bureau? Box
13. In Begin date > enter 11/16/2001
14. Leave End date blank
15. In Continent Field > select OC from drop down list
16. In Time Zone > enter 8.00
17. Update and flush buffers (blue disc icon next to + button)
18. Close LOGic and run Clean
Ducie Island VP6-D will now appear in your drop down DXCC list and in your spot log.
Page 66 - Subj: Improved way of sending serial numbers in CW
From: [email protected] (Frank Ayers - Frank W2FCA)
A while back I asked about the code for sending a serial number during a CW contest. Somebody pointed out that the code is STX(3) or STX(4). I started to use this during the ARRL SS but found it sends leading zeroes. To make the exchange a bit faster, I modified it to -
STR(VAL(STX(4)))
Now it just sends the number, ie 23 instead of 0023.
Page 67 - Subj: Cabrillo Export
From: [email protected] (Skip Cameron - W5GAI )
I finally figured out how to get the Recd Exchange output in the Cabrillo Export.
For those who may have the same problem, here's what I did:
1. Open the log form for the contest you want to export.
2. From the contest log, go to LOG/SETUP/GENERAL
Make sure the contest dates and ID are correct for the contest you want to export.
3. Copy the Exchange Expression.
4. Go to the CABRILLO tab and paste this expression in the Rx Exchange Expression 1 field. 5. 5. Click OK.
6. Go to TOOLS/EXPORT/ARRL CABRILLO CONTEST FORMAT
7. Enter your TX exchange and transmitter number.
8. Click on Export and Logic exports all the data needed to file a Cabrillo Report.
Page 68 - Subj: How to Edit the TelNet and WebCluster Drop Down Menus
From: [email protected] (George Vincent - George K3GV)
…this is how to edit the drop down lists for both TelNet and Web Cluster Spotting to delete an item on the list:
1. Make sure the WebCluster and TelNet windows are closed
2. Go to > Tools > Advanced > Database commands
3. In the "Command Window" Type: Use Telnet_menu
4. Enter
5. Type: Browse nowait
6. Enter
7. Now comes the oddity; click on the blue bar at the top of the Database commands window and drag the window to reveal the window underneath which is a list of the items on the drop down menu
8. Simply highlight the item and the time stamp and use the delete key on the keyboard.
9. The items on the drop down list that you deleted are now gone.
10. Repeat for the WebCluster drop down list except in the "Command Window" Type: Use DXSummit_menu
SRI, that it sounds trickier than it really is, but it is really quite simple. I have done it several times and it works OK. The tricky part was revealing the hidden window. Why it is hidden I do not know and neither does Dennis. According to Dennis these files maintain themselves automatically--they remember the last 20 or so selections. The drop down lists were really not intended to be edited. Each can only hold so many entries and then they start to be overwritten with the oldest replaced first. However, I understand that it is nice to be rid of those not needed and this is how it can be accomplished.
Page 69 - Subj: How to Print Slashed Zero Ø Font
From: [email protected] (PDA)
Question: Logic shows the slash zero on the log sheet but not when reports are printed.
Answer: You have to change the font in the report to whatever you are using.
Another trick is to use chr(216)--that prints a character like this in most fonts: Ø
Instead of printing CALL, for instance, you would print CHRTRAN(CALL, "0", CHR(216))
Page 70 - Subj: Modifying a Userfield Value
From: [email protected] (Arthur Tan - Art AB4RL)
Question: I'd like to do mass changes to the database, based on the State info instead of district, but I don't know how to change, in FoxPro, the CQZ tag in the Userfields field.
Answer: Make a backup of your log data, no matter what happens.
Try using Tools|Miscellaneous Utilities|Fix Stuff.PRG first.
You can also try Tools|Advanced|Database Commands
USE LOG
REPLACE USERFIELDS WITH 'CQZ:5|' FOR STATE='FL'
[...etc...]
CLOSE TABLES ALL
You can do this for each state but it's a long and tedious process.
Page 71 - Subj: How to turn the Rig Control Window On or Off
From: [email protected] (George Vincent - George K3GV)
The radio control window can be hidden in both LOGic 5 and LOGic 6 by clicking on the "Window" drop down menu on the top of the screen and then clicking on the Rig Description. In my case that is "Yaseu FT-1000MP." The description is whatever was chosen during rig setup. If the control is hidden then more screen space is available for other windows. Rig control is still possible by clicking on "Rig" or "Log" in the "Spot Log" and the frequency will be changed. If you later decide to display the rig control window, simply go to the "Window" drop down menu and click on the rig description and it will be unhidden.
Page 72 - Subj: How to Change Comment Field Size in Lists Table
From: [email protected] (George Vincent - George K3GV)
Go to Tools > Advanced > Database Commands
Turn "Exclusive" On (check box)
Type "use lists" without quotes and Enter
Type "modify structure" without quotes and Enter
Change size of "Comment" field to 254 (maximum)
Page 73 - Subj: Filtering Using Date/Time
From: [email protected] (Joe Dubeck - Joe NA9A)
Question: What is the format for entering the time when filtering for date and time using
QSO Date T.
Answer: Try filtering both QSO DATE T as ">" the day before your beginning date and TIME OFF as ">" the second before the beginning time - and with the "AND" box checked (default) at the top of the filter dialog box, it worked fine. This is a work-around to what I assume is a more correct use of QSO DATE T in case you don't get that answer.
Page 74 - Subj: How to Clear Error in Logic 6.0
"CAREFUL GUYS ZAP IS POWERFUL"
From: [email protected] (Tony Boykin - Tony WB2JRI)
First Use same dbase command screen type SET EXCLUSIVE ON or put a check in the box center bottom of screen. It's a kind of safety some no other files are affective.
Next type use errorlog Then type zap. It should ask do you what to zap and the name the file Yes or No.
Next type Pack. to reclaim the blank space, same pack in database maintaince.
When your done type exit to leave command and put you back into logic.
Any *.dbf file can be cleared in LOGic the same way, be careful. Once zapped you can't get the data back unless it's backed up.
TIP: If you want to see how many *.dbf files you have and how big they gotten and when they were last updated "Type dir" in command screen
Page 75 - Subj: How to Resize the Mode Field
From: [email protected] (Richard Thorne - N5ZC)
Go to Tools > Misc Utilities and then Select > Change size of log fields > Increase the Width of the Mode Field > Click OK
On the Log screen > Unlock the padlock to allow unlock form and layout modifications > then Right click on the field that you want to change.
Page 76 - Subj: How to Reset Contest Score Window
From: [email protected] (Terry Dummler - W7QA)
Question: In the middle of running a contest with the Log Form all set up, the dates are generous before and after the contest. However, I forgot to set the dates when I started logging and had about 40 contacts in the log before I noticed the count being too high. So I went into the contest Set Up and set the dates closer to the actual contest. Then I did the Contest Clear and Rescore. All appeared to be normal, count right etc. However when I logged a new contact and finished the logging with either the Return Key or CTRL N for the next contact the count in the Contest Score window changed and reflected only those contacts that were logged AFTER I had changed the date. How can I get the Contest Clear and Rescore to become permanent?
From: [email protected] (Dennis - W4AZY)
Answer: Just close the log window before rescoring the contest, and all will be well.
Page 77 - Subj: How to Manage Log Forms
From: [email protected] (Terry Dummler - W7QA)
Question: In the FORMS, LOG, SELECT LOG FORM window there are four choices shown. Default, Main, Userfields and WQ7A. These open normally when chosen. I also have two forms set as defaults to open, WQ7A and MARAC and these open upon program start up.
How do we really "manage" the choices in this window. The Manage Log Form Files really doesn't seem to allow any choices. What I would like to do is be able to add and delete forms to the FORMS, LOG, SELECT LOG FORM window.
From: [email protected] (Art Tan - AB4RL)
Answer: When you select Forms|Log it brings up a list of "non-contest" logforms. Unlike Reports which can now be grouped into QSLing, Contesting, Favorites, etc., Log Forms are either "contest" or "non-contest." To change from one to the other just open up any form and go to Log|Setup|Contest Setup and either check or un-check the "Contest Mode On" box.
All forms show up under Forms|All Log Forms and only the few non-contest forms show up under Log|Forms. The Manage Log Forms box is just a handy way to bring up all the log forms.
Page 78 - Subj: Printing Labels
From: [email protected] (Roy - ON6FT)
Question: I want to print labels with following requirements on each page:
- no upper line ( ... page nr. ... printed on "date"....)
- format A4 paper (211 x 297 mm)
- equal partition per page: 3 columns with 7 labels each consequently: 21 labels (each 42,4 x 70,3 mm) per page
How do I resolve this problem? This size does not appear in the LOGic6 label list?
From: [email protected] (Joe - NA9A)
Answer: Your printer properties will be used to select your A4 paper size. Find a LOGic label report close to what you want so that the information (addresses or QSL info) will already be programmed into the form. Using Windows Explorer or something to make a copy of that report and then rename the copy with any new name of your choice (keep same extension in name). I think there are two reports with the same name but different extensions (rpt & fmt?).
Then in LOGic, go to the menu bar and select File/Print/Modify report. Select the report with the new name that you just created.
Drag the bottom of the upper modification window down so you can see the whole label and the two or three "bars" above and below the label. Left-double-click on the left end of the DETAILS bar (left of that little black pyramid). That will open a dialog box where you can enter the height of the label that you want. I don't recall seeing metric dimensions so you may have to convert to decimal inches. There is also a top bar (I don't recall its name) that you can slide up (left-click and drag) to cover the top header with the page number and date.
Then select File/Page Setup at the menu bar and an image of the whole label sheet will appear. Change the spacing between labels, number of labels across etc. to your liking. Finally, with more clicking and dragging, move around the programmed information to your liking and save it under that same new name you created. When you click on any item, moving it is much more precise using your arrow keys. Before you save it - or later again in the modification screen, you can have fun with the various tools available so you can insert pictures, graphics, colors and fonts into your masterpiece.
After exiting the modification screens, test your new format by selecting it at (I think) the QSLing menu selection and print it to your screen. What you see is what you'll get and it most likely will require tweaking.
Customizing reports and labels can really get your creative juices flowing.
Page 79 - Subj: DXCC Spots Configuration
From: [email protected] (Hank - AA4HP)
Question: I have a couple of DXCC submissions now, and they currently track, band, and mode, but not band/mode (to clarify: I work them on 20 ssb, and 15 cw, I have two modes and two bands confirmed when I get the card, but working on 20 cw and 15 ssb gains no additional credit, even for the Challenge Award). Does the setup in Logic not understand this, or do I have it configured incorrectly, or maybe I don't understand the rules.
From: [email protected] (Art - AB4RL)
Answer: LOGic does not understand the way the DXCC Challenge works, nor does it need to. Basically the Band Table gives you total control via the "1234" settings. If you want to track everything, then by all means use 1234. If you really want to just track spots in the Spot Log by Band and Mode but not Band/Mode then just put "23" or "123" in each of the boxes. Heck, if you don't have antennas on certain bands, leave the boxes for certain bands completely blank. Then, spots on those bands won't even show up as needed in the spot log.
Page 80 - Subj: Widening "DESCR" in Spot Log
From: [email protected] (Jack - K4WSB)
Question: Is there any way to increase the number of characters shown in the description field in the spot log? I would like to show the entire name of the country in question rather than having is cut off mid word.
From: [email protected] (Art - AB4RL)
Dennis came back with the answer and YES(!) it can be done.
----- Forwarded message from PDA <[email protected]> -----
No problem to make it larger.
*Close all windows. Go to
tools/advanced/database commands.
*Type
USE SPOTS EXCLUSIVE
MODIFY STRUCTURE
Change the size of the DESCR field.
-----------------------------------------------------------
I changed the width of my DESCR field to around 25 characters and now I can see the whole entity name.
"LOGic Tips and Tricks"
is maintained and edited by George Vincent K3GV, revised April 20, 2003
"If it isn't LOGic it isn't LOGging"