G
GinCan via AccessMonster.com
In a database it is quite normal to have to assign a date to an event, a task,
an appointment, etc. With activeX calendar controls, (or built-in, in Access
2007) it is easy to have a minicalendar popping up.
What to my knowledge is not natively available in Access yet, is the ability
to display database records by date in a Calendar form similar to Outlook
Calendar but self contained within Access. By searching on the internet I
found code and implemented some workarounds but they are so cumbersome and so
very heavy on resources.
What surprises me (actually really frustrates me...) is that when designing
Access forms on PCs with MS Office or MS Works installed, we discover quite a
number of DLLs and References and Objects with encouraging names such as:
-"Microsoft Outlook Controls" (outlctl.dll),
-"Outlook Object Libary" (msoutlb.dll),
-"Microsoft Works Calendar Type Library", etc.
Some of these activeX I can actually drag onto a form but I have never been
able to work out or raise a form similar to a calendar. Some other objects
like "Microsoft Works Calendar Block Control" or "Microsoft Works Calendar
Month Control", immediatly crash my Access 2003, upon being dragged onto the
form.
It seemed logical to me that these objects -properly referenced and
registered- could have been used as ActiveXs in a Form and would make
available all the features of Calendaring (like adding a new item directly to
the calendar, displaying week/month/year views, etc.).
Am I missing something? Has any one been able to implement an easy calendar
form using any of these ActiveX or it is deliberate Microsoft policy to make
this so difficult?
Thank you for any suggestion and comments.
an appointment, etc. With activeX calendar controls, (or built-in, in Access
2007) it is easy to have a minicalendar popping up.
What to my knowledge is not natively available in Access yet, is the ability
to display database records by date in a Calendar form similar to Outlook
Calendar but self contained within Access. By searching on the internet I
found code and implemented some workarounds but they are so cumbersome and so
very heavy on resources.
What surprises me (actually really frustrates me...) is that when designing
Access forms on PCs with MS Office or MS Works installed, we discover quite a
number of DLLs and References and Objects with encouraging names such as:
-"Microsoft Outlook Controls" (outlctl.dll),
-"Outlook Object Libary" (msoutlb.dll),
-"Microsoft Works Calendar Type Library", etc.
Some of these activeX I can actually drag onto a form but I have never been
able to work out or raise a form similar to a calendar. Some other objects
like "Microsoft Works Calendar Block Control" or "Microsoft Works Calendar
Month Control", immediatly crash my Access 2003, upon being dragged onto the
form.
It seemed logical to me that these objects -properly referenced and
registered- could have been used as ActiveXs in a Form and would make
available all the features of Calendaring (like adding a new item directly to
the calendar, displaying week/month/year views, etc.).
Am I missing something? Has any one been able to implement an easy calendar
form using any of these ActiveX or it is deliberate Microsoft policy to make
this so difficult?
Thank you for any suggestion and comments.