Hi Mauro, hope you are well !!

If your a user of LoTW, LOTWRDATE and LOTWSDATE consume 38 characters in USERFIELDS and so would have an impact on it's total character limit of 255. They can be disabled in Tools/Setup/Logfields if they provide no benefit.

The USERFIELDS character limit of 255 does fill up quickly depending on how many you have set-up and enabled, the majority of my QSO's approach 200 characters, many are at 230 characters, so I need to watch the limit and weigh the benefit of all those fields I'm capturing. LOTWRDATE has been a huge benefit to me with sorting out discrepancies in LoTW, LOTWSDATE is too new. Of course every user will have a differing opinion but all have the option to disable one or both of them if desired.

73 de Brad, N8GLS

Hi Brad,
here everything is fine thanks and I hope for you too.
Thanks for the answer I imagined. In fact there are too many characters busy and I can't understand which application can be done. As far as I'm concerned, LOTW works perfectly and I don't need to check anything. I wanted to ask how to disable this automatic function and you anticipated me and thank you. Did I remove the flag on enable? into Logfields so my Logic will no longer use this automation, freeing up useful spaces in the 255-character record.
Is there a safe system also to delete LAT and LON data from the archive ??? There is a .PRG that can do this in the whole archive.
With gratitude for the support.
73's de IKØCHU Mauro
***

Hi Brad,
also I a long time ago I asked Dennis if it was possible to increase the 255 characters but he replied that 255 is the maximum limit imposed by the programming language. The number of fields allowed in the entry forms are also limited. I got over this by making forms for each DXCC that has a lot of awards to handle. In this way I can manage many awards but occupying the 255 characters only with the data necessary for that DXCC. I am very happy and by now I'm used to this log management.
I still have to solve a few things that I will shortly expose to Dennis if he can advise me on how to manage what I would like to do.
For LAT and LON it is not possible with the Mass Change function because there are so many variables. I think you need a .prog that eliminates, for example, all the strings | LAT: 12,20 etc freeing up other characters. I'm bringing this data back from Logic8. For now I take them off by hand if I happen to find them on the record.
Hello and 73's Mauro IKØCHU
***

Hi Brad,
I don't think your syntax can work. The use of quotes in this case indicates only two spaces and not two variable numerical values. Here it needs the "hand of the boss" hihi
I like to use Logic as a tool to better manage an office with dynamism. The only difference is that there is no user and the best results have to satisfy myself. I try and enjoy spending time with it, considering that I don't understand much about programming. Perhaps more correct to say that I like to analyze the problem to be able to solve it perhaps in a theoretical way, hoping that Dennis can evaluate the question useful for all users of Logic.

IKØCHU Mauro
***

Hi Brad,
I inform you that remove the flag on Enable? and removing the flags on import and export adif both on LOTWSDATE and LOTWRDATE does not affect the recording of the dates in the qsos record. The dates are placed the same.
So I would ask Dennis to prepare, if possible, an ON / OFF setting in order to activate or eliminate this function which I find very invasive on the 255 characters. I would also like to know what use can be made of these dates in managing the logbook.
Thanks for any feedback.
73's de IKØCHU Mauro
***