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

Notification

Icon
Error

2 Pages12>
Logic 9 Update 9.20.5 Help !!
LU1BJW
#1 Posted : Monday, April 27, 2020 5:30:55 PM(UTC)
Rank: Advanced Member

Groups: Registered
Posts: 39
Location: Buenos Aires, Argentina

Thanks: 13 times
Was thanked: 3 time(s) in 3 post(s)
Hi Dennis,

Last week I updated to Version 9.20.4 and problems started:
Specifically when I run the "callbook batch update" rutine the systems stops and sometimes closes.

Today I decided to update to Version 9.20.5 and the problem it is worse.
Whem I try to save a qso after edit it, a warning appears like "Member Getlogicfieldinfo does not evaluate to an object".
Them shuts down the program.
When I run again the edited QSO are saved with changes.

Other warnings appear when I tried to edit a qso like:

Error 1943 "Member GETLOGICFIELDINFO does not evaluate to an pbject"
has occurred in program.
FMT_SAFETYLOG_REC, Line 46

If I Ignore change for the following :

Error 52 "No table is open inthe current work area."has occurrred in program"
_5R616DCM.NEXT_REC Line 7.

If I Ignore change for the following :
Error 12
"Variable "Call"is not foundm has ocurred in program
_5R616DC7M.UPDATE_RELATED_FORMS, LINE 4

What do you suggest?

Best 73
Horacio - LU1BJW
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 : Monday, April 27, 2020 7:27:31 PM(UTC)
admin

Rank: Administration

Groups: Administrators, Beta Testers
Posts: 2,393
Man
Location: Auburn, GA

Thanks: 518 times
Was thanked: 344 time(s) in 270 post(s)
Hi Horacio:

Sorry for the problem.

Please download and install the 9.20.5 update again. I found (with your help) a scenario where it would error when there were no user-defined fields in a QSO and the SafetyLog is on. I couldn't reproduce that exact error.

Please try the update to the update, and let me know. If it still happens, please describe step-by-step how to reproduce it. I tried editing say Name or CQZ and then saving, no problems.

I have not changed anything in the Callbook Batch Update in a long time. Which callbook are you using?

Tnx & 73,

Dennis WN4AZY

1 user thanked WN4AZY for this useful post.
LU1BJW on 4/30/2020(UTC)
LU1BJW
#3 Posted : Monday, April 27, 2020 8:55:12 PM(UTC)
Rank: Advanced Member

Groups: Registered
Posts: 39
Location: Buenos Aires, Argentina

Thanks: 13 times
Was thanked: 3 time(s) in 3 post(s)
Hi Dennis,

I did what you said, I installed the 9.20.5 update again, and the same errors continues appears and crash the programe as before.
I'm using QRZ.com callbook with a XML paid subscription (before this worked good) and the edition of qso too.
I will publ;ish another post with description of what I do.
Do I have to install a previous update?

Looking forward to your reply,
Thank your very much.

Horacio
LU1BJW
#4 Posted : Monday, April 27, 2020 9:11:59 PM(UTC)
Rank: Advanced Member

Groups: Registered
Posts: 39
Location: Buenos Aires, Argentina

Thanks: 13 times
Was thanked: 3 time(s) in 3 post(s)
Hi Dennis

Step by step.
I open the program.
In the entry window I fill the field of QSL RCV with and "R" and the field LOTW with and "R".
Once is ready to save a push the Disket Icon
The first error square appears as: Program ERROR "Member GETLOGICFIELDINFO does not evaluate to an object"
After ignoring twice the program shuts down.

If instead of pushing the disket Icon I click on the next qso arrow,
The first error square appears as: ERROR Error 1943 "Member GETLOGICFIELDINFO does not evaluate to an pbject"
has occurred in program.
FMT_SAFETYLOG_REC, Line 46
Attempt to continue? Yes or no?
If I click NO the program shuts down.

After each shut down, the program runs the CLEAN rutine and Initialialized with the indexing.

Horacio


LU1BJW
#5 Posted : Tuesday, April 28, 2020 8:49:27 AM(UTC)
Rank: Advanced Member

Groups: Registered
Posts: 39
Location: Buenos Aires, Argentina

