C
Cameron Piper
I am presently working on a Acess 2002 database being
designed for Windows and Office XP Professional based
computers.
I have developed an activities manager to manage tasks
for specific clients or for specific projects. The
system tracks a variety of information (ClientID, Type of
task, date due, date assigned, etc.) The company I am
working with has many systems for their tasks. For
example: based on a certain date, they know that they
would have to call their client 20 days prior, send them
an email 5 days prior and set an appointment for that
day. The actual systems that they use are much more
involved using a longer time frame and at times upwards
of 20-30 tasks/reminders/appointments.
As the datbase presently exists, I track task related
information in tblActivity, and associate it with a
client or projects based on a linked field in the client
and/or project table. This system is very effective for
single tasks, but in the event that a task would ever
repeat or in the event of a system of tasks as described
in the previous paragraph I have no idea.
1. I would like to be able to click a button based on a
selected followup system and have all of those tasks put
into place based on a system start or end date. The
database would need to know to associate each task with a
particular client or project and then be able to add the
tasks as a large group of single events to tblActivity.
2. I would like to have the ability to repeat a task,
much like in Microsoft Outlook. After the click of a
button I would like to have the database add the tasks to
tblActivity as a large group of single events.
Does anyone have any thoughts on how this might be
accomplished. I am not asking for the complete solution
right now, just some expert advice on how you would put a
solution like this together.
Cameron Piper
CSPiper@(re.move.)CBBurnet(.no.spam).com
As an aside, I am almost certain that I will get a posted
respone asking why I don't just integrate my database
with Outlook. To answer this question ahead of time, our
defining motivation for writing an access database to run
our office, is so that we can incorporate our entire
business into one program and not have to use any
others. It may seem sureal but the reason that the
databse is being written is so that "one" program can run
our "entire" business.
designed for Windows and Office XP Professional based
computers.
I have developed an activities manager to manage tasks
for specific clients or for specific projects. The
system tracks a variety of information (ClientID, Type of
task, date due, date assigned, etc.) The company I am
working with has many systems for their tasks. For
example: based on a certain date, they know that they
would have to call their client 20 days prior, send them
an email 5 days prior and set an appointment for that
day. The actual systems that they use are much more
involved using a longer time frame and at times upwards
of 20-30 tasks/reminders/appointments.
As the datbase presently exists, I track task related
information in tblActivity, and associate it with a
client or projects based on a linked field in the client
and/or project table. This system is very effective for
single tasks, but in the event that a task would ever
repeat or in the event of a system of tasks as described
in the previous paragraph I have no idea.
1. I would like to be able to click a button based on a
selected followup system and have all of those tasks put
into place based on a system start or end date. The
database would need to know to associate each task with a
particular client or project and then be able to add the
tasks as a large group of single events to tblActivity.
2. I would like to have the ability to repeat a task,
much like in Microsoft Outlook. After the click of a
button I would like to have the database add the tasks to
tblActivity as a large group of single events.
Does anyone have any thoughts on how this might be
accomplished. I am not asking for the complete solution
right now, just some expert advice on how you would put a
solution like this together.
Cameron Piper
CSPiper@(re.move.)CBBurnet(.no.spam).com
As an aside, I am almost certain that I will get a posted
respone asking why I don't just integrate my database
with Outlook. To answer this question ahead of time, our
defining motivation for writing an access database to run
our office, is so that we can incorporate our entire
business into one program and not have to use any
others. It may seem sureal but the reason that the
databse is being written is so that "one" program can run
our "entire" business.