HELP with SORT and TMPSRnnn tables

#11

Quote:

For the record, I wasn't the one who decided users shouldn't have delete
rights in the data dir

yes, but your experience with that is the basis for your detailed
description of EXACTLY what happens.. (g)

--
Steven Green - Waldorf Maryland USA

Diamond Software Group
http://www.diamondsg.com/main.htm
Paradox Support & Sales

Diamond Sports Gems
http://www.diamondsg.com/gemsmain.htm
Sports Memorabilia and Trading Cards

"Liz McGuire" <liz (AT) paradoxcommunity (DOT) com> wrote

Quote:

Thanks.

Can you tell management have yelled at me? <g

For the record, I wasn't the one who decided users shouldn't have delete
rights in the data dir - that was someone before me - as soon as I found
out they didn't, I told the network manager to give them delete rights and
that solved a lot of problems (until our user count caught up with the
poor design... we're still trying to out-run that one).

Liz

Steven Green wrote:
excellent explanation of the internals, Liz.. !!!

--
Steven Green - Waldorf Maryland USA

Diamond Software Group
http://www.diamondsg.com/main.htm
Paradox Support & Sales

Diamond Sports Gems
http://www.diamondsg.com/gemsmain.htm
Sports Memorabilia and Trading Cards

#12

I would add two more ways to Liz' excellent summary:
3) Mark all *directories* as hidden. Sadly, Paradox does not like it
when the files themselves (db, fsl etc.) are hidden or that would be an
extra layer of .
4) Mark all *directories* as read only (but don't automatically cascade
that right down to all the sub-directories!).

When dealing with users, every little bit helps... :-)

On 24-05-2007 12:04 Liz McGuire wrote the following email:

Quote:

There are 2 ways to help avoid users deleting tables:

1) Use some obscure drive letter for your Paradox files and don't put
any other files there and don't allow users to create files at the root
of the drive. Have nothing but folders at the root of the drive.

2) Use UNC rather than mapped drives, so that it's harder for users to
find where your Paradox files live in the first place.

#13

Liz,

Superb explanation - for both the technical and LOL portions!!

Thank you.

To emphasise one point you made: some apps (a likely example is Backup
systems) create files in root folders of all available drive-letters,
no-matter-what. If any PDox data or programs are in the ROOT of any
drive, and if PDox is not expecting any "foreigners" at that location,
PDox might get upset when these odd-ball files appear.

(I've been caught with that one - I had all programs at the root of a
mapper drive-letter in the server, and had procs to copy these into a
local client folder if any item is updated. These procs duly choked on
the unexpected files...)

Zal,

Quote:

I would add two more ways to Liz' excellent summary:
3) Mark all *directories* as hidden. Sadly, Paradox does not like it
when the files themselves (db, fsl etc.) are hidden or that would be an
extra layer of .
4) Mark all *directories* as read only (but don't automatically cascade
that right down to all the sub-directories!).

On some PdoxDOS sites, I've had issues with ******** (ie, probably
users!) deleting some important files. So, I marked all unchanging files
(forms, reports, VALs, SETs, etc) and all program files, as Read-Only.

It helped greatly, but, obviously, was a small nuisance when these files
had to be revised - one BAT file to clear all the R-O flags before
updates were applied, and one to set them on the relevant files after
the updates.

- Mike

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

HELP with SORT and TMPSRnnn tables

comp.databases.paradox comp.databases.paradox

Re: HELP with SORT and TMPSRnnn tables - 05-24-2007 , 01:51 PM

Re: HELP with SORT and TMPSRnnn tables - 05-25-2007 , 08:53 AM

Re: HELP with SORT and TMPSRnnn tables - 05-25-2007 , 11:27 AM