Hi,

Why would I want or need to use these?

Just curious

--
-----
Anne Wainwright
Please reply to group

I have never used them, so I can't say.

--
Bertil Isberg - CTECH
Paradox buglist:
online: http://hem.bredband.net/bertilisberg/

"Anne Wainwright" <duffaddress (AT) ananzi (DOT) co.za> skrev i meddelandet
news:Xns98C59DDD6C159azopane (AT) 196 (DOT) 25.240.158...

I would guess that you would mostly use them with a Runtime distribution
of an application to ensure that registry settings never/always change.
-e prevents writes to the registry, so if your install script has done
all the work you don't want end-users changing anything
-f forces writes to the registry, so maybe useful if you want your
end-users to be able to customize settings for themselves.

It would be interesting to know which one is higher in the hierarchy if
you use them both!

On 27-01-2007 08:31 Anne Wainwright wrote the following email:

I expect that the one which prevents registry writes could be used with
the pdoxwin.ini related command line options to read and write options
to an ini file rather than the registry. This would be useful in a
situation where users can't write to the registry but can change the
Paradox settings. Otherwise, it could be used alone and changes to
settings would either not be allowed or would be for the session only -
you'd have to test it to see.

I don't know what the point of the force registry writes one would be
other than to ensure changes which are normally written to the registry
get written - but that's the default, so this one might be like -t
option (allows resizing of Paradox window - that's the default, so
what's the point in the command-line option?).

I'm just guessing, never used them.

Liz


Anne Wainwright wrote:

I have found that the registry settings for the BDE (for example memory,
file handles and so on) are not necessarily the same as the settings shown
in the BDE Administrator.

For example, I kept getting "out of memory" problems even though the BE
configuration allowed for lots of file handles (the "out of memory" is a
red-herring for "out of file handles") until I discovered that the BDE
registry settings were wrong, and manually fixed them.

First I heard of the -f flag!!!

"Zal Dabhoiwala" <dabhoiwala (AT) no (DOT) spam.com> wrote

Anne Wainwright wrote:
Somebody at some time must have thought of a use for them ... beats me what
it would be.

----
ChimneySweep(R): Fast(!) table repair at a click of the mouse!
http://www.sundialservices.com

I wonder if this would fix the syncornization between the registry and the
Paradox configuration file. I have had cases where I have had to make a
change to the BDE to get other changes to show up.Seems like th eregistry
and config file get out of sync and the change makes them get back in sync.

Just a thought.

"Zal Dabhoiwala" <dabhoiwala (AT) no (DOT) spam.com> wrote

Could they be a toggle? That is the -e prevents it and the -f allows it..
Just thinking outloud
Craig

"Sundial Services" <info (AT) sundialservices (DOT) com> wrote

"Sundial Services" <info (AT) sundialservices (DOT) com> wrote

Yep, the somebody was the technical specs writer along with the summer
intern programmer who dreamed up this functionality and sold it to the
documentation team. Then the development team had to implement all the
features according to spec. Still, out of millions of Paradox installs,
only one currently uses these flags. (Okay, I made that up, but it sounded
good.)

Hi,

the -e switch helped me a lot: after installing Win XP (and Paradox 8), all
changes I made in "Preferences" were successfully written into Registry.
However, at the same time pdoxwork.ini file has been created on exit (almost
empty, with 2 lines or so). Next time Paradox started, it did not read the
preferences from the Registry, but from this stupid file. I did not find
any way how to stop Paradox creating this file, so in the end I made all
neccessary changes manually in Registry, and since then I always start Paradox
with -e -n switches to ensure that 1) the Registry settings remain unchanged,
and 2) pdoxwork.ini is not created anymore.

No idea about the usability of the -f switch, though.

Regards,

Jan



Anne Wainwright <duffaddress (AT) ananzi (DOT) co.za> wrote: