Combination Data

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

Guest

I am establishing a database for a call center. There are three different
call representatives using a copy of my form for data entry. What is the
best way to link these tables. It can be done continuous or once at the end
of the day just so all the data is in the right place.
 
Link these tables? There should only be ONE table. You should include a
field to store the rep's name or number, but you would not want a separate
table for each.

What is someone needs to work on an issue that was started by a rep who is
at lunch?
 
The representatives are on three seperate computers working at the same time.
How do you propose i combine all their data into a master?
 
A shared database should have the backend (the tables) on a server.

Each PC should have a separate copy of the front-end (the queries, reports,
and forms) on the individual computers.

This is called a "split database".
 
Also, with only three users you could even risk all of them sharing one fiel
on the LAN and not bother to split it. I have run up to ten users without
too many problems, but this does open you up to corruption issues.
 
So at the end of the day when i want all the information to be in a master
table i should just cut and past them all together or is there a way to have
it save to the master?
 
so if i kept them all on the same file would the file change for all of them
when they saved? Could you give me more information on having the three work
off one file on the server.
 
NO.

There is only ONE table for the call records.

You don't have to DO anything.

All the users are writing records to ONE table. Their userid or name, or
number is stored as the "representative" in each record.
 
Just put your databse on the LAN and have each user open the fiel and then
go about their business. Access is a mutli-user application by default.
 
Ok, thank you very much for our help. I took a simple overview class in
database and now a fortune 50 company wants me to be the guru. I use the
message boards a lot so your help is greatly appreicated.
 
You appear to be thinking like a spreadsheet user

Think one copy of the data. Several people use it.. Data flows into and
out of the the centralized tables from many sources.

You do not SAVE records in Access. As soon as you leave a record an go to
the next one it is saved.

With the database on a server. Each rep opens the form as he needs and and
enters data into the data table (The Master/Only table) That table needs a
field for the rep name or code so you will know who made what

The form can be opened with a filter so that rep can only see / work on his
own records. Everything from all reps flows into the same table as they are
working.

You can then make reports that separate the records by each rep or records
from all reps for any day or date range.

While they are working, you can see the data from all of them as it is
populatiing the table.

You need another course to get into the shared and relational aspects of the
database
 
Back
Top