pdoxusrs.lck problem

[Todd]

I have created a delphi app that resides on a server. For the users to be
able to access this directory, they must have read/write in order to create
the .lck file when using it. How can I set up the pdoxusers.net file so I
can set aside a section of network where this .lck file can be created and
deleted without giving them access to the application directory where all
the files and databases sit.

[Liz]

Todd,

You can't. The .LCK files go in the same dir as the
tables. Not only do your users need read/write privileges,
they need create, modify and delete as well (the .LCKs get
deleted when the last user closes the last table, created
when the first user opens the first table, modified in
between). Some suggestions to minimize your risk:

1. Backup. Backup. Backup.
2. If you're not using NT (which doesn't work so well with
UNC), you can NOT map a drive to the data, and point to the
tables using UNC, thereby making it _slightly_ more
difficult for the average user to locate the tables and muck
with them.
3. If that's not an option, make sure the dir isn't used for
any other purpose; make sure its name isn't something that
sounds 'deletable' ("junk" would be a likely target for
thoughtless deletion, for example); make sure your users are
trained and know not to do anything in this directory with
the file system, but rather they should leave it to your
app.
4. If you're lucky enough to have a Novell server, become
good friends with filer and make sure the users know to call
support as soon as they screw up rather than three days
later. (Don't know if NT server has such a tool.
5. Backup. Backup. Backup.

If your users only need to _view_ data, as opposed to
writing data, you can put a dir lock in and make the dir
read only - let us know if you need help on making a dir
lock.

Liz

[Todd]

HI LIz,

Thanks so much I appreciate the quick response.

YES, they only need to view the database tables. What is a dir lock.

Thanks again

"Liz" <lea...@aros.net> wrote in message news:3ABA965B...@aros.net...

[Todd]

LIz,

I should add, I am just a network admin. type and I dont really have access
to the original Delphi/paradox code. Hopefully this can be done without
having to manipulate existing code.

Thanks

"Liz" <lea...@aros.net> wrote in message news:3ABA965B...@aros.net...

[M.H. Avegaart]

You can modify the directory where the .net file is located by changing
Configuration | Drivers | Native | PARADOX | NET DIR in the BDE
Administrator or (in code) by changing Session.NetFileDir (before any
databases are opened). But I haven't checked if this changes the .lck file
location...

"Todd" <noT...@hotmail.com> schreef in bericht
news:W4wu6.278434$Vj5.36...@news02.optonline.net...

[Liz]

Todd,

I'd recommend you get a programmer in to make sure the code will
work with a dir lock in place. (Isn't the developer around
anymore? Or is it commercial software?)

I'm not a Delphi developer. I can't tell you how to make a
directory lock with Delphi. I could tell you how to do it in
Paradox (comp.databases.paradox, FYI, covers Paradox the program
rather than Paradox the file format).

So hopefully a Delphi developer will jump in here and give you
what you need.

Liz

[Todd]

the .lck file is already created in this network directory. The .net file
is also here to so multiple users can access the program. RIght now, they
have to have full access to this directory to be able to create and delete
this .lck file.

Is the command to create and delete this .lck file in the code? OR is it
something I can modify in the Idapi.cfg file on each users local machine. I
would like to limit all users to read access only, and perhpas move this
.lck file to another place.

I hope I dont have to modify the code, I believe this is a compiled program.
But if this is the only way, how wold the programmer go about changing this?
I can talk to him.

THanks a bunch!!

"M.H. Avegaart" <avegaar...@mccomm.nl> wrote in message
news:99fiaq$3ts$1...@porthos.nl.uu.net...

[Todd]

Yes, I tried to change the location of the .net file in the BDE config
program, but the .lck file is still being created in the same place where
all the databases are.

"M.H. Avegaart" <avegaar...@mccomm.nl> wrote in message
news:99fiaq$3ts$1...@porthos.nl.uu.net...

[Steve Green]

Todd wrote:

> Yes, I tried to change the location of the .net file in the BDE config
> program, but the .lck file is still being created in the same place where
> all the databases are.

there will *always* be lock files in the directories where tables are accessed..
that's how it works, you can't change it.. if tables are for "view" only (like
they are on a CD) you can place what is known as a DirLock (directory lock) in
the directory with the tables.. that tells paradox (or the BDE) that the tables
are "read only" and it doesn't try to modify the lock, or allow any non "read
only" access to the tables..

--

Steve Green
Corel CTech - Paradox
Diamond Software Group, Inc.
Waldorf, Maryland USA

http://www.diamondsg.com
Gre...@DiamondSG.com

[John]

I put this in my mainforms oncreate event.

Session.PrivateDir := 'Some directory';
Session.NetFileDir := 'A directory that can be accessed by all';

Use a seperate folder to hold the Net file. c:\data\net or something like
that.

If no access to the source codes then set using BDE admin. prog.
configuration/driver/native/paradox Net Dir to the same location on all
machines that access the shared datafiles.

"Todd" <noT...@hotmail.com> wrote in message
news:p%Lu6.286826$Vj5.37...@news02.optonline.net...

[Todd]

Steve & LIz,

How do you do this (directory lock)?

Thanks

Todd

"Steve Green" <gre...@diamondsg.com> wrote in message
news:3ABB9B68...@diamondsg.com...

[Steve Green]

Todd wrote:

> How do you do this (directory lock)?

it's created by command, but they're generic.. you can get somebody to pass
you one that's already made.. it's just got a one-byte difference from the
regular lock files..

[Todd]

HOw can I create one by command, and also how may I get a generic one.

Thanks

"Steve Green" <gre...@diamondsg.com> wrote in message

news:3ABBBB57...@diamondsg.com...

[Liz]

Todd,

Don't know which groups will accept an attachment, and which
won't, so go to http://www.aros.net/~law/dirlock.htm and
download the file. I've never used dir locks, didn't know
they were generic. No guarantees this set will work
(there's two files in the zip).

Liz

[Steve Green]

Liz wrote:

> I've never used dir locks, didn't know they were generic.

a lock file doesn't know what directory it belongs to.. a dirlock doesn't
get written to once it's created.. so pdox (or the BDE) is content in just
seeing that it's there..

[Liz]

Steve,

Makes sense. (Also explains why those 'left over' lock
files can be such a problem...)

Thanks,

Liz

[Todd]

Liz, I downloaded the file and will try it out. I will let you know how it
goes.

Thanks guys for your help.

"Liz" <lea...@aros.net> wrote in message news:3ABCDFE8...@aros.net...

[Todd]

Liz,
That download did work. GREAT!! Thanks so much. IT works now with only
read only to this directory and I moved the .net file somewhere else.

Thanks a bunch

"Todd" <noT...@hotmail.com> wrote in message

news:Sdlv6.19176$K54.2...@news02.optonline.net...

[Liz]

Todd,

Glad to hear it!

Liz

[Liz]

Todd,

Glad it works.

Liz