Has anyone come up with a patch for this problem yet? Keep The Faith, Jim From [EMAIL PROTECTED] Thu Jul 14 07:11:51 2005 From: [EMAIL PROTECTED] (WA9YSD) Date: Thu Jul 14 07:21:45 2005 Subject: [Dxbase] WB9CIF/J6 ,Spots, Prefix/WPX Message-ID: <[EMAIL PROTECTED]>
What is also happening WB9CIF/J6 if you make a correction in your log say you entered WB9CIF/J6 then changed it to WB9CIF/EA8, WB9CIF/IT9, WB9CIF/M the log will not change the Prefix or the WPX when you make a correction in the log. Just make the correction to the prefix on the same log entry and see what happens. I have been noticing that when WB9CIF/J6 is spotted on internet packet, and I need that county in the DX info box with the spots tab that spot does not show up in the box. It should show up and highlight in BLUE for a new band country. If the spot goes through as J6/WB9CIF it works just fine. At the end of the original callsign after the SLASH mark is where all the trouble starts and how DXBase program deals with it. I am not using anything like an RAC data base and Jim Preston has stated about his problem. there seams to be a common problem through out the program that deal with call signs such as WB9CIF/J6 that has a common thread with a SLASH and a PREFIX folowing a 2 by 3 call. I may be with other shorter or longer call signs, maybe Jim has narrowed it down to what type of call signs are being affected. Some thing is just wrong in the program casue it has prefix issues. Can this be fixed please? Keep The Faith, Jim From [EMAIL PROTECTED] Fri Jul 15 13:22:23 2005 From: [EMAIL PROTECTED] (Joseph Glockner) Date: Fri Jul 15 13:34:39 2005 Subject: [Dxbase] Tnx for your vote at Joe WA6AXE's website Message-ID: <[EMAIL PROTECTED]> Tnx to all who visited my website and voted on the 2 surveys that I had posted ... Here are the STATS from those surveys. Survey #1 --- Most recent version of DXbase you are using? 2006 90 (77%) 2005 14 (12%) 2004 2 (1%) 2003 7 (6%) 2002 0 (0%) 2001 0 (0%) 2000 1 (0%) 98 0 (0%) DOS 2 (1%) other 0 (0%) 116 Total votes Survey #2 --- Report & Labels that Joe makes - do you use them? Yes - always 33 (35%) Yes - sometimes 32 (34%) Yes - but infrequently 20 (21%) No - but will when I upgrade 2 (2%) No - do not need them 7 (7%) 94 Total votes 73 Joe wa6axe From [EMAIL PROTECTED] Fri Jul 15 23:21:35 2005 From: [EMAIL PROTECTED] (Joseph Glockner) Date: Fri Jul 15 23:33:54 2005 Subject: [Dxbase] DXbase Reflector -- Acceptable Use Policy -- admin Message-ID: <[EMAIL PROTECTED]> As a reminder to all users of the DXbase Reflector, here is the "Acceptable Use Policy" of the DXbase Reflector (quoted from Jack's www.dxbase.com website): This service has been established to promote the open communication among DXbase enthusiasts. It's primary function is to enable subscribers to ask questions and receive answers regarding the use of DXbase. It is not filtered or screened, so what you post will be distributed immediately. For the benefit of all, there are a few general topics that are not condoned or permitted. These include spam, advertising, sarcasm, and general whining. Let's keep the content of the reflector positive in nature and helpful to all. 73 Joe WA6AXE Reflector Co-Administrator From [EMAIL PROTECTED] Sat Jul 16 10:00:38 2005 From: [EMAIL PROTECTED] (WA9YSD) Date: Sat Jul 16 10:10:54 2005 Subject: [Dxbase] Re: Acceptable Use Policy -- admin Message-ID: <[EMAIL PROTECTED]> I am not sure if I understand the policy correctly. Can you please explain in more detail what is ment by "sarcasm, and general whining". Keep The Faith, Jim From [EMAIL PROTECTED] Sun Jul 17 14:09:15 2005 From: [EMAIL PROTECTED] (Ed K1EP) Date: Sun Jul 17 14:21:45 2005 Subject: [Dxbase] ADIF import to DxBase2006 problems Message-ID: <[EMAIL PROTECTED]> I had about four contest (CT adif) logs to import to my DxBase log. I imported the logs using the utility, one after another, without starting up DxBase. When I did run DxBase, I found a number of oddities in the log. I would see several log entry lines that didn't have any QSO data and were grayed (actually red 50%) out. I saw QSO's that were probably wrong because they were in the wrong date order, even after sorting. When I tried to do Initialize Tables, I think I got some non-fatal error, something like "unrecognized bookmark". Initialize Tables only found about 10% of the QSO's in the log. I thought maybe I did something funny, so I reverted back to my saved log (Yes, I made a copy before doing all this). I carefully did the same import process again, importing the logs in a different order. Same results. I then imported the logs one at a time on the original .MDB file, running DxBase between each import to verify that the import went okay. By doing that, the log was fine after the four imports. When I looked at the two files, the bad .MDB file was something like 10% larger in size than the correct log after the imports. Is there anything in DxBase that requires you to run DxBase after an import?? I am pretty sure that I have done multiple imports in the past without any problems like this. Anyone see similar results?
