Following a few instances over the past two years where changes I made on the conventional frequencies tab in EZ Scan produced erroneous results, I did some testing this week to better understand what was happening.
Bottom Line: If a frequency change was made to an existing object on EZ Scan's conventional tab, the change looked OK on the screen but was applied to the wrong object if the list was not sorted by the "Rec#" field.
For test purposes, I created a list of 10 conventional frequencies from 400-409 MHz in 1 MHz steps and imported it into a fresh configuration (V-Scanner Folder) from EZ Scan's "Conventional Frequencies" tab. Each frequency was randomly assigned an Alpha Tag letter (A-H). To keep things simple, the import contained no other fields aside from Frequency and Alpha Tag.
Following import, I sorted the list by Alpha Tag on the Conventional Frequencies tab, and then changed one of the frequencies by clicking on it and entering a new frequency. All looked fine, but after re-sorting the list by Rec# I discovered that the frequency of a different object had been changed, rather than the one I had clicked on.
The only exception was when I changed the frequency of Rec# 00005, which by chance remained in the same position within the list regardless of whether it was sorted by Rec# or Alpha Tag. But after changing the frequency of this object I re-sorted the list by frequency, causing the object's position to move. A second frequency change was then made, and it got applied to the wrong object.
In many but not all cases, EZ Scan mis-applied the frequency change to the record which had been immediately below the one I edited. Fields other than Frequency could be edited properly, regardless of sort order.
My test data file is attached to this message in case anyone wishes to try it, but be sure to us a fresh V-Scanner folder so as not to corrupt your active one. I'd be curious if your results are the same or if it happens with EZ Scan versions for other Whistler scanners as well. I couldn't find any past forum discussions.
Bottom Line: If a frequency change was made to an existing object on EZ Scan's conventional tab, the change looked OK on the screen but was applied to the wrong object if the list was not sorted by the "Rec#" field.
For test purposes, I created a list of 10 conventional frequencies from 400-409 MHz in 1 MHz steps and imported it into a fresh configuration (V-Scanner Folder) from EZ Scan's "Conventional Frequencies" tab. Each frequency was randomly assigned an Alpha Tag letter (A-H). To keep things simple, the import contained no other fields aside from Frequency and Alpha Tag.
Following import, I sorted the list by Alpha Tag on the Conventional Frequencies tab, and then changed one of the frequencies by clicking on it and entering a new frequency. All looked fine, but after re-sorting the list by Rec# I discovered that the frequency of a different object had been changed, rather than the one I had clicked on.
The only exception was when I changed the frequency of Rec# 00005, which by chance remained in the same position within the list regardless of whether it was sorted by Rec# or Alpha Tag. But after changing the frequency of this object I re-sorted the list by frequency, causing the object's position to move. A second frequency change was then made, and it got applied to the wrong object.
In many but not all cases, EZ Scan mis-applied the frequency change to the record which had been immediately below the one I edited. Fields other than Frequency could be edited properly, regardless of sort order.
My test data file is attached to this message in case anyone wishes to try it, but be sure to us a fresh V-Scanner folder so as not to corrupt your active one. I'd be curious if your results are the same or if it happens with EZ Scan versions for other Whistler scanners as well. I couldn't find any past forum discussions.
