Putting a database on a network

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have created a database of student information and would like to put it on
the school intranet, so it is accessible to all staff. It would have to be
read only, so nothing can be changed by anyone but myself.
I understand that I would need to split it into a front and back end, which
I think I am capable of doing. What I don't understand is how to make it so I
can access it and change things, add information and do the maintainance, and
anyone else who accesses it is only able to look and print reports etc.
Could anyone give me a simple explination of what steps I need to take.

Many thanks
 
Unfortunately there are products on the web which will let an
unauthorised user break the security of a properly secured Access
database. And I imagine that a student population would be very likely
to (a) want to do that, and (b) know how.

So before you go any further, I'd be asking myself what level of risk I
was prepared to take with this data.

HTH,
TC (MVP Access)
http://tc2.atspace.com
 
TC said:
Unfortunately there are products on the web which will let an
unauthorised user break the security of a properly secured Access
database. And I imagine that a student population would be very likely
to (a) want to do that, and (b) know how.

So before you go any further, I'd be asking myself what level of risk I
was prepared to take with this data.

HTH,
TC (MVP Access)
http://tc2.atspace.com
Click to expand...

I appreciate what you are saying TC, but these are young children most of
whom have difficulty using a computer, so I would say the risk is negligible.
 
Ok, if that is the case, just ensure that the database, on starting up,
displays a switchboard (or "selection" or "menu") form that you have
designed. That form should have selection options for other forms &
reports that you have designed. The reports are automatically "read
only" in nature. In the forms, just set the AllowAdditions,
AllowDeletions and AllowEdits properties to False: then the users will
not be able to add, delete or edit records via those forms.

However, be aware that a knowledgeable user could easily add, edit or
delete records by going directly into the various tables - bypassing
all your forms completely.

It is desirable for various reas0ons to split your fatabase into a
front end/back end structure. For more information, just google the
Access groups for those terms, or "FE/BE" etc. To understand how to set
or bypass database startup properties, just google the Access groups on
"startup properties" with or without the quotes.

HTH,
TC (MVP Access)
http://tc2.atspace.com
 
TC said:
It is desirable for various reas0ons to split your fatabase into a
front end/back end structure.
Click to expand...


Is "fatabase" the technical term for a database which needs splitting into
two thinner parts?
 
Anthony England said:
Is "fatabase" the technical term for a database which needs splitting into
two thinner parts?
Click to expand...

Curiously it is my mother-in-law's name.
 
Keith Wilby said:
Curiously it is my mother-in-law's name.
Click to expand...

<ho ho ho>

I saw six men kicking and punching my mother-in-law.
The neighbour said 'Are you going to help?'
I said 'No, Six should be enough.'
 
Thanks TC for the help, I will try and get it sorted when I get back to work
after the Easter holiday.
Nice to see some humour come out of what was a serious question. I had a
good laugh at the replies
 
Back
Top