Database Access

  • Thread starter Thread starter J.J. Holiday
  • Start date Start date
J

J.J. Holiday

I'm trying to set up a database that can be read by anyone but only
certain people can update/delete or add records.

I have the database in a seperate domain and only people with access
to that domain can do the updating (i.e. admin.domain.com and a "www"
where the admin domain only allows users with usernames/passwords into
it). But, I need it to be displayed in the main domain (the www).

Could anyone tell me the proper permissions to use to do this on each
domain or recommend a book, website, etc. that has instructions on how
to do it?

Thanks for any help you can give.

J.J.
 
I'm trying to set up a database that can be read by anyone but only
certain people can update/delete or add records.

I have the database in a seperate domain and only people with access
to that domain can do the updating (i.e. admin.domain.com and a "www"
where the admin domain only allows users with usernames/passwords into
it). But, I need it to be displayed in the main domain (the www).

Could anyone tell me the proper permissions to use to do this on each
domain or recommend a book, website, etc. that has instructions on how
to do it?
Click to expand...

It depends on the database. All of the "enterprise-class" databases
have access control built into the database engines - Oracle, SQL
Server, Sybase, Ingres, DB2, etc. If you are talking about Access,
then you will need to craft your own access control.

so:
1) What database are you talking about

2) What kind of access are you trying to allow
(unlimited browsing through the data via administrative isql tools,
limited access thru forms, web access, etc)

3) Why are you creating a separate domain for this instead of creating
a separate group within your existing domain?

4) Is this publicly accessible, or internal only?

--Kent

=================================
Kent Smith * IPSO Incorporated
Business * Technology * Solutions
Financial Services and Accounting Systems Consulting

http://www.ipsoinc.com
 
1) What database are you talking about
Click to expand...

MS Access
2) What kind of access are you trying to allow
(unlimited browsing through the data via administrative isql tools,
limited access thru forms, web access, etc)
Click to expand...

Records will be displayed in a table (using the FrontPage database
results). The page used to update/add/delete is an ASP page.
3) Why are you creating a separate domain for this instead of creating
a separate group within your existing domain?
Click to expand...

If you can tell me how, I'd do it that way. Sorry for being such a
novice. This is one of my first forays into permissions.
4) Is this publicly accessible, or internal only?
Click to expand...

As I said, the data will be displayed in a table. I only want certain
people to be able to update the records though.

Thanks for any help you can give me.
 
MS Access


Records will be displayed in a table (using the FrontPage database
results). The page used to update/add/delete is an ASP page.
Click to expand...

Then the best approach is to use ASP security. There are dozens of
good books out there that give cookbook approaches; this is a very
common thing to do. Make sure you know if you are using ASP or
ASP.NET (they are very different). ASP has pages with a .asp
extension, ASP.NET has pages with .aspx extensions.

This way all your security is handled cleanly by the web server, and
you can lock down the actual database so that it is only accessible by
the IIS anonymous user.

--Kent


=================================
Kent Smith * IPSO Incorporated
Business * Technology * Solutions
Financial Services and Accounting Systems Consulting

http://www.ipsoinc.com
 
Then the best approach is to use ASP security. There are dozens of
good books out there that give cookbook approaches; this is a very
common thing to do. Make sure you know if you are using ASP or
ASP.NET (they are very different). ASP has pages with a .asp
extension, ASP.NET has pages with .aspx extensions.
Click to expand...

I'm using ASP (Not ASP.NET). There seems to be a myriad of books
available. Can you recommend one or two that have information on how
to do what I need done.

BTW, thank you for your help.

J.J.
 
I'm using ASP (Not ASP.NET). There seems to be a myriad of books
available. Can you recommend one or two that have information on how
to do what I need done.

BTW, thank you for your help.

J.J.
Click to expand...

When I did it for the first time, I used "ASP 3.0 A Beginner's Guide"
by Mercer. The basic thing to do is to create a session object to
hold the login state (true/false). Then have each page check the
session variable to see if it is allowed to display things that are
only visible to users who are logged in. If the session is not logged
in, then render a read-only page. If the session IS logged in, then
render an updatable page.

But like I said, this is a very common thing to do, any good ASP
development book should give you examples.

--Kent
=================================
Kent Smith * IPSO Incorporated
Business * Technology * Solutions
Financial Services and Accounting Systems Consulting

http://www.ipsoinc.com
 
Back
Top