I think I have downloaded and researched every reference on the WWW to calendaring as it pertains to MS Access; I know the beginning and I know the end - I just can't make the leap to the middle. I've attached a graphic explaining each, now for the operational narrative followed by my question(s).
Operational Scenario
Setup
The admin will access the user form and schedule an event (A, B, C and Unavailable). Each event A, B, C will have a maximum number of assignments that can be processed that day.
The admin will then select a recurrence pattern (looks suspicously like the layout of another application we all know). Finally, they will enter a range of recurrence: start and end/interval/perpetual (see User Form).
Execution
The admin on other forms (A/B/C) will double-click a date control and it will call up a calendar for date picking. The result of the the setup will be displayed for the admin (see Desired Output - the graphic only has one week for demo purposes). In this manner, the user can visually interpret what date to click on based on their current form.
Problem
User Presentation of Desired Output
My basic take on this is at the end of all the logic I only need 3 pieces of data for the correct formatting of the output: (1) Date, (2) EventType and (3) MaxAssign.
Note: If the admin selects Unavailable, it will have a 'higher priority' and override whatever event was scheduled that day.
Presentation logic will determine precedence for correct formatting of output (e.g., if Unavailable then this formatting over all else).
Through my research, I think I have scrounged enough code and can hack my way through but what I don't know is the best implementation of structure (hence logic follows) to get from the User Form to the Desired Output in terms of table design. I could do this by storing each event in a table but I am hung up and greatly desire to create a perpetual application which would make said table infinitely large and undoable.
My thinking is that the calendar popup would take in the event data, sort it/group it/calculate/interpolate/extrapolate it for presentation purposes (only stored data is the event record). So if event A occurred every 2nd Monday of the Month, it would change the text accordingly on that date.
I have pondered the idea of modifying or somehow overloading the API (for Access '07 DatePicker), but read that this is unadviseable. I have also thought of bridging Outlook for this, but a requirement is that this should be self-contained.
I can code the input and code the formatted output, but my overall question is; how should the event table be set up (additional items to form) and what would the psuedo-code look like to boil the table down to the 3 pieces of required data?
Thanks to any who reply. If there is something out there I missed, I will gladly take it, and if not, any thoughts that will point me in a general direction with be greatly, humoungsly appreciated.
Once completed, I will post this sub-project up here for reviews and any 'hey, it could be better optimized by.... '
-dK
Operational Scenario
Setup
The admin will access the user form and schedule an event (A, B, C and Unavailable). Each event A, B, C will have a maximum number of assignments that can be processed that day.
The admin will then select a recurrence pattern (looks suspicously like the layout of another application we all know). Finally, they will enter a range of recurrence: start and end/interval/perpetual (see User Form).
Execution
The admin on other forms (A/B/C) will double-click a date control and it will call up a calendar for date picking. The result of the the setup will be displayed for the admin (see Desired Output - the graphic only has one week for demo purposes). In this manner, the user can visually interpret what date to click on based on their current form.
Problem
User Presentation of Desired Output
My basic take on this is at the end of all the logic I only need 3 pieces of data for the correct formatting of the output: (1) Date, (2) EventType and (3) MaxAssign.
Note: If the admin selects Unavailable, it will have a 'higher priority' and override whatever event was scheduled that day.
Presentation logic will determine precedence for correct formatting of output (e.g., if Unavailable then this formatting over all else).
Through my research, I think I have scrounged enough code and can hack my way through but what I don't know is the best implementation of structure (hence logic follows) to get from the User Form to the Desired Output in terms of table design. I could do this by storing each event in a table but I am hung up and greatly desire to create a perpetual application which would make said table infinitely large and undoable.
My thinking is that the calendar popup would take in the event data, sort it/group it/calculate/interpolate/extrapolate it for presentation purposes (only stored data is the event record). So if event A occurred every 2nd Monday of the Month, it would change the text accordingly on that date.
I have pondered the idea of modifying or somehow overloading the API (for Access '07 DatePicker), but read that this is unadviseable. I have also thought of bridging Outlook for this, but a requirement is that this should be self-contained.
I can code the input and code the formatted output, but my overall question is; how should the event table be set up (additional items to form) and what would the psuedo-code look like to boil the table down to the 3 pieces of required data?
Thanks to any who reply. If there is something out there I missed, I will gladly take it, and if not, any thoughts that will point me in a general direction with be greatly, humoungsly appreciated.
Once completed, I will post this sub-project up here for reviews and any 'hey, it could be better optimized by.... '
-dK