JVG said:
I tested some combinations to the WIN96 Web Import and I found that if the field "First Target Channel" has a number of 51 or higher entered into it, it will give the error you described. Interesting enough a value of 50 will load the trunk ID's if you selected them but will not show any frequencies. Of course there is no channel 50, only 0-49 so this makes sense.
Yes, it's the "First target channel" field, telling you to enter a "valid" channel number as the first destination for the frequencies you're importing.
There is, as Jack noted, a small bug in that warning code. It is limiting your input to 0-50, when it should be 0-49. A similar bug exists in the "First target talkgroup subbank" and "First target talkgroup" fields. All three are limiting you to 0 - <number of items>, when they should be 0 - <number of items minus 1>. The bug won't cause any data corruption - later code checks the value internally and won't write past the end of the various lists in a bank.
Entering a "valid" number for the "First target channel" (that is, a number between 0 and 49) will take care of the warning. You should probably enter a number between 0 and <50 minus channels you're importing>, so that all of your channels are actually imported. For example, if you're importing 4 control channels, you could enter a value between 0 and 46. You could actually enter 47, 48, or 49, but you'd only import 3, 2, or 1 channels.
Note that the "First target channel" field is
ignored for EDACS systems. Win96 will always import such systems according to the LCNs listed in the RR database.
-Don
