Sharing a database on a network

I've created a database that tracks employees time. In this database they
are able to post their hours inf a form and then generate a biweekly
timesheet report to be submitted to payroll.

My problem....
I don't know how to make this an effective multiuser db. I have little
networking and sharing skills. There may be up to 8-10 employees who will be
using this db at the same time. Is it possible to set this up. If possible
how can it be set up so that this db only shows the individual employee just
their information, but the manager be able to view everyone's info..

I hope this makes sense. Please help

--
Message posted via http://www.accessmonster.com

Split your database. Use a separate front-end for everyone, assuming that
they all use their own computer. Just set filters so they can only see their
own information. You will need a server that you can put the back-end on, so
that everyone can link to it.

"najah via AccessMonster.com" wrote:

I've created a database that tracks employees time. In this database they
are able to post their hours inf a form and then generate a biweekly
timesheet report to be submitted to payroll.

My problem....
I don't know how to make this an effective multiuser db. I have little
networking and sharing skills. There may be up to 8-10 employees who will be
using this db at the same time. Is it possible to set this up. If possible
how can it be set up so that this db only shows the individual employee just
their information, but the manager be able to view everyone's info..

I hope this makes sense. Please help

--
Message posted via http://www.accessmonster.com

Thanks for the info.
As I stated this may be out of my league. However, let me attempt get a
little clarity.

Are you stating that instead of deploying the same front end copy to 10
workstations, I should create 10 individual front end databases that are
linked to the Back end database stored on the server. In doing so, how do I
apply a filter so that the employee can only view and enter their own
information.

Split your database. Use a separate front-end for everyone, assuming that
they all use their own computer. Just set filters so they can only see their
own information. You will need a server that you can put the back-end on, so
that everyone can link to it.

I've created a database that tracks employees time. In this database they
are able to post their hours inf a form and then generate a biweekly
[quoted text clipped - 8 lines]

I hope this makes sense. Please help

--
Message posted via http://www.accessmonster.com

Are you stating that instead of deploying the same front end copy to 10
workstations, I should create 10 individual front end databases that are
linked to the Back end database stored on the server. In doing so, how do I
apply a filter so that the employee can only view and enter their own
information.

Your backend contains all of your tables, and the tables contain all of the
data. Your front end contains queries/forms/reports, but links to the share
on the server where your backend resides. Once you have created the
queries/forms/reports, you can make copies of the master front end, and then
modify those copies depending on who is getting them. You set up your
filters from the very beginning, in your master copy, but in the master copy
you set the filters to give you all information. In all the individual
copies, you set the filter for the particular person who is getting it. Only
takes a few minutes, because the filter is set in the queries, and you
shouldn't need many of those. Then you lock the copies of the database, once
they are ready to be given out, so that people can't easily go in and change
the filter.

There are more elegant ways to do this, but this is a quick-and-dirty
solution.

Your information is very informative, and has help me tremendously, in
understanding this topic. However, It's the doing that has me stuck.

Let me explain to you again what's going on, and I may have just me this
simple task too complex for my own good.

I have a mainform Timesheet which contains fields such as [TimesheetID]
;EmployeeID]; [StartDate];[EndDate] and a subform TimesheetHours which
contains the work week details such as [Date], [TAskid],[hours] Both of these
forms are based on tables, not queries. They then run a report that
calculates their daily hours, and a biweekly total. From this entry we are
able to run various time tracking reports according to tasks, daily hours,
etc.

They enter their time via a switchboard button, that opens the form in add
mode. From the switchboard the employees also have the capabilities to view
specific Timesheets(reports) based on start/end date. These reports are based
on a parameter query.

I need for them to be able to click a button on the switchboard that allows
them to edit/modify their timesheet, However, when they click this button
they only have access to their timesheet info.

How would I apply this filter. I don't know how to do this. Can you give me
a step by step example.

mnature wrote:
Are you stating that instead of deploying the same front end copy to 10
workstations, I should create 10 individual front end databases that are
linked to the Back end database stored on the server. In doing so, how do I
apply a filter so that the employee can only view and enter their own
information.

Your backend contains all of your tables, and the tables contain all of the
data. Your front end contains queries/forms/reports, but links to the share
on the server where your backend resides. Once you have created the
queries/forms/reports, you can make copies of the master front end, and then
modify those copies depending on who is getting them. You set up your
filters from the very beginning, in your master copy, but in the master copy
you set the filters to give you all information. In all the individual
copies, you set the filter for the particular person who is getting it. Only
takes a few minutes, because the filter is set in the queries, and you
shouldn't need many of those. Then you lock the copies of the database, once
they are ready to be given out, so that people can't easily go in and change
the filter.

There are more elegant ways to do this, but this is a quick-and-dirty
solution.

--
Message posted via http://www.accessmonster.com