Thanks: 13 times
Was thanked: 3 time(s) in 3 post(s)
Good morning Dennis,


As you see now the main problem it is not the Callbook butch update...

After almost 35 years of Logic I continue to trust this excellent tool that manages the 50,000 contacts of a lifetime of activity.
I am very active these days of quarantine. Using the software every day.
With this problem I can't use it, and I don't want to make it worse either.

So will it be possible to install a previous version?
That can damage the database?

Another possibility is that you see my desktop running Logic through a Teamviewer session.
Buenos Aires is -3 hours UTC. Or it is 1 hour later than New York city time.

Looking forward to your reply

Thanks
Horacio
n8gls
#6 Posted : Tuesday, April 28, 2020 9:44:10 PM(UTC)
bwilliams

Rank: Advanced Member

Groups: Registered
Posts: 281
Location: Mentor, OH

Thanks: 66 times
Was thanked: 57 time(s) in 51 post(s)
Hi Horacio,

I'm getting similar errors, I believe due to an improvement done to the SafetyLog feature. Try stopping the SafetyLog feature (go to Tools, Setup, Misc Ham Setup) and delete the SafetyLog file name from the field. This will stop the errors until there is a fix.

73 de Brad, N8GLS
2 users thanked n8gls for this useful post.
WN4AZY on 4/29/2020(UTC), LU1BJW on 4/30/2020(UTC)
WN4AZY
#7 Posted : Wednesday, April 29, 2020 2:48:44 PM(UTC)
admin

Rank: Administration

Groups: Administrators, Beta Testers
Posts: 2,393
Man
Location: Auburn, GA

Thanks: 518 times
Was thanked: 344 time(s) in 270 post(s)
You can go back to 9.20.4 without issues.

Turning off the safetylog should also do it.

Still cannot duplicate the problem here.

Tnx & 73,

DH
1 user thanked WN4AZY for this useful post.
LU1BJW on 4/30/2020(UTC)
LU1BJW
#8 Posted : Wednesday, April 29, 2020 5:44:18 PM(UTC)
Rank: Advanced Member

Groups: Registered
Posts: 39
Location: Buenos Aires, Argentina

Thanks: 13 times
Was thanked: 3 time(s) in 3 post(s)
Brad and Dennis,

I click "None" in Miscellaneous setup menu and the Safetylog(TM) file name is blank.
Then I run the "Callbook batch update" and edit some fields with on the entry window with no errors at all.

If everything continue without errors I will continue using the program with 9.20.5 version.
And in absence of safetylog backup I 'll continue with the daily backup of the complete Logic folder.

And let's wait for the next update.
Thanks both of you for the support.

Best 73
Horacio
p.s. Brad we had a qso on 10 meters in Feb 4th 1990!
n8gls
#9 Posted : Wednesday, April 29, 2020 8:07:29 PM(UTC)
bwilliams

Rank: Advanced Member

Groups: Registered
Posts: 281
Location: Mentor, OH

Thanks: 66 times
Was thanked: 57 time(s) in 51 post(s)
Horacio,

I usually check to see if I have worked the person I'm responding to but forgot to do that ! We did work on 04 Feb 1990, I even got a QSL card from you on 25 Mar 1990, I sent you one on 20 Apr 1990 so hope you received it !! That was a long time ago and hope to work you again!


Dennis,

Thanks for looking at this. I can send more snippets if you need them.

73, Brad
n8gls
#10 Posted : Wednesday, April 29, 2020 9:00:36 PM(UTC)
bwilliams

Rank: Advanced Member

Groups: Registered
Posts: 281
Location: Mentor, OH

Thanks: 66 times
Was thanked: 57 time(s) in 51 post(s)
Dennis,

Not sure if this will help any but here is the SafetyLog file that I was using at the time of the errors. I only used this feature for a very short time so the file is very small.

Note that SafetyLog exported without any errors prior to the share change. When I started LOGic after installing the update here is what I did;

Note all the entries prior to the last two with TM6M were BEFORE the change.

