|
Date and Date/Time keys used in the Booking Templates need to be in ascending order or the template will not work with the file.
The templates are designed to use with your existing Resource files.
The paradigm here is that something is "booked" against a resource. Therefore, a resource is required for the booking file. The Booking file stores the information for the booking, and what is "booked" against the resource can be a customer, internal user, or some freehand type thing as lunch, vacation, Maintenance, downtime, whatever. You have the freedom to decide how you do it. This is usually handled by an entry in the booking file, not necessarily a customer or planned job, to require information. It can be dependant on another file or not, depending on your needs.
Resource Files All you really need for the minimum requirements is a Autoinc SysId with Key, and Resource Name to display for this file. Other optional fields you can use are a Different Field to Display or display order, and/or additional Key for display order if you want. The template is designed to work with your existing Doctor, Dentist, Production Machine, Work Bay, whatever file you want to Book.
ResId LONG - Resource System Id ResName STRING(35) - Name to Display in Resource column Key_ResId KEY(ResId),NOCASE,OPT,PRIMARY,AutoInc ResId - ASCENDING ( For Bookings ) Key_ResName KEY(ResName),DUP,NOCASE,OPT ResName - ASCENDING ( Optional For Display order )
Booking Files Daily The daily booking file can use a standard Appointment type file. Its needs are a SysId Autoinc field and key to update against, and a resource Id field to store the Resource it is booked against , with a Key on the Resource Id, Date and Time to retrieve the records, and an optional GuiId Field/Key. You can have other fields as needed, one to display for Tooltips, one for assigning conditional icons, etc.
SysId LONG - System Id Resource-Employee Id LONG - Resource System Id Date LONG - Date Of Appointment Time LONG - Time of Appointment Duration SHORT - Appointment Duration in minutes Contact STRING(35)- Field to appear in Scheduler AppmntType STRING(20)- For Conditional icon support GuiId STRING(16)- For Remembering recurring appointments settings* Key_By_SysId KEY(SysId),NOCASE,OPT,PRIMARY,Autoinc SysId - ASCENDING (For updating) Key_SchedId_Date_Time KEY(Resource-EmployeeId,Date,Time),DUP,NOCASE,OPT EmployeeId - ASCENDING (For Loading Bookings against Resource) Date - ASCENDING Time - ASCENDING ByGuiIdDateTime - KEY(BAP:GuiId,BAP:Date,BAP:Time),DUP,NOCASE,OPT*
*The GuiId Field/Key is optional and used to remember settings in the using RecurSched and WCRecurReminder templates.
Week, Month, Year The Day Booking file(Week, Month) and Month Booking File (Year) are very similar to the Daily booking file, but do not require a time field, or its inclusion in the key. Its needs are a SysId Autoinc field and key to update against, and a resource Id field to store the Resource it is booked against , with a Key on the Resource Id and Date to retrieve the records. You can have other fields as needed, one to display for Tooltips, one for assigning conditional icons, etc.
SysId LONG - Booking Day System Id ResId LONG - Resource Id to Book Against StartDate LONG - Day Booking Starts Duration SHORT - Number of Days(or Months) of Booking DisplayContact STRING(35) - Information to Display or for ToolTip BookingType STRING(20) - Can Use for Conditional Icons Key_By_SysId KEY(SysId),NOCASE,OPT,PRIMARY,Autoinc SysId - ASCENDING (For updating) Key_By_Resc_Date KEY(ResId,StartDate),DUP,NOCASE,OPT ResId - ASCENDING (For Loading Bookings against Resource) StartDate - ASCENDING
Customer, Consumer, User Files. Whatever your existing files are, as needed to book against the resource. Use lookups, etc in your forms. You can also allow free form entry for Vacation, upkeep, maintenance, etc depending on what you are booking.
|