Discussion :

[yannick]

Salut tout le monde,
voila mon problème...
je développe une application en mono poste avec paradox7 sous Delphi 5 pro... mais je l'ai installée sur un réseau local poste a poste, c.à.d où il n'y a pas de serveur dédié.
j'ai pris un poste comme serveur et j'ai installer l'appli dessus. J'ai créé des raccourcis sur les bureaux des autres postes de sorte qu'on execute le programme comme si on était en clt/serveur.
A un moment donné, l'appli ne répond plus sur aucun poste et il m'affiche le message suivant " Repertoire contrôlé par un autre fichier.net, Répertoire c:\
Fichier: PDOXUSRS.LCK
comment puis**-je résoudre le problème ?
merci...

[Epictète]

Il faut parametrer le BDE en fonction de ta configuration réseaux, lire :


Guide de survie de l'utilisation des tables Paradox dans Delphi :
http://www.developpez.com/sgbd/PDox%...al%20Guide.rtf

[yannick]

merci pour l'aide, elle est précieuse pour moi..
Je suis allé sur le lien et j'ai trouvé ce que je voulais...Je l'essaye et je te tiens au courant. Encore une fois merci...

[yannick]

bjr,
c encore moi, j'ai parametré le BDE sur la machine servant de serveur en affectant la valeur "TRUE" au "Local share" mais malgré cela j'ai tjrs le même message. J'ai redémarré la machine mais sans succès.
que puis-je faire encore...

[Anonymous]

Voici en anglais un extrait d'une réponse sur un forum US à ton type de probleme.

(voici les liens te permettant de retrouver le message
http://www.thedbcommunity.com/support/
news://pnews.thedbcommunity.com

Objet: Re: BDE Initialization Failure
Date: Tue, 02 Apr 2002 06:45:37 -0700
De: Liz <liz@paradoxcommunity.com>
Société: Paradox Community
Forums: pnews.paradox-development


Si tu ne comprends pas l'anglais, le paragraphe 2 indique simplement d'éffacer les fichiers .NET et .LCK
Mais attention ces operations ne sont pas anodines. Faire des copies auparavant.
Régis

*** quote***
.....
B. It has been my experience that if Paradox creates a local .NET
when the network .NET is not available, **** it will use the
local .NET from then on even when the network .NET is available
**** Somehow, it seems to know that there's a .NET file on the
local HDD and uses it instead of the network one. I realize this
sounds like voodoo, and I can't reproduce it reliably, but I've
seen it. So, the following are my instructions for fixing BDE
Initialization errors:

1. Close Paradox (and any other BDE app) on all computers on the
network.

2. Search all computers, including the server and computers which
are not currently attached to the network (laptops, for example
which come and go from the network), for PARADOX.LCK,
PDOXUSRS.LCK and PDOXUSRS.NET. Delete *all* found instances of these files.

3. On _all_ computers, including the server (if BDE is installed)
and computers not currently attached to the network,
_double_check_ the NET DIR setting, make sure it's _identical_ on
all machines (I usually use the browse button so it's in the
format the BDE wants to put it in (case, included backslashes,
etc.)). Do this even though you're sure it's right.* While
you're there, take the opportunity to check that LOCAL SHARE is
TRUE, and that other settings are as you'd like them to be.
NOTE: Merging a .cfg file with the user's does _NOT_ change all
settings (I think maybe it just adds aliases, not sure). If
you're gonna do this by sharing a file, _replace_ the user's
config file.

*Why do this even though you're sure it's right? There are
_numerous_ applications out there which use the BDE. These
generally do an unfriendly, 'hidden' BDE install - they don't
announce that the BDE is about to be installed. They frequently
overwrite newer versions of the BDE. They frequently _overwrite_
your config file, removing aliases and/or the NET DIR setting.
They can overwrite bits of the config file settings - maybe they
dump your aliases, maybe they overwrite NET DIR, maybe they reset
the default block size, whatever, they almost always mess things
up. Your users aren't allowed to install software on their
computers? Aren't allowed and aren't able are two different
things. Don't trust anyone or anything, double check it! :-)

4. For all computers which occasionally work off network, create
a separate config file with a local NET DIR, create a "network"
and a "local" icon for the app, use the -o command-line parameter
to force the proper config file to be used for each. (This seems
to get around the problem mentioned in B above, which only seems
to happen when, on startup, Paradox cannot find the proper .NET
file.) You may wish to use the -o command-line for all Paradox
shortcuts on all machines to ensure the proper config file is
being used... You may wish to set the config file to read-only
(depending on your needs), but this will NOT prevent the problem
of other apps installing the BDE as mentioned above.

5. Start up one specific workstation. Ensure that it created the
.NET file in the proper dir. Open one table in each data
directory, ensure that this creates two .LCK files per
directory. Allow other users to start Paradox. Leave that one
workstation as is until you're certain that all users are in and
their copy of the app is functioning normally. Should anyone
report problems once all this has been done, double check their
settings, and that they don't have stray .LCK or .NET files, and
if all is as it should be and you can find no other source of the
problem, reinstall Paradox.
...
*** end quote***[/url]

[Anonymous]

Il faut supprimer le fichier LCK.
Pendant un mois j'ai essayé de faire fonctionner une appli (delphi)avec des tables paradox en réseau ( 30 postes) .Que des merdes. quand ce n'est pas le problème des fichiers LCK ou .net ce sont les tables qui sautent avec le message ' en tête endommagée' et qui ne sont récupérable que par access.
Paradox fonctionne par défaut en mode pessimiste et cela n'est pas configurable De là viennent une bonne partie des problèmes.Mais il y en a d'autre notemment la fragilité bien connue du fichier d'index (.PX) qui claque pour un oui ou pour un non et qui rend la table innaccessible.
La solution: abandonner paradox pour les appli en réseau.
J'ai choisi access .Plus de problème.