Quote

> Problems with Paradox on CD-Rom on a network

> We have a Paradox Database on a CD-Rom  accessed via Netware 3.12.
> The Problem is that Paradox tries to write the *.lck Files
> (Paradox.lck and Pdoxusrs.lck ) in the Database Directory on CD.
> Is it possible to avoid writing these locking files or to put them
> into another directory?

Quote

> Dipl. Inform. Bernd Ostermann wrote:

> > Problems with Paradox on CD-Rom on a network

> > We have a Paradox Database on a CD-Rom  accessed via Netware 3.12.
> > The Problem is that Paradox tries to write the *.lck Files
> > (Paradox.lck and Pdoxusrs.lck ) in the Database Directory on CD.
> > Is it possible to avoid writing these locking files or to put them
> > into another directory?

> I guess your problem is that the paradox database is on a network drive
> and the BDE assumes it can create .lck files.  Using a local CD-ROM is
> fine, as the BDE detects it is a read-only drive.  What you could try is
> revoking all create, write etc rights to the directory using filer (or
> is it syscon...been a while).  This should tell the BDE that this drive
> is read-only when it queries Netware.  I think the only rights you need
> are Read and Filescan.  Of course, you need a place where they can
> create their .net files.  This is mandatory.

> The other thing you could try is opening the tables in readonly mode
> (property of the ttable object).

> --
> Mark.

Quote

<pa...@linusserver.pccity.com.au> wrote:
>I, too, would be interested in a solution.

>If I can convince the BDE a database is read only then I wouldn't have to
>expose my server to {*word*193} users who like deleting things!  At the moment, I
>need to give all users read/write access to the server to enable networking
>(I've been told that the SUBST command is unreliable under win95).

>Paul. pa...@linuxserver.pccity.com.au 13:34 Wed 21/8/96

>Mark Pritchard <pritc...@ozemail.com.au> wrote in article
><321964C5.5...@ozemail.com.au>...
>> Dipl. Inform. Bernd Ostermann wrote:

>> > Problems with Paradox on CD-Rom on a network

>> > We have a Paradox Database on a CD-Rom  accessed via Netware 3.12.
>> > The Problem is that Paradox tries to write the *.lck Files
>> > (Paradox.lck and Pdoxusrs.lck ) in the Database Directory on CD.
>> > Is it possible to avoid writing these locking files or to put them
>> > into another directory?

>> I guess your problem is that the paradox database is on a network drive
>> and the BDE assumes it can create .lck files.  Using a local CD-ROM is
>> fine, as the BDE detects it is a read-only drive.  What you could try is
>> revoking all create, write etc rights to the directory using filer (or
>> is it syscon...been a while).  This should tell the BDE that this drive
>> is read-only when it queries Netware.  I think the only rights you need
>> are Read and Filescan.  Of course, you need a place where they can
>> create their .net files.  This is mandatory.

>> The other thing you could try is opening the tables in readonly mode
>> (property of the ttable object).

>> --
>> Mark.

Quote

> Not that I know much about Paradox tables, but doesn't the NetFileDir
> property of TSession specify where the lock files are located, i.e.
> can't you change it in the Session object?
>=20
> On 21 Aug 1996 03:36:01 GMT, "Paul Motyer"
> <pa...@linusserver.pccity.com.au> wrote:
>=20
> >I, too, would be interested in a solution.

> >If I can convince the BDE a database is read only then I wouldn't =
have to
> >expose my server to {*word*193} users who like deleting things!  At the =
moment, I
> >need to give all users read/write access to the server to enable =
networking
> >(I've been told that the SUBST command is unreliable under win95).

> >Paul. pa...@linuxserver.pccity.com.au 13:34 Wed 21/8/96

> >Mark Pritchard <pritc...@ozemail.com.au> wrote in article
> ><321964C5.5...@ozemail.com.au>...
> >> Dipl. Inform. Bernd Ostermann wrote:
> >> >=20
> >> > Problems with Paradox on CD-Rom on a network
> >> >=20
> >> > We have a Paradox Database on a CD-Rom  accessed via Netware =
3.12.
> >> > The Problem is that Paradox tries to write the *.lck Files
> >> > (Paradox.lck and Pdoxusrs.lck ) in the Database Directory on CD.
> >> > Is it possible to avoid writing these locking files or to put =
them
> >> > into another directory?
> >>=20
> >> I guess your problem is that the paradox database is on a network =
drive=20
> >> and the BDE assumes it can create .lck files.  Using a local CD-ROM =
is=20
> >> fine, as the BDE detects it is a read-only drive.  What you could =
try is=20
> >> revoking all create, write etc rights to the directory using filer =
(or=20
> >> is it syscon...been a while).  This should tell the BDE that this =
drive=20
> >> is read-only when it queries Netware.  I think the only rights you =
need=20
> >> are Read and Filescan.  Of course, you need a place where they can=20
> >> create their .net files.  This is mandatory.
> >>=20
> >> The other thing you could try is opening the tables in readonly =
mode=20
> >> (property of the ttable object).
> >>=20
> >> --=20
> >> Mark.
> >>=20

Quote

Quote

> SYMPTOMS

> You cannot link (attach) a Paradox table (*.DB) located on  a read-only drive. If you try to link a Paradox
> table on a read-only drive, you receive the following error message :

>  Couldn't open file ....
> or
>   Couldn't  lock table ....

> CAUSE

> Neither Paradox nor the Paradox indexed sequential access method (ISAM) shipped with Microsoft Access
> supports databases located on read-only drives.

> STATUS

> This behaviour  is by design.
> '