Password protecting a linked database

[Mark]

I have a front end user interface with a backend database (the frond
end links to the database using linked tables). The front end of the
database has user level security applied to it and that works fine.
The problem is that the backend database does not have any security
applied to it and a user can easily open open the database and play
around with the data. Is there a way of password protecting the
backend database so users cannot gain access do the database?

 

[Rick Brandt]

I have a front end user interface with a backend database (the frond
end links to the database using linked tables). The front end of the
database has user level security applied to it and that works fine.
The problem is that the backend database does not have any security
applied to it and a user can easily open open the database and play
around with the data. Is there a way of password protecting the
backend database so users cannot gain access do the database?

Why don't you just use ULS on the back end? If you've done so to the front
end (properly) then you have already done 90% of the work to also apply it
to the back end.

 

[Mark]

Why don't you just use ULS on the back end?  If you've done so to the front
end (properly) then you have already done 90% of the work to also apply it
to the back end.

Would I just do this using the wizard again, or would you just create
another ULS on the back end?

 

[Rick Brandt]

Would I just do this using the wizard again, or would you just create
another ULS on the back end?

No. Any file you create while joined to a secured workgroup is automatically
secured with that workgroup. Just open Access while signing into your
secured workgroup as an administrator, create a new blank file, then import
all of the tables from your existing back end into it. Then all you have to
do is assign permissions and replace your current back end with the new
file.