The first TM6M entry (second from the bottom) I manually added LOTW_QSLRDATE, as soon as I moved out of the QSO LogForm, LOGic threw the errors. I closed out of LOGic, did a clean and launched LOGic again.
The second TM6M entry (last one at the bottom) I manually added LOTW_QSLRDATE, moved out of the Logform and LOGic threw the same errors.

So manual changes to existing QSO's seemed to trigger the errors. May not matter at all but I did notice the case of the entries was lower/upper case before the change, after the change the case was all upper. You'll see in the adi file. Also, when I added a LOTW_QSLRDATE I did NOT set the Lotw Rcvd flag to show it was received, also may not matter but worth mentioning.

I'll try logging a new QSO to see if that throws any errors and report back.

Update: Just logging a new QSO also throws the same errors, so not related to changing a prior QSO.

Brad, N8GLS
File Attachment(s):
N8GLS-SAFETY.ADI (8kb) downloaded 2 time(s).
WN4AZY
#11 Posted : Friday, May 1, 2020 9:26:46 AM(UTC)
admin

Rank: Administration

Groups: Administrators, Beta Testers
Posts: 2,393
Man
Location: Auburn, GA

Thanks: 518 times
Was thanked: 344 time(s) in 270 post(s)
Hi--

The ADIF file header is old. Exit LOGic. Delete the safetylog file. Lot something. A new one will be created. If the header still says

Quote:
This file is ADIF compatible except as noted:

* The DXCC field is not exported in order to save ADIF code lookup time.
However, LOGic will calculate DXCC based on callsign when importing.

* All of LOGic's user-defined fields are exported under the tag USERFIELDS
LOGic will import this correctly, but it will be ignored by
other programs.


then you do not have the latest logic.exe, and probably need some new needed libraries as well. I redownloaded and installed the 9.20.5 update from the server, and it is OK.

Could someone who is getting the "Member GETLOGICFIELDINFO does not evaluate to an object" error please perform the following test for me?

Go to tools/advanced/database commands. Type in or copy/paste the following command and press {Enter}

? global.safetyuserfields.GetLogicFieldInfo("VE PROV")


It should display

(object)

Thanks,

Dennis WN4AZY
LU1BJW
#12 Posted : Friday, May 1, 2020 9:53:37 AM(UTC)
Rank: Advanced Member

Groups: Registered
Posts: 39
Location: Buenos Aires, Argentina

Thanks: 13 times
Was thanked: 3 time(s) in 3 post(s)
Hi Dennis,

In may case displays:

Error 1925
Unknown member SAFETYUSERFIELDS.

73
Horacio
1 user thanked LU1BJW for this useful post.
WN4AZY on 5/2/2020(UTC)
n8gls
#14 Posted : Friday, May 1, 2020 12:22:25 PM(UTC)
bwilliams

Rank: Advanced Member

Groups: Registered
Posts: 281
Location: Mentor, OH

Thanks: 66 times
Was thanked: 57 time(s) in 51 post(s)
Dennis,

Deleted the adif safety file, re-installed 9.20.5, created new SaftetyLog, logged a couple fake QSO's and still got the errors.

The "new" adif files header looks good and says "This file is ADIF compatible" with no exceptions.

Also the getlogicfieldinfo("VE PROV") displays (object).

I am clueless why the previous adif file had compatibility exceptions, I had installed 9.20.5 before, twice in fact. Think I'll reboot the PC and try this again.
LOGic.exe file properties has a date of 04/27/2020, v9.20.5

Brad, N8GLS

Update: Did disk clean-up and cold booted PC, tried above again and still got the error.
1 user thanked n8gls for this useful post.
WN4AZY on 5/2/2020(UTC)
WN4AZY
#15 Posted : Saturday, May 2, 2020 8:37:23 PM(UTC)
admin

Rank: Administration

Groups: Administrators, Beta Testers
Posts: 2,393
Man
Location: Auburn, GA

Thanks: 518 times
Was thanked: 344 time(s) in 270 post(s)
Ok, I don't know what is going on then. You have the right LOGic.exe and the library.

When you log, are you still getting the error "Member GETLOGICFIELDINFO does not evaluate to an object"

Could I impose on you to log into your machine again?
http://www.hosenose.com/remote_support.aspx
770-307-1496 or give me a good time to call.

Tnx & 73,

Dennis WN4AZY

