McKilty
2010-08-26 18:59:59 UTC
Okay, I'm working on a project that is totally kicking my butt and
makes me want to throw in the towel. I would appreciate your
thoughts, advice, guidance, code, suggestions, etc with this.
My boss has asked me to develop an database in MS Access 2010 in which
he will create his Weekly Plan. There are forms for Weekly Notes,
Daily Notes, Weekly Budget Notes, and Calendar Items. He enters
information into these four forms, and send a PDF report to his
executive staff.
The Weekly Notes, Daily Notes, and Weekly Budget Notes all come from
him. The Calendar Items come from Outlook. For these, he wants to
record additional information (Preparation, Energy Budget, Planning
Budget, Hourly Budget, Must have.) Most of these calendar items are
recurring and he needs to record information for these fields for each
and every recurrence.
He needs to be able to access this planner when he is not online and
connected to Exchange.
My idea what to have a routine he would run while connected that would
import all of his calendar items for a selected date range (Between
Date-7 and Date+10) into an Access table with each recurrences. This
table would also have the extra fields he will record. If any of the
information in Outlook changes, it needs to update those changes in
Access.
To be able to update Access, there needs to be a link back to
Outlook. The Entry ID can be longer than 255 characters, so it needs
to be a memo field and cannot be indexed. So my plan was to loop
through each recurrence between those dates and assign an ID from
Access.
Does this make sense to do it this way? Is there a better way?
I thought I had this working, but when single occurring items were
imported to Access, and then later changed to recurring items in
Outlook, the ID I assign is assigned to all recurrences. I worked
that out using two ID fields, but now it seems I cannot write to
Outlook consistently (see this post:
http://groups.google.com/group/microsoft.public.office.developer.outlook.vba/browse_thread/thread/c2b6097ca03bd527?hl=en#)
I'm at my wits ends. Luckily the boss has been away on travel, but
he'll be back tonight or tomorrow, and my progress will be "Yeah, I um
didn't make any progress. In fact, I went backwards."
My programming background is best described as a self-taught
scratcher. I figure out how to do things by finding code samples on
the internet or using samples from the MS library Seriously, I wish
the boss would just hire a Slovak, Mosher, or Streblechenko to do this
for him. He'd have plenty of work for any one of those three for
sure.
Thanks for reading this,
Rick
makes me want to throw in the towel. I would appreciate your
thoughts, advice, guidance, code, suggestions, etc with this.
My boss has asked me to develop an database in MS Access 2010 in which
he will create his Weekly Plan. There are forms for Weekly Notes,
Daily Notes, Weekly Budget Notes, and Calendar Items. He enters
information into these four forms, and send a PDF report to his
executive staff.
The Weekly Notes, Daily Notes, and Weekly Budget Notes all come from
him. The Calendar Items come from Outlook. For these, he wants to
record additional information (Preparation, Energy Budget, Planning
Budget, Hourly Budget, Must have.) Most of these calendar items are
recurring and he needs to record information for these fields for each
and every recurrence.
He needs to be able to access this planner when he is not online and
connected to Exchange.
My idea what to have a routine he would run while connected that would
import all of his calendar items for a selected date range (Between
Date-7 and Date+10) into an Access table with each recurrences. This
table would also have the extra fields he will record. If any of the
information in Outlook changes, it needs to update those changes in
Access.
To be able to update Access, there needs to be a link back to
Outlook. The Entry ID can be longer than 255 characters, so it needs
to be a memo field and cannot be indexed. So my plan was to loop
through each recurrence between those dates and assign an ID from
Access.
Does this make sense to do it this way? Is there a better way?
I thought I had this working, but when single occurring items were
imported to Access, and then later changed to recurring items in
Outlook, the ID I assign is assigned to all recurrences. I worked
that out using two ID fields, but now it seems I cannot write to
Outlook consistently (see this post:
http://groups.google.com/group/microsoft.public.office.developer.outlook.vba/browse_thread/thread/c2b6097ca03bd527?hl=en#)
I'm at my wits ends. Luckily the boss has been away on travel, but
he'll be back tonight or tomorrow, and my progress will be "Yeah, I um
didn't make any progress. In fact, I went backwards."
My programming background is best described as a self-taught
scratcher. I figure out how to do things by finding code samples on
the internet or using samples from the MS library Seriously, I wish
the boss would just hire a Slovak, Mosher, or Streblechenko to do this
for him. He'd have plenty of work for any one of those three for
sure.
Thanks for reading this,
Rick