New Database

I am new to Access and working to create an automated way for our service
reps to track their calls. Can someone take a look and provide some feedback?

CUSTOMERS TABLE
Customer ID (primary key)
Name
Address1
Address2
City
St
Zip
Phone
Fax
Email
Notes

REQUESTS TABLE
Customer ID (link to customer ID in Customers Table)
Request Number (auto assigned)
Request Type
User ID (Link to User ID in USER Table)
Open Date
Close Date

USER ID TABLE
USER ID
Employee First Name
Employee Last Name

Microsoft has a template out there for a "Service Call Management" database.
Why don't you start with that as your template, and build on to it instead
of reinventing the wheel?

http://office.microsoft.com/en-gb/te...CT101426031033

--
Rick B



"K Petroski" wrote in message
...
I am new to Access and working to create an automated way for our service
reps to track their calls. Can someone take a look and provide some
feedback?

CUSTOMERS TABLE
Customer ID (primary key)
Name
Address1
Address2
City
St
Zip
Phone
Fax
Email
Notes

REQUESTS TABLE
Customer ID (link to customer ID in Customers Table)
Request Number (auto assigned)
Request Type
User ID (Link to User ID in USER Table)
Open Date
Close Date

USER ID TABLE
USER ID
Employee First Name
Employee Last Name

I am aware of the "Service Call Management" template. The reps taking the
calls are looking for one basic form for data entry purposes only. They will
have access to this one form only for now. I may add addtional features and
functionality later but I need to sell them on the idea of using Access
instead of the manual process they currently have in place.

"Rick B" wrote:

Microsoft has a template out there for a "Service Call Management" database.
Why don't you start with that as your template, and build on to it instead
of reinventing the wheel?

http://office.microsoft.com/en-gb/te...CT101426031033

--
Rick B



"K Petroski" wrote in message
...
I am new to Access and working to create an automated way for our service
reps to track their calls. Can someone take a look and provide some
feedback?

CUSTOMERS TABLE
Customer ID (primary key)
Name
Address1
Address2
City
St
Zip
Phone
Fax
Email
Notes

REQUESTS TABLE
Customer ID (link to customer ID in Customers Table)
Request Number (auto assigned)
Request Type
User ID (Link to User ID in USER Table)
Open Date
Close Date

USER ID TABLE
USER ID
Employee First Name
Employee Last Name

Ok. Not sure how that affects my previous post.

As I stated, use the template, and modify it to meet your needs. If they
don't want the other bells and whistles, tell them not to use them. You
could also delete them, or make them invisible, but I can't imagine that
they would not want the features.

Basically, that database has the structure in place. Use that structure.
In my opinion, it is much easier to take a properly-designed database that
has too many features, and strip a few of them out. Rather than start with
a clean slate and try to build the structure, relationships, forms, reports,
etc.

If it were me, I would leave everything there and roll it out to the users.
As I stated, they don't have to run the reports, queries, etc. if they don't
want to.

--
Rick B



"K Petroski" wrote in message
...
I am aware of the "Service Call Management" template. The reps taking the
calls are looking for one basic form for data entry purposes only. They
will
have access to this one form only for now. I may add addtional features
and
functionality later but I need to sell them on the idea of using Access
instead of the manual process they currently have in place.

"Rick B" wrote:

Microsoft has a template out there for a "Service Call Management"
database.
Why don't you start with that as your template, and build on to it
instead
of reinventing the wheel?

http://office.microsoft.com/en-gb/te...CT101426031033

--
Rick B



"K Petroski" wrote in message
...
I am new to Access and working to create an automated way for our
service
reps to track their calls. Can someone take a look and provide some
feedback?

CUSTOMERS TABLE
Customer ID (primary key)
Name
Address1
Address2
City
St
Zip
Phone
Fax
Email
Notes

REQUESTS TABLE
Customer ID (link to customer ID in Customers Table)
Request Number (auto assigned)
Request Type
User ID (Link to User ID in USER Table)
Open Date
Close Date

USER ID TABLE
USER ID
Employee First Name
Employee Last Name

I am going to use the template as you suggested. Thanks.

"Rick B" wrote:

Ok. Not sure how that affects my previous post.

As I stated, use the template, and modify it to meet your needs. If they
don't want the other bells and whistles, tell them not to use them. You
could also delete them, or make them invisible, but I can't imagine that
they would not want the features.

Basically, that database has the structure in place. Use that structure.
In my opinion, it is much easier to take a properly-designed database that
has too many features, and strip a few of them out. Rather than start with
a clean slate and try to build the structure, relationships, forms, reports,
etc.

If it were me, I would leave everything there and roll it out to the users.
As I stated, they don't have to run the reports, queries, etc. if they don't
want to.

--
Rick B



"K Petroski" wrote in message
...
I am aware of the "Service Call Management" template. The reps taking the
calls are looking for one basic form for data entry purposes only. They
will
have access to this one form only for now. I may add addtional features
and
functionality later but I need to sell them on the idea of using Access
instead of the manual process they currently have in place.

"Rick B" wrote:

Microsoft has a template out there for a "Service Call Management"
database.
Why don't you start with that as your template, and build on to it
instead
of reinventing the wheel?

http://office.microsoft.com/en-gb/te...CT101426031033

--
Rick B



"K Petroski" wrote in message
...
I am new to Access and working to create an automated way for our
service
reps to track their calls. Can someone take a look and provide some
feedback?

CUSTOMERS TABLE
Customer ID (primary key)
Name
Address1
Address2
City
St
Zip
Phone
Fax
Email
Notes

REQUESTS TABLE
Customer ID (link to customer ID in Customers Table)
Request Number (auto assigned)
Request Type
User ID (Link to User ID in USER Table)
Open Date
Close Date

USER ID TABLE
USER ID
Employee First Name
Employee Last Name