I'm a new user of DXbase and need some advice on how to organise logging. I'd like to run a single log, but i'd also like to be able to identify the QSO done from the base station from the QSO done from the week-end QTH. So far i've used the SPECIAL_1 field to write the QTH name. Does this make sense? Is there a better way to do? In addition, is there a way to log the end time of the QSO? Many thanks. 73 Mauro i2suh From [EMAIL PROTECTED] Mon Oct 11 16:44:41 2004 From: [EMAIL PROTECTED] (FireBrick) Date: Mon Oct 11 16:53:54 2004 Subject: [Dxbase] Advice on how to organise log for 2 locations. References: <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]>
Ask for additional callsign registrations. Ask for I1SUH (which would be your main home station Ask for I1SUH/1 (which would be the week-end qth. Ask for I1SUH/P (which would be for any other place you operate) When at the weekend qth, save that log as I1SUH/1 and then use DXB Import to merge it into your home log. I THINK this will work.... I know I needed three callsigns in my 'Registration' file. and my log uses the info and data as if it's one big single callsign log. Good luck, If you request the reg file, make sure you save it in a separate, safe place at each qth. ----- Original Message ----- From: "Mauro Succi" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Monday, October 11, 2004 3:21 PM Subject: [Dxbase] Advice on how to organise log for 2 locations. I'm a new user of DXbase and need some advice on how to organise logging. I'd like to run a single log, but i'd also like to be able to identify the QSO done from the base station from the QSO done from the week-end QTH. So far i've used the SPECIAL_1 field to write the QTH name. Does this make sense? Is there a better way to do? In addition, is there a way to log the end time of the QSO? Many thanks. 73 Mauro i2suh ______________________________________________________________ Dxbase mailing list Home: http://mailman.qth.net/mailman/listinfo/dxbase Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[email protected]
