No, you don't need a lot of colulmns, you need a lot of ROWS. Customer: CustMaint
Custid Custid Custname DateMaint Custaddress etc. LOTS of row sin the CustMaint table with one row for each date of scheduled maintenance and any other info you need to store about each maintenance visit. David ----- Original Message ----- From: "Phil Nolette (BellSouth)" <[EMAIL PROTECTED]> To: "RBASE-L Mailing List" <[EMAIL PROTECTED]> Sent: Monday, February 10, 2003 4:12 PM Subject: [RBASE-L] - Re: A design approach is requested > Thanks David. > I would lean to Idea 1. I looked through the help section of Rbase (using > the most current of 6.5++) and could not find the max number of columns per > table. Do you know what that would be? I would then have a three > dimensional array? > Phil > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of David M. > Blocker > Sent: Monday, February 10, 2003 10:22 AM > To: RBASE-L Mailing List > Subject: [RBASE-L] - Re: A design approach is requested > > Phil: > > Idea 1: > > Create a table with all days of the year - or a view could be generated > dynamically to generate this from the curent date. YOu set up two tables > for the customer > > Customer ---> MaintenanceSched (many side). > > Entry brings up a check box of the year from the current date and user > checks off scheduled maintenance days. Code does INSERT into Maintenace > using the days checked and the custid. > > Idea 2: > Less labor intensive for the user harder for you. User can set parameters > for a schedule on a form with variables: > > Month #Days per Week Preferred Days > Jan 1 Wed > Feb 1 Wed > March 1 Wed > April 1 Wed > May 1 Wed > June 2 Mon - Wed > July 3 Mon - Wed - Fri > > etc. > > Now you write a program that figures this out by working with the > parameters and your calendar table/view! > > David Blocker > > > Based on the input > ----- Original Message ----- > From: "Phil Nolette (BellSouth)" <[EMAIL PROTECTED]> > To: "RBASE-L Mailing List" <[EMAIL PROTECTED]> > Sent: Monday, February 10, 2003 8:46 AM > Subject: [RBASE-L] - A design approach is requested > > > > > > I am building a database for a swimming pool maintenance company and would > > like to know what the best procedure would be for a maintenance table for > > customers when they request service over a year's period. When the > customer > > signs up for service during the winter months service will only be > performed > > weekly on a special day. As it moves to spring, it would increase > possibly > > to two days per week, and finally during the hot summer months, it may be > > three times a week. > > Would you construct a table keyed by customer ID that would have 365 days > in > > it with a value of 0 or 1 to designate what day service is requested? Or, > > is there a way to show a user entry form that has a months view on it and > > the operator would check what days need servicing? > > I know that whatever process used, it will be difficult to design the > entry > > and reporting portion of this scheduling and maintenance portion and > wanted > > to get the best strategy before venturing off into the right approach. > > Thank you, > > > > Phil Nolette > > http://www.ncsgrp.com/ <http://www.ncsgrp.com/> > > > > > >
