Kasey Chang (fix address before replying to me!)
Quote:> Local share only needs to be true if you are running multiple IDAPI
> based programs at the same time, including multiple sessions of
> Paradox, ON THE SAME COMPUTER. This is usually NOT true.
Sorry to have to correct you on this one; local share must be set to TRUE
on another case as well. See the following text that I wrote some time ago
when replying to similar threads. You may also confirm it by looking up the
subject "Sharing information between workstations" in Paradox 8's help (if
you think that it looks similar to my text it is because I sent it to Corel
during the beta and they decided to include in the help file).
Here is a brief explanation of how LOCAL SHARE should be used. Actually, it
is a concatenation of parts of previous messages that I sent some time ago.
Hope it helps.
If the tables are being stored on a workstation's shared disk then the
LOCAL SHARE *must* be True (using the BDE / IDAPI / ODAPI configuration
utilities), but only on that workstation (which has the tables); other
workstations accessing these shared tables (which are not local to them) do
not need to have the LOCAL SHARE set to True. This configuration requires
that the workstations that store shared tables (and that need to have the
LOCAL SHARE set to True) have a different BDE (or IDAPI / ODAPI)
configuration file from the workstations that just access tables which are
shared on other workstations, unless you don't mind having all
workstations' LOCAL SHARE set to TRUE (which, by the way, is the safest
thing to do).
The way that a true file server (Netware, NT) implements locks at the NOS
level is different (better & faster) from the way that a workstation in a
peer-to-peer network does for the shared files that reside on its local
disk. In older Paradox editions, we had to specify which network was being
used; there was a separate entry for each of the major file server LANs,
and a single entry for all the "share-based networks" (LANtastic, WfW,
Novell Lite) that needed MS-DOS's SHARE to be loaded.
So, if your shared files reside on a file server then the locking works
properly without the need to load MS-DOS's SHARE or to set the LOCAL SHARE
to True. However, when sharing the files (tables) of a workstation (WfW,
95) both should be used (MS-DOS's SHARE and LOCAL SHARE) so that the
workstation's operating system will resepect the locking mechanism.
Actually MS-DOS's SHARE need not be loaded in Win95 as it is loaded
automatically on demand - but LOCAL SHARE still has to be set to True.
The general advice should be to set the LOCAL SHARE to
True, at least for the non-experts. There is another reason to do so: if it
is set to False then directory lockings (as locked via the setDirLock
method) are not respected.
Note: Don't confuse NT Workstations with NT Servers. Shared files on an NT
Workstation are handled in the same way as on an Win95 workstation.