local share BDE for paradox 
Author Message
 local share BDE for paradox

Hi,

About paradox databases:

On several webpages concerning paradox file corruption (e.g.
http://www.***.com/ ), I read that the local share
setting of the BDE should be set to true. But it should only be important on
peer to peer LAN's.

I'm working on a LAN with NT4 server, and my data is on one of these
networkdrives (subdir). The NET file is pointing to the same directory on
that network drive for every client. Everything seems to work OK. This is
not peer to peer.

Should I still set the Local Share property to TRUE or not? If so, must I do
this for all clients while no-one is using the database?

Thanks,
Sokon.



Wed, 18 Jun 1902 08:00:00 GMT
 local share BDE for paradox


Quote:
> Hi,

> About paradox databases:

> On several webpages concerning paradox file corruption (e.g.
> Http://www.itecuk.com/Delmag/paradox.htm ), I read that the local share
> setting of the BDE should be set to true. But it should only be important
on
> peer to peer LAN's.

Its only vital on peer-to-peer. I've found that it makes sense for every
installation, including single user ones.

Quote:

> I'm working on a LAN with NT4 server, and my data is on one of these
> networkdrives (subdir). The NET file is pointing to the same directory on
> that network drive for every client. Everything seems to work OK. This is
> not peer to peer.

It's not peer-to-peer from your perspective but it is from a network point
of view. Any station on the network can interact with any other station -
that's peer-to-peer.

Quote:

> Should I still set the Local Share property to TRUE or not? If so, must I
do
> this for all clients while no-one is using the database?

Yes. Not necessarily but I would suggest it.
Quote:

> Thanks,
> Sokon.



Wed, 18 Jun 1902 08:00:00 GMT
 local share BDE for paradox

Quote:
> > I'm working on a LAN with NT4 server, and my data is on one of these
> > networkdrives (subdir). The NET file is pointing to the same directory
on
> > that network drive for every client. Everything seems to work OK. This
is
> > not peer to peer.

> It's not peer-to-peer from your perspective but it is from a network point
> of view. Any station on the network can interact with any other station -
> that's peer-to-peer.

from the Inprise/Borland site I found
(http://community.borland.com/article/0,1410,15247,00.html):

"The BDE automatically detects when tables reside on a
network drive, but it cannot detect whether the tables
are on a dedicated server or a server/client.  Dedicated
servers notify client applications that a file has been
modified or locked.  This functionality is not present in
Peer-To-Peer (non-dedicated) networks.  To achieve this
functionality with Peer-To-Peer networks set "LOCAL
SHARE" to TRUE in the BDE Configuration Utility on the
System page.  This must be done on all BDE clients that
access the tables on networks listed above."

---
We have a fileserver (NT4 server). This is dedicated, or not?
PS: I'm using BDE 5.10.
---

The following link (http://www.itecuk.com/Delmag/paradox.htm) contained:
"In the BDE Configuration application on all PCs that will run the program,
set Local Share to True on the System page. This ensures that lock files are
written to the local hard disk, thereby ensuring that applications on other
machines will be able to find the lock files. This should only be necessary
for the machine where the data resides, however the general opinion is that
it should always be turned on, provided you have file sharing functionality
loaded with either SHARE or VSHARE. On peer to peer networks, the default
setting of Local Share is a common cause of data loss."

---
The lockfiles are written to the location of the database on the fileserver.
Is this not the best location to find the lock files for other machines? The
NET file also resides here. SHARE or VSHARE -> aren't these old terms (I
remember something like that from Delphi 1)?
---

And now the part that is frightning me:

"If Local Share is True then the BDE will detect an incorrect NetFileDir and
refuse to access the tables. If an incorrect assignment here is causing
corruption then Local Share is still the real culprit."

---
I would not want this to happen...
---

Then:
"Ensure that all users have their own private directory, preferably local.
This is set with the Session object's PrivateDir property."

---
Is this really nessecary?
---

Thanks for any help,
Sokon.



Wed, 18 Jun 1902 08:00:00 GMT
 
 [ 3 post ] 

 Relevant Pages 

1. BDE - Local Share - True or False

2. HELP for setting LOCAL SHARE in BDE

3. BDE - LOCAL SHARE - True or False

4. BDE - LOCAL SHARE

5. Paradox 4.5 Local Share Problem on Peer-Peer Network

6. "LOCAL SHARE" and multiuser Paradox databases

7. A BDE-capable local database faster than Paradox with TQuery

8. lcoking/sharing problem BDE/Paradox over network

9. Sharing BDE Session Between Delphi And Paradox

10. Problem Sharing PARADOX tables via shared directory on server

11. BDE 5.0 SQL on Paradox tables so slow in comparisont to BDE 2.52

12. Delphi3 BDE and Paradox BDE problems


 
Powered by phpBB® Forum Software