[LOGic] Logform Issue

[J.A. Wolf, MD, K6JW]

Thanks! I'll try this. I hadn't thought of using the laptop this way.
--Jeff, K6JW


----- Original Message ----- 
From: "Mel Martin" <ve2dc at videotron.ca>
To: "LOGic is open to all radio amateurs for discussion of LOGic logging 
program" <logic at mailman.qth.net>
Sent: Saturday, January 03, 2009 12:59
Subject: Re: [LOGic] Logform Issue


> Here's what you need to do.
>
> Share the folder Logic8 on the main computer with the sharename logic (or 
> whatever)
>
> Install Logic on the laptop
>
> To access remote instances of Logic you need to modify the shortcut to
>
> Program data=logdata;data
>
> It will probably look like (all on one line):
> C:\logic8\logic.exe 
> data=\\maincomputer\logic\logdata;\\maincomputer\logic\data
>
> You can then select the forms you want to open on the laptop as this data 
> is remembered locally.
>
> Also, put single quotes around the UNC paths if there are any spaces.
>
>
> J.A. Wolf, MD, K6JW wrote:
>> Nope -- still not quite right.
>> What I WANT to do is to use the SAME database, but a different screen 
>> layout more suitable to the laptop single monitor instead of the home 
>> dual monitors. I should be able to load a specific logform to do this, 
>> but with reference to the same log database. There doesn't seem to be any 
>> easy way to do this.
>> --Jeff, K6JW
>>
>>
>> ----- Original Message ----- From: "N6FM Ben" <n6fm at oregonfast.net>
>> To: "'LOGic is open to all radio amateurs for discussion of LOGic logging 
>> program'" <logic at mailman.qth.net>
>> Sent: Friday, January 02, 2009 11:23
>> Subject: RE: [LOGic] Logform Issue
>>
>>
>>> OK, I think you mean that you wish to use a separate log database for 
>>> the
>>> home station than the remote station? If you wish to use a separate 
>>> database
>>> for remote contacts vs local contacts, then I think what you would have 
>>> to
>>> do is define a new shortcut for the program and add the parameters in 
>>> the
>>> command-line specifying the location of the desired log database (DATA
>>> perameter). Then you would restart the program each time using the 
>>> different
>>> shortcuts.
>>>
>>> I don't know any other way to switch databases. Someone else might.
>>>
>>> I understood your question:
>>>
>>>>   My question is whether there is any easy way to close one logform
>>>> and load another without first closing every window in one logform
>>>> before loading the next, so they're not one on top of the other?
>>>
>>> ...to mean that you wanted to just that, close the log form without 
>>> closing
>>> the other windows and open a different log form. IN any event, the other
>>> forms (I assume forms such as "Other QSOs", "INFO", etc) would apply to
>>> whatever database you were using (LOG.DBF), not a specific log form.
>>>
>>> The logform merely is a means to add QSOs to the database, it is not the
>>> database unto itself. "LOG.DBF" is the actual log.
>>>
>>> Also, look in the docs under "multiple instances of Logic" and 
>>> "networking
>>> and multiple databases"....where it discusses the "DATA" parameter.
>>>
>>> Hope that helps..
>>>
>>> Ben
>>>
>>>
>>> -----Original Message-----
>>> From: logic-bounces at mailman.qth.net 
>>> [mailto:logic-bounces at mailman.qth.net]
>>> On Behalf Of J.A. Wolf, MD, K6JW
>>> Sent: Friday, January 02, 2009 10:21 AM
>>> To: LOGic is open to all radio amateurs for discussion of LOGic logging
>>> program
>>> Subject: Re: [LOGic] Logform Issue
>>>
>>> Hi, Ben.
>>>   Thanks for the quick response. Clicking on that X only closes the data
>>> entry and browse windows. It doesn't close all the other open windows. 
>>> What
>>> I'd really like to do is clear the entire workspace, i.e., also have the
>>> Spot Log and other open windows close, too. There may be no good way to 
>>> do
>>> this, unfortunately, since the "logform" definition appears to include 
>>> just
>>> the data entry and browse windows. Ideally, the "logform" would include
>>> everything on the screen at the time it's closed, but I guess it 
>>> doesn't. I
>>> might have to set up another log database and just move any remotely 
>>> made
>>> contacts to the main log when I get home. Seems awfully cumbersome.
>>> --Jeff, K6JW
>>>
>>>
>>> ----- Original Message ----- From: "N6FM Ben" <n6fm at oregonfast.net>
>>> To: "'LOGic is open to all radio amateurs for discussion of LOGic 
>>> logging
>>> program'" <logic at mailman.qth.net>
>>> Sent: Friday, January 02, 2009 09:41
>>> Subject: RE: [LOGic] Logform Issue
>>>
>>>
>>>> Try the X in the upper right corner of the logform, or select its
>>>> representative icon in the Windows taskbar, right click and choose
>>>> "Close".
>>>>
>>>> Then Click on Forms then All log forms and pick the one you want. You 
>>>> can
>>>> have more than one open at the same time on the same database.
>>>>
>>>> Hope I understood your question correctly.
>>>>
>>>> Ben
>>>>
>>>> -----Original Message-----
>>>> From: logic-bounces at mailman.qth.net 
>>>> [mailto:logic-bounces at mailman.qth.net]
>>>> On Behalf Of J.A. Wolf, MD, K6JW
>>>> Sent: Friday, January 02, 2009 9:12 AM
>>>> To: logic at mailman.qth.net
>>>> Subject: [LOGic] Logform Issue
>>>>
>>>> To All:
>>>>   Happy new year to everyone.
>>>>   Here's my issue to start the new year off with a bang. I run LOGic8 
>>>> over
>>>> two monitors at the home station. I'm setting up for remote access to 
>>>> the
>>>> station, however, and will be doing that access from a laptop. What I'd
>>>> like
>>>>
>>>> to do is to set up a new logform on one screen for when I'm accessing
>>>> remotely. Setting up the new form is easy.
>>>>   My question is whether there is any easy way to close one logform and
>>>> load another without first closing every window in one logform before
>>>> loading the next, so they're not one on top of the other? There doesn't
>>>> seem
>>>>
>>>> (or I can't find) any "close logform" command in the available menus. 
>>>> Am I
>>>> just looking in the wrong place?
>>>>   Is there a way to set up a shortcut that will load the desired 
>>>> logform
>>>> without having to copy the entire logdata directory, which would have 
>>>> the
>>>> undesirable effect of creating a separate log database? I don't want to 
>>>> do
>>>> that.
>>>>   Any advice would be appreciated.
>>>>   Again, a happy and healthy new year to all.
>>>> 73,
>>>> Jeff, K6JW
>>>>
>>>> _______________________________________________
>>>> LOGic mailing list
>>>> LOGic at mailman.qth.net
>>>> http://mailman.qth.net/mailman/listinfo/logic
>>>>
>>>> _______________________________________________
>>>> LOGic mailing list
>>>> LOGic at mailman.qth.net
>>>> http://mailman.qth.net/mailman/listinfo/logic
>>>>
>>>
>>> _______________________________________________
>>> LOGic mailing list
>>> LOGic at mailman.qth.net
>>> http://mailman.qth.net/mailman/listinfo/logic
>>>
>>> _______________________________________________
>>> LOGic mailing list
>>> LOGic at mailman.qth.net
>>> http://mailman.qth.net/mailman/listinfo/logic
>>>
>>
>> _______________________________________________
>> LOGic mailing list
>> LOGic at mailman.qth.net
>> http://mailman.qth.net/mailman/listinfo/logic
>>
>
> -- 
> Mel, VE2DC
> _______________________________________________
> LOGic mailing list
> LOGic at mailman.qth.net
> http://mailman.qth.net/mailman/listinfo/logic
>