|Date:||Wed, 18 Oct 2017 14:30:26 -0700
Thank you for the reply.
That is also the approach I have been using but I am running into other
complications so I would like to do it when opening the program
I did make something up yesterday in a form, putting the SetPrivDir() in
the open method and trap for MenuChangingPriv in the menuaction (to
prevent closing.)It is working okay
I tried doing it in a script but the script has no menuaction. So the
SetPrivDir() works but adding any other code (even a "view(PrivDir())")
will result in not working.
I am now looking at the registry and seeing if there is something I
could there instead, via script writing data to the keys. Dangerous area
On 10/17/2017 03:05 PM, modridirkac wrote:
> In a shortcut you can define which private to use.
> c:\app\runtme\pdxwin32.exe -p x:\app\priv1 -w x:\app\db start.fsl
> Something like that.
> "Peter" je napisal v sporočilo news:firstname.lastname@example.org
> It seems each computer has different disk/directory structures. Is it
> unwise to make a directory on the server and a folder for each station
> to serve as the private directory?
> On 10/17/2017 02:04 PM, Peter wrote:
>> I have an app running on a small network. I want each computer to run 2
>> sessions (on separate screens) of Pdox and am wondering the best way of
>> accomplishing that.
>> The current method right now is defining two different private
>> directories in the desktop shortcuts. Is there a better way? Thank you
>> for any ideas.