|Date:||Sun, 22 Oct 2017 10:16:22 -0400
|From:||"Steven Green" <email@example.com>
another long-term piece of advice.. changing the priv repeatedly will get
you in trouble, too.. you can't track where you've been, or if
":priv:mytable" is really the one you're expecting it to be..
also, putting the priv on the server creates more I/O traffic.. on a busy
network, with a busy paradox app, that can become the prime offender
KISS - keep it simple, stupid.. always good advice :-)
Myrtle Beach, South Carolina, USA
Collectibles and Memorabilia
Vintage Lego Sets and Parts
- and Paradox support, too
"Peter" wrote in message news:firstname.lastname@example.org...
Okay I got my problem solved as far as checking, creating, setting the
The problem is that whenever Pdox is restarted (after setting a new
privdir)it hangs on to that. I would like Pdox to use the new priv dir
just for that session and any other startup use the regular privDir.
Is there a way to reset the privdir when the desktop shuts down? I
cannot do it when the form closes because the user may want to open
another form in that program.
Thank you, anyone.
On 10/18/2017 04:37 PM, Leslie wrote:
> Do NOT look to the registry to solve this problem, that is the wrong
> approach. I have explained many times why people using the Registry
> eventually can screw up the BDE and even if you find a Paradox specific
> setting you will run into the same trouble.
> The golden rule has always been to set your session "variables" at run
> time - do not expect "static" settings to live forever in case something
> occurs to change things - like someone else changing the registry to
> some other value.
> On 19/10/2017 7:30 AM, Peter wrote:
>> 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
>> for me.
>> 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:email@example.com
>>> 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.
> This email has been checked for viruses by AVG.
This email has been checked for viruses by Avast antivirus software.