restricted access to a split database on a server

[Bob H]

I have been looking at ways of making a Access 2007 database in mdb
format, which is on a NAS server, restricted to some users.

I have looked at password protecting the whole database, but not what I
want. I have also looked at Access 2007 own security feature, but I
can't see how different users can have different access rights, and from
what I have learned so far, this is a whole new learning process.

So, is there any other way I can restrict access to a said database on a
server?

thanks

 

[David W. Fenton]

I have been looking at ways of making a Access 2007 database in
mdb format, which is on a NAS server, restricted to some users.

If it's not NTFS, I'd recommend against using it, as the only
underlying file systems that are 100% reliable with Jet/ACE are
Windows file systems.

I have looked at password protecting the whole database, but not
what I want. I have also looked at Access 2007 own security
feature, but I can't see how different users can have different
access rights, and from what I have learned so far, this is a
whole new learning process.

So, is there any other way I can restrict access to a said
database on a server?

Yes, with a domain controller. You could set up a real Windows
server as domain controller to do the job, and perhaps make the NAS
a member of the domain. You could also set up a non-Windows box and
run SAMBA to act as domain controller. It wouldn't matter that you
were using a non-Windows domain controller, as long as the data is
stored on a Windows file system.

You'll find that there really isn't much in the way of actual
security available with these NAS devices.

 

[Bob H]

If it's not NTFS, I'd recommend against using it, as the only
underlying file systems that are 100% reliable with Jet/ACE are
Windows file systems.


Yes, with a domain controller. You could set up a real Windows
server as domain controller to do the job, and perhaps make the NAS
a member of the domain. You could also set up a non-Windows box and
run SAMBA to act as domain controller. It wouldn't matter that you
were using a non-Windows domain controller, as long as the data is
stored on a Windows file system.

You'll find that there really isn't much in the way of actual
security available with these NAS devices.

The situation I have is that the NAS server is at work, and the reason
the Acess 2007 database is in mdb format is because there are still 2
users who have Access 2003
The OS on the machines at work is WinXP, and possibly NTFS file system.
What is a Domain Controller, and anything else is not really possible.

As I mentioned before , I only want to give restricted access to the
database in as much as allowing full rights to the Admin, and only read
rights to others.

Thanks anyway

 

[Jeff Boyce]

Bob

If you are talking about the "database" as a collection of tables, rather
than a full-blown application, I am only aware of file-level permissions
from the NOS, and the complex (and not terribly secure) Access security.

If you are talking about a full-blown application, then an option I've used
is to set up a "settings" list (some folks use an INI file) that includes
settings (ADMIN) and "members" (via their network logon initials).

Then, while opening a form in the application, I use a function to determine
if the logon initials of the user is in the list of legitimate members of
"ADMIN" (or any other setting). I use the boolean result (approx. IsADMIN)
to control things like which controls are enabled/disabled, etc.

A determined hacker could circumvent this security, but the same has been
said for Access' built-in security...

Good luck!

Regards

Jeff Boyce
Microsoft Access MVP

--
Disclaimer: This author may have received products and services mentioned
in this post. Mention and/or description of a product or service herein
does not constitute endorsement thereof.

Any code or pseudocode included in this post is offered "as is", with no
guarantee as to suitability.

You can thank the FTC of the USA for making this disclaimer
possible/necessary.

 

[Bob H]

The database a split database with the tables on the back end on the NAS
server, then a copy of the front end with forms and queries on local PC's.
The restriction I want is for certain users to just view the data, while
for 1 other person besides myself, I want full read/write permissions.

I am aware that what you use is an option but as a newbie/intermediate
with Access 2007, I don't know how to set this up.
I would guess it would mean having a table of users, and possibly
permissions, but I don't know after that.

Thanks

 

[David W. Fenton]

The situation I have is that the NAS server is at work, and the
reason the Acess 2007 database is in mdb format is because there
are still 2 users who have Access 2003

???

What does MDB format have to do with it? It's Jet/ACE no matter
whether you use MDB or ACCDB and the issues with the file system and
multi-user locking are the same.

The OS on the machines at work is WinXP,

Irrelevant. What matters is the OS on the NAS, which is most likely
*not* NTFS.

and possibly NTFS file system.

On WinXP machines I'd consider it very unlikely if it were not NTFS.
But it has nothing to do with the question of accessing the shared
back end.

What is a Domain Controller, and anything else is not really
possible.

As I mentioned before , I only want to give restricted access to
the database in as much as allowing full rights to the Admin, and
only read rights to others.

Without a central logon authority to enforce that, it's not
possible. Most NAS devices have very simple user/password setup, but
it's unlikely to be able to handle different levels of access, nor
be transparently usable with Access.

 

[David W. Fenton]

If you are talking about the "database" as a collection of tables,
rather than a full-blown application, I am only aware of
file-level permissions from the NOS, and the complex (and not
terribly secure) Access security.

I thought it was pretty clear from the original post that he wanted
to control access via the file system to a back end stored on a NAS
device. As I've explained, this is likely unworkable unless the
device is a Windows device.

 

[Jeff Boyce]

Offering options, seeking clarification...

Jeff B.