Why use our components

Innobate developed its  ActiveX components in response to the vacuum of third-party scheduling components. Few companies have any type of scheduling software available. The selection that is available is incomplete at best and non-functional at worst. Many of the existing applications deal mainly with scheduling in a very narrow context, such as employee scheduling or task scheduling. Many of these applications display the schedules as Gantt graphs. Most people who have created schedules by hand are familiar with the diary model or grid display. This appears to be an obvious way to display scheduled information; however the lack of software that displays information in these formats is noticeably missing. 

To fill in the void, Innobate offers general-purpose software components that may be used to display scheduled information of almost any type, in many, different formats. Our DayView component displays information in a common format with time and date on opposite axes, an interface most people are already familiar with from using manual paper based diaries. It can display an arbitrarily large schedule, allowing for 2GB of data or as much as the back end database can handle. There are conflict resolution routines that can determine if a change will cause a conflict with other appointments. A warning may also be given to the user in this situation, if need be. 

Innobate's suite of scheduling ActiveX components will not only allow to display schedule information in a grid with multiple configurations but also be used to display this information in WeekView or MonthView formats as well. The MonthView component shows information in the Month format popularized by MS-Outlook. This view allows the user to see a month at a glance. For those who are accustomed to viewing information in an diary book format, they will not be disappointed because the Innobate DiaryView offers this view as well. 

Most of the functionality available may be used with little or no coding. There are many properties that may be set to configure the behavior of the Dayview. These properties control almost all of the functionality and behavior of the software. Customizations may be added in code. Opportunities are given to override the default behavior of all the shedule components by using the provided events. There are procedures for most common events. For example there is a Click and DoubleClick event. The first may be used to highlight an appointment. The latter maybe used to open a appointment window where more details can be entered for the appointment as a booked session.

In all, the components are truly general purpose. These components allow the developer full control over the display and behavior of every aspect of their existence. The controls were designed to allow maximum flexibility over almost any type of scheduling scenario.