WN4AZY
#13 Posted : Saturday, May 2, 2020 8:38:19 PM(UTC)
admin

Rank: Administration

Groups: Administrators, Beta Testers
Posts: 2,393
Man
Location: Auburn, GA

Thanks: 518 times
Was thanked: 344 time(s) in 270 post(s)
Originally Posted by: LU1BJW Go to Quoted Post
Hi Dennis,

In may case displays:

Error 1925
Unknown member SAFETYUSERFIELDS.

73
Horacio


That's because you have SafetyLog turned off.

Tnx & 73,

Dennis WN4AZY
1 user thanked WN4AZY for this useful post.
LU1BJW on 5/3/2020(UTC)
LU1BJW
#17 Posted : Saturday, May 2, 2020 9:17:16 PM(UTC)
Rank: Advanced Member

Groups: Registered
Posts: 39
Location: Buenos Aires, Argentina

Thanks: 13 times
Was thanked: 3 time(s) in 3 post(s)
Ok, I don't know what is going on then. You have the right LOGic.exe and the library.

When you log, are you still getting the error "Member GETLOGICFIELDINFO does not evaluate to an object"

Could I impose on you to log into your machine again?
http://www.hosenose.com/remote_support.aspx
770-307-1496 or give me a good time to call.

Tnx & 73,

Dennis WN4AZY

Hi Dennis,
The message above for me or for Brad?
Regards
Horacio
LU1BJW
#20 Posted : Sunday, May 3, 2020 11:47:36 AM(UTC)
Rank: Advanced Member

Groups: Registered
Posts: 39
Location: Buenos Aires, Argentina

Thanks: 13 times
Was thanked: 3 time(s) in 3 post(s)
Good morning:

Update:
After disable the safetylog feature going to Tools, Setup, Misc Ham Setup and deleting the SafetyLog file name from the field.
Re-installing the 9.20.5 Version when Dennis suggested.

I can edit the contacts and run the "Callbook Batch update"without any problem.

I'm available to make any other test.
73

Horacio

n8gls
#16 Posted : Sunday, May 3, 2020 2:35:42 PM(UTC)
bwilliams

Rank: Advanced Member

Groups: Registered
Posts: 281
Location: Mentor, OH

Thanks: 66 times
Was thanked: 57 time(s) in 51 post(s)
Hi Dennis,

Quote:
When you log, are you still getting the error "Member GETLOGICFIELDINFO does not evaluate to an object"


Yes, I still get that error. I tried various other things like closing all other software down, closing all the links to LOGic then re-booting and re-launching LOGic. Still the error, sometimes it generates one immediately after the other but stops at two. I'm clueless, thought maybe something with the SafetyLog file location, changed that and still the same.

Quote:
Could I impose on you to log into your machine again?
http://www.hosenose.com/remote_support.aspx
770-307-1496 or give me a good time to call.


No problem, how about Monday afternoon ?? If you have a time preference let me know otherwise I can call ahead.

Thanks for the help !!

Brad
WN4AZY
#21 Posted : Sunday, May 3, 2020 4:57:04 PM(UTC)
admin

Rank: Administration

Groups: Administrators, Beta Testers
Posts: 2,393
Man
Location: Auburn, GA

Thanks: 518 times
Was thanked: 344 time(s) in 270 post(s)
Sorry, tomorrow isn't good. Anytime Tuesday AFAIK. Or if you want to call this evening.... Leave a message and I'll call right back.

Tnx & 73,

Dennis WN4AZY
WN4AZY
#18 Posted : Sunday, May 3, 2020 6:38:24 PM(UTC)
admin

Rank: Administration

Groups: Administrators, Beta Testers
Posts: 2,393
Man
Location: Auburn, GA

Thanks: 518 times
Was thanked: 344 time(s) in 270 post(s)
Hi Horacio:

Originally Posted by: LU1BJW Go to Quoted Post
O

Hi Dennis,
The message above for me or for Brad?
Regards
Horacio
Sorry, it was for Brad. I didn't expect you to make a long distance call, but I appreciate it!

Tnx & 73,

Dennis WN4AZY
Users browsing this topic
Guest
2 Pages12>
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.135 seconds.