By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,089 Members | 2,069 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,089 IT Pros & Developers. It's quick & easy.

Adding a scheduling component to Access

P: n/a
Here's the scenario. I'm building an integrated electronic health
record for maternal/infant outpatient case management for my employer,
a hospital. We are basing the EHR in Access 2003 (fully expecting to
move to SQL server after we go live and add users).

One core piece of the database involves the users' need to manage
schedules from within the EHR. I need an ability to push appointments
from Access to Outlook 2003/Exchange, and to read those appointments
back for reporting.

Obviously, simply linking tables is not a robust solution.

I'm wondering, in broad terms, what you good people recommend.

I'm not absolutely beholden to Outlook if there is a different
schedule-management solution that might be more appropriate.

Nov 10 '06 #1
Share this Question
Share on Google+
4 Replies


P: n/a
On 10 Nov 2006 13:10:41 -0800, "Jason Gillikin"
<gi************@gmail.comwrote:

Outlook can display the schedule for you, but it will not manage it -
that's up to your app to do.
I like apps that integrate tightly with Outlook. WithEvents can be
very powerful. Unfortunately the Outlook event model is somewhat
uneven; I think better in O2003 than before.
Managing schedules can be done efficiently in MsProject.

-Tom.

>Here's the scenario. I'm building an integrated electronic health
record for maternal/infant outpatient case management for my employer,
a hospital. We are basing the EHR in Access 2003 (fully expecting to
move to SQL server after we go live and add users).

One core piece of the database involves the users' need to manage
schedules from within the EHR. I need an ability to push appointments
from Access to Outlook 2003/Exchange, and to read those appointments
back for reporting.

Obviously, simply linking tables is not a robust solution.

I'm wondering, in broad terms, what you good people recommend.

I'm not absolutely beholden to Outlook if there is a different
schedule-management solution that might be more appropriate.
Nov 11 '06 #2

P: n/a
Thanks, Tom. I'm wondering what people think about the most
appropriate and user-friendly model for adding a relatively robust
schedule-management function to an Access database might entail. Do it
all internally, with tables? Or integrate to some degree with
Exchange/Outlook? Or find a groupware solution?

This is one area where I don't have a lot of experience, so any counsel
I can get is most helpful.

Tom van Stiphout wrote:
On 10 Nov 2006 13:10:41 -0800, "Jason Gillikin"
<gi************@gmail.comwrote:

Outlook can display the schedule for you, but it will not manage it -
that's up to your app to do.
I like apps that integrate tightly with Outlook. WithEvents can be
very powerful. Unfortunately the Outlook event model is somewhat
uneven; I think better in O2003 than before.
Managing schedules can be done efficiently in MsProject.

-Tom.

Here's the scenario. I'm building an integrated electronic health
record for maternal/infant outpatient case management for my employer,
a hospital. We are basing the EHR in Access 2003 (fully expecting to
move to SQL server after we go live and add users).

One core piece of the database involves the users' need to manage
schedules from within the EHR. I need an ability to push appointments
from Access to Outlook 2003/Exchange, and to read those appointments
back for reporting.

Obviously, simply linking tables is not a robust solution.

I'm wondering, in broad terms, what you good people recommend.

I'm not absolutely beholden to Outlook if there is a different
schedule-management solution that might be more appropriate.
Nov 13 '06 #3

P: n/a
The answer depends entirely on your audience:

If everyone who will be using the app is guaranteed to have Outlook, then
why not use the power and features already there? There are several sites
with information on Outlook and Access, such as:

http://www.outlookcode.com/d/index.htm

If even one user may NOT have Outlook, then don't attempt to use it.

--
Darryl Kerkeslager

"Jason Gillikin" <gi************@gmail.comwrote
Thanks, Tom. I'm wondering what people think about the most
appropriate and user-friendly model for adding a relatively robust
schedule-management function to an Access database might entail. Do it
all internally, with tables? Or integrate to some degree with
Exchange/Outlook? Or find a groupware solution?

Nov 13 '06 #4

P: n/a
"Darryl Kerkeslager" <ke*********@comcast.netwrote in
news:mv******************************@comcast.com:
The answer depends entirely on your audience:

If everyone who will be using the app is guaranteed to have
Outlook, then why not use the power and features already there?
There are several sites with information on Outlook and Access,
such as:

http://www.outlookcode.com/d/index.htm

If even one user may NOT have Outlook, then don't attempt to use
it.
It's not just having Outlook -- for it to be of any real use, they
have to be using Outlook as an Exchange client.

Really, there's no reason to use Outlook in any other scenario, as
the vast majority of Outlook's good features are unavailable without
Exchange.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
Nov 14 '06 #5

This discussion thread is closed

Replies have been disabled for this discussion.