logo
Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

Error Message
N0AT
#1 Posted : Thursday, October 17, 2013 9:15:03 AM(UTC)
Rank: Advanced Member

Groups: Registered
Posts: 31
Location: Minnesota

Was thanked: 4 time(s) in 4 post(s)
I upgraded to version 9.0.60.
In one of my logs, I get a log entry.
I make changes to the log entry.
I click the right arrow to go to the next record.
The error message "Variable 'BASECALL' is not found." is displayed.
I click on cancel.
LOGic shuts down.

Sponsor
Note: We receive a commission from Amazon when you purchase via this link. It does not affect your cost. Thank you!
WN4AZY
#2 Posted : Friday, October 18, 2013 2:47:13 PM(UTC)
admin

Rank: Administration

Groups: Administrators, Beta Testers
Posts: 3,097
Man
Location: Auburn, GA

Thanks: 998 times
Was thanked: 497 time(s) in 412 post(s)
Hi--

It looks like one of your log files is from an older version of LOGic.

Try this--

Exit LOGic. Do a CLEAN UP INDEXES AND TEMPORARY FILES. Next, delete all of the .CDX files located in the folder that contains your secondary database. Start LOGic.

Let me know if this doesn't fix it.

Tnx & 73,

Dennis WN4AZY
LA8OM
#3 Posted : Thursday, December 15, 2016 4:42:38 PM(UTC)
Rank: Newbie

Groups: Registered
Posts: 7
Location: Norway

Was thanked: 1 time(s) in 1 post(s)
I have 'always' had the message "Variable 'BASECALL' is not found" displayed during start-up. Have clicked 'Ignore' and proceeded, and it has not caused further issues during the session. (Yes, choosing 'Cancel' closes the program).

However, with new install (9.1.2 and 9.1.6) the "Variable 'BASECALL' is not found"-message comes up always after a record has been updated (e.g. checked in QSL) when navigation to another record in the log.

I tried Dennis' advice above. But did not find any .CDX-files left to delete after the Clean-up. Also, not sure what is meant by the secondary database.
WN4AZY
#4 Posted : Monday, December 19, 2016 9:13:51 AM(UTC)
admin

Rank: Administration

Groups: Administrators, Beta Testers
Posts: 3,097
Man
Location: Auburn, GA

Thanks: 998 times
Was thanked: 497 time(s) in 412 post(s)
Followup for anyone else reading. Apparently LOGic 8 data got copied into LOGic 9. We deleted LOG.DBF & LOG.FPT, reinstalled the update to get a new empty log file, then IMPORTED the LOGic 8 data.
Users browsing this topic
Guest (2)
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

Powered by YAF 1.9.5.5 | YAF © 2003-2011, Yet Another Forum.NET
This page was generated in 0.024 seconds.