How to set LocalShare=true automaticly

#1

How to set LocalShare bY Opal or Innosetup?

Günter Matthies

#2

Günter,
I don't believe it's possible.
When I changed some configuration details interactively the
BDE-administrator always points to that changes first apply after having
restarted all BDE-applications.
Of course you can change registration entries, but my experience is, this
will not apply either.

Egbert

"Günter Matthies" <nospam.info (AT) mk-news (DOT) com> schrieb im Newsbeitrag
news:43e1c28b$1 (AT) pnews (DOT) thedbcommunity.com...
How to set LocalShare bY Opal or Innosetup?

Günter Matthies

#3

Egbert,

better to be at newpapaer: so bad news are good news
for programmer bad nwes cost a lot of time

thank for the reply
Günter

#4

in addition...
what I'm use to do is to deliver a custom *.cfg file.
In the command line I use the -o PathToCnfFile.
This has a lot of advantages: No changes to an existing configuration (no
merger). After closing the P-app the old configuration is recreated.
With PDE you can specify short-cuts with command line parameter. I guess,
Immo will allow this too, but haven't used it yet.
Egbert

#5

Egbert
sounds good
I try it
Thank for Your help
Günter

#6

Günter,

Look in "TheDBComminity.com" for an article written by Rick Kelly on the BDE
API. Rick has provided us with a complete listing of the API calls for the
BDE from within Paradox. It is possible to change all BDE parameters from
within Paradox by using his code examples.

By using "Sessions", it is possible to cause these changes to take effect
for the current Paradox session and optionally save the changes to the
active IDAPI.CFG file so they'll be in effect the next time Paradox opens.
You can test it by causing a BDE parameter change, then enumerating the BDE
configurations.

--
....
`·.¸¸.·´¯`·.¸¸.·´¯`·-> rodney

#7

Rodney,

find the link at

http://www.thedbcommunity.com/code/bdeapi.htm

very good stuff.

The reason I need this, is to install 2 paradox runtime sessions at the
same time working on the same table. (Automatic Install far away)

Thanks

Günter

#8

Quote:

The reason I need this, is to install 2 paradox runtime sessions at the
same time working on the same table. (Automatic Install far away)

I think that the default setting for local share is TRUE. I'm sure about
runtime in P10 and P11. Don't know about earlier Paradox/BDE versions.

If you are willing to "gamble" on the local share setting beeing correct,
the only thing you need to start to sessions simultaniously is the -p switch
in the command line to set different PRIV, but you probably allready knew
that.

Anders

#9

Hi Anders,

Quote:

I think that the default setting for local share is TRUE. I'm sure >about
runtime in P10 and P11. Don't know about earlier Paradox/BDE versions.

I don't think so, Automatic Install: local Share=false, for me with the
tool which someone made for Inno-Setup.

But actually I don't need it, because:
Two Instance of (same) Runtime on same Work Dir, and with different
PrivDir and Local Share=false shares automatic the both used table.

Günter

#10

"Günter Matthies" <nospam.info (AT) mk-news (DOT) com> wrote in message

Quote:

But actually I don't need it, because:
Two Instance of (same) Runtime on same Work Dir, and with different
PrivDir and Local Share=false shares automatic the both used table.

wrong!!.. this is a perfect example of why you need it to be TRUE.. the BDE
caches data internally from local drives, when set to FALSE.. if you
continue sharing a local table like this, you will lose data.. and you could
even end up with a damaged table..

--
Steven Green - Waldorf Maryland USA

Diamond Software Group
http://www.diamondsg.com/main.htm
Paradox Support & Sales - Corel CTech Paradox

Diamond Sports Gems
http://www.diamondsg.com/gemsmain.htm
Sports Memorabilia and Trading Cards