Hello all, on the last update I have to import some ADIF data but Import button does not made nothing.
This has been tested on two differents computers with the same result.
Thank you so much!!
Fernando Gomez - EA7KJE
ea7kje@gmail.com
Spain
Log4OM 2.18.0.0 don't import ADIF files
- G4POP
- Log4OM Alpha Team
- Posts: 10807
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Re: Log4OM 2.18.0.0 don't import ADIF files
Perhaps you had a corrupt download it works for me
73 Terry G4POP
Re: Log4OM 2.18.0.0 don't import ADIF files
Well I don't know but what does not work is the function of the import button... This don't do nothing after press "Import" and consequently the data on file has not been readed. I don't know if I not described correctly.
This is something that I and my friends have made sometimes when by example we have forget launch Log4OM but we made some contacts with WSJT-X.
Anyway I have downloaded the new version again, installed and tested again with the same result. Ahm and I have tested this on the computers of my friends via TeamViewer on where they or I download her owns new version software, so mine is not a problem of downloaded corrupted files, I have not used my downloaded file.
I have tested this with two file extensions like .adi and .adif...
This is something that I and my friends have made sometimes when by example we have forget launch Log4OM but we made some contacts with WSJT-X.
Anyway I have downloaded the new version again, installed and tested again with the same result. Ahm and I have tested this on the computers of my friends via TeamViewer on where they or I download her owns new version software, so mine is not a problem of downloaded corrupted files, I have not used my downloaded file.
I have tested this with two file extensions like .adi and .adif...
- DF5WW
- Log4OM Alpha Team
- Posts: 2035
- Joined: 02 May 2013, 09:49
- Location: Kraam, Rhineland Palatinate, Germany
- Contact:
Re: Log4OM 2.18.0.0 don't import ADIF files
Rename the ADIF file to "Test.adi". Could be possible the filename is too large.
73´s .. Juergen ... ALT-512 SDR (10W) , 50 m random wire at SG-211 autotuner, 2 x Xiegu G90 (20W HF TRX) one as portable Radio. Also TS-790E (40 W) for VHF/UHF with X-50 vertical and Duoband 4-Element LPDA.
Re: Log4OM 2.18.0.0 don't import ADIF files
Renamed but still happen the same... nothing!!
Re: Log4OM 2.18.0.0 don't import ADIF files
Same problem for me. A simple adif file with 1 entry, clicking on Import does nothing. It used to work fine until this update.
- G4POP
- Log4OM Alpha Team
- Posts: 10807
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Re: Log4OM 2.18.0.0 don't import ADIF files
Well its working here so send support requests to lele or me
73 Terry G4POP
Re: Log4OM 2.18.0.0 don't import ADIF files
Emailed Lele a support request, along with a sample test.adi file.
73 Ian VK1DI
73 Ian VK1DI
Re: Log4OM 2.18.0.0 don't import ADIF files
Hi, also I have encountered the problem after replacing the version V2.17.0.0 with that Version 2.18.0.0
so after installing and finding myself without my contacts I had to redo a new database and then change my name.
Only then did the IMPORT button do everything normally.
so after installing and finding myself without my contacts I had to redo a new database and then change my name.
Only then did the IMPORT button do everything normally.
Re: Log4OM 2.18.0.0 don't import ADIF files
Hi,
I did some testing for someone with the same problem and it seems that this problem only occurs with an ADIF that only contains one record (QSO). In that case version 2.17 works as expected, but in v 2.18 nothing happens.
I tried the same with an ADIF with 2 records and then the import works in both v2.17 and v2.18 without any problems
How many records were there in the ADIF you were trying to import?
I did some testing for someone with the same problem and it seems that this problem only occurs with an ADIF that only contains one record (QSO). In that case version 2.17 works as expected, but in v 2.18 nothing happens.
I tried the same with an ADIF with 2 records and then the import works in both v2.17 and v2.18 without any problems
How many records were there in the ADIF you were trying to import?