Hi Dennis,
For about a year I've always upgraded my prefix.table with CTY data updates.
I am pleased with the new change in logic 0.74 on the interaction of the table with the values of CTY.
My question:
Now what am I to do to upgrade to 0.75 with my prefix.table? I must cancel my prefix.table and replace it with the original or I can leave it just as it is now?
I saw that the update creates a file prefixexceptions.xml in the \Logic\data folder. May conflict with my prefix.table already changed?
What is the procedure for updating this file from the website?
Thank you.
73's de IKØCHU Mauro
***

Hi ....
I do not understand what you mean by a new master field.
73's de IKØCHU Mauro
***

Hi Dennis,
I did lots of tests to implement the latest changes.
In fact to me it is that the update is in stark contrast to the dynamic possibilities for the user to interact with the software to suit your needs and often to adapt to serious misconduct. (Little and simple OT example: XX1XXX/P -> PFX= P0 etc..)
My luck was to have tested updates on another computer because if I had done on the computer reserved for radio would be a major problem undermining all the work done over years of use of Logic.
Any substantial change to the structure of the program creates inconvenience to the user who then has to spend his time to replace things as they were before and with much difficulty.
Surely it depends on my stupidity in claim benefits from the program, but as a user I feel compelled to act out my concerns about a product that I like and I like to use it with confidence without being obsessed about losing all my work if I were to commit a slight indiscretion as to not backup or do an upgrade that disrupts everything.
I always wanted Logic filling in a specific field called COUNTRY the description of the DXCC, which I put in my printing QSL, in the format used by the ARRL that should be used, in my humble opinion, as a default for ALL logbook and contests programs.
Probably this was my biggest mistake.
It was not the compatibility that generated the idea of ADIF ??
I do not have much knowledge of programming, but I managed it. Probably the solution adopted is not compatible with the structure of the latest updates.
I am very sorry and I'll stop for now at version .72 waiting for better times.
Sincerely.
73's de IKØCHU Mauro
***

Hi Dennis,
thanks for help me.
If you dont mind i tell you my question step by step one time.

Installing .76 i Always received an error as " PFXINFO is not an object"
The error result when is active the telnet window with the connection at cluster.
Closing the telnet the error is OFF. It's impossible use the spot log.

I used your DB sintax to set all the master flag ON.
I tryied to insert a new exception E51MQT as N Cook I instead of S Cook I. To make this i tryed to duplicate the record, as before was possible, in the prefix table to add also the user flag ON. It was no possible because a popup comeback with this error : UNIQUENESS OF INDEX REC_NO IS VIOLATED. To close only REVERT button must be typed.
Then i tryed at old way. I modified the record E5-N adding XXX,E51MQT, make reidex and all ok.

Is this correct use??
For now that's enough, otherwise too thinly ... hi
Thanks de IKØCHU Mauro
***

Hi Dennis,
I installed .77 and put prefix table flag in off.

I can use SpotLog well as before; no error occurs

I cannot duplicate the DXCC to add new exceptions. I can only add calls in the same record. Of course all doing a fine job.
Now a question ... When the spaces in the DXCC form are finished how to procede to add new one if its impossible create a second record? The .xml file how can be updated? only with new release of CTY on the server or can be done also manually with a form in the program?

A request if possible:
Having updated my prefix file with Others data files from contest programs should be possible to have dupe calls in my prefix table and in your .xml file. It's possible to clean in my table the dupe calls using an external program??
The result would be to have a prefix table as DXCC defined by ARRL and used only by authorized programmer; the .xml files only for the exceptions automatically updated from CTY files or similar files and exceptions by user manual access. Would be interesting insert in the record also the start and end day of exceptions.
Two separate things and you can update, when you want or necessary, the prefix table for all the Logic9 users.

73's de IKØCHU Mauro
***

Sorry. Check Help/about and make sure .77 is installed.

Give me the exact error -- the first one you get.

73,

DH

Hi Dennis,
half hour without error ...
Now i opened spotlog and after twoo minutes i received a strange error :
OLE IDispatch exception code 0 from PDA.Logic.PrefixCallsignDBLockup: (But the error its in italian: Riferimento a un oggetto non impostato su istanza di oggetto...)
I try to translate hi hi ... Object reference not set to an instance of the object ...
The nest was been PFXINFO is not an object
Hope its usefull for you ..
73's de IKØCHU Mauro
***

Hi--

I don't know what is going on. I suspect something with the prefix table. When you update it is supposed to add new fields, but maybe something is wrong there. Can you post your prefix.dbf here or email it to me? If emailing, wait a few hours. We are moving our mail server at the moment.

I also sent you a Skype contact request. We can do teamviewer.

Tnx & 73m,

Dennis

Ok, it seems that User Account Control might be biting us in the butt. The table you sent did not have the new fields added. I let my copy of LOGic add them and am sending it back to you.

Ideally, turn off UAC. Search the C: drive for all instances of prefix.dbf. Delete them, especially the ones in a VirtualStore folder. Then save the attached file to the logdata folder. Do CLEAN UP INDEXES AND TEMPORARY FILES from the Start menu. You should be good now.

If not, there is something else to try.

Tnx & 73,

WN4AZY

Hello Dennis,
while I'm waiting TX3X hi ...
in my testing laptop I got another error message right now. (PFXINFO etc..)
I have basically seen by comparing the spotlog of my desktop, that .77 issued the error latching on spot S79SP.
I pressed the button IGNORE 7 times and immediately displays 3 spot of S79SP.
I do not know if it could be a case.
All this for your information.
73's de IKØCHU Mauro
***