Jack and Courtney, After using DXBase stand-alone for quite a while, I finally decided = today to try to import my DXLog data into DXBase 2003. I expected there = would be some problems with DXCC country and prefix recognition, and = sure enough there were quite a few records with such problems. I am = prepared to dig through the two logs and manually fix those errors. = However, I am not at all prepared to fix the error with the reported = frequency on each and every record. DXBase has rounded off each = frequency from DXLog to just one significant digit with formats like = 7000.00, 24000.00, 28000.00, etc. The worst ones are the 160m QSOs = which are all logged now as 1000.00 kHz! (Yes, I realize that DXBase = does correctly recognize 1000.00 kHz as 160 meters)
To sniff a bit further into this situation, I imported the DXLog data = (which happens to be in Dbase III format) into Access 97 in order to = look at the original frequency values. DXLog records the frequency in = MHz, so I see entries like 14.246, 7.02, 24.9, etc. Why is the DXBase = import program not able to convert 14.246 to 14246.00, 7.02 to 7020.00, = 24.9 to 24900.00 and so on? The correct original data is clearly = imported into Access 97 (the native DXBase underpinnings), and it would = seem to be a simple operation to move the decimal place and preserve the = integrity of the data when importing into DXBase. =20 Would you PLEASE upgrade your import utility so that I can merge my logs = and get on with operating, rather than spending countless hours = laboriously transferring data from one log to the other. 73, Walt, AJ6T --- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html The reason this message is shown is because the post was in HTML or had an attachment. Attachments are not allowed. Please post in Plain-Text only.---
