Rights and Permissions

  • Thread starter Thread starter Carroll McAllister
  • Start date Start date
C

Carroll McAllister

Got a problem with our Windows 2000 Server, when we set up our hard drives
formatted as NTFS.

We use a dental office practice management system for insurance and billing.
As a part of the record-keeping process, we can scan documents (lab reports,
explanations of benefits (EOBs), and more importantly for my uses,
photographs and x-rays) which can be linked to a patient's record.

Our problem is that when we have the hard drive set up as NTFS, and even
though I have granted full rights and permissions to the group authorized
access to those records/files, any images scanned by an individual user,
can't be seen by anyone else who views that record. The link to the image
is in the database, but when our app goes to find it, it can't.

After some investigation, I've seen that when an individual user scans a
document, they're listed as the owner of that document, and no one else can
view it, even though they've been granted full rights to the app directory,
subdirectories, and files. However, if the original "owner" attempts to
view the scanned document, they can.

As a workaround, I've gone back to FAT32, until I can trace down the root of
the problem.

Any suggestions would be appreciated.
 
where is the database ?

It is on the file server. Dell Poweredge 1300 running Windows 2000 Server,
SP4. Two duplexed 18GB SCSI hard drives. The app is in a subdirectory off
the main hard drive, with a drive letter on each workstation mapped to that
subdirectory.

Since we're not running Active Directory on our file server at the moment
(that's another issue), I've got a group set up on the file server with
complete access rights to that directory/subdirectory. All users in our
office who would need access to that subdirectory are in the group.

On the file server, the app is actually in the \Softdent\Softdent directory.
On each workstation, I've got a drive mapped to the root directory of that
particular folder tree ( the first \Softdent directory), which is Drive S:
(easy to remember where it's located). The app itself (and associated
files) are actually in the \Softdent\Softdent directory/folder, with more
folders off that directory.

When each user logs onto the network, a drive letter (again, S:), is mapped
to the \Softdent directory, the highest directory/folder in that particular
tree. Then, the app is set up on their workstations to run the app from the
S:\Softdent directory.

Our app can be run either from shortcuts to the files on the server, or in
"client-server mode", where the files necessary to run the app are installed
on the local machine, and the data files are kept on the file server.
Client-server would be used in order to reduce network traffic. Otherwise,
there would be a *lot* of traffic on the network as each workstation grabbed
*everything* it needed to run the app from across the wire. In
client-server mode, it's just shooting the data back and forth, instead of
the program itself.

It looks more confusing than it is. <G>
 
Windows 2000 Pro or XP Pro. One station is running Windows 98 SE, and one
is running Windows ME, but neither one of those have a particular need to
view scanned documents.

I'll take a look at the file you pointed me to, and see what it says.
Thanks.
 
Back
Top