what about you make a timestamp when its reserved and right before your code where you count up how many are free, you remove all reservations which:
current time - time stamp > time limit ----- Original Message ----- From: "Dan Stein" <[EMAIL PROTECTED]> To: "Multiple recipients of list witango-talk" <[EMAIL PROTECTED]> Sent: Monday, December 30, 2002 12:04 PM Subject: Re: Witango-Talk: Courses Full? > I thought of that but what do I do then if they never finish the > registration for some reason so the course is not paid for. > > Your right that I want to pull it out of inventory but how do I get it back > in if they don't actually make a purchase. > > > -- > Dan Stein > Digital Software Solutions > 799 Evergreen Circle > Telford PA 18969 > Land: 215-799-0192 > Mobile: 610-256-2843 > Fax 413-410-9682 > FMP, WiTango, EDI,SQL 2000 > [EMAIL PROTECTED] > www.dss-db.com > > > > From: "Tom Ferguson" <[EMAIL PROTECTED]> > > Reply-To: [EMAIL PROTECTED] > > Date: Mon, 30 Dec 2002 14:50:11 -0500 > > To: Multiple recipients of list witango-talk <[EMAIL PROTECTED]> > > Subject: RE: Witango-Talk: Courses Full? > > > > well, if you think of this "shopping cart" as an actual shopping cart, you > > could reduce your class "inventory" as soon as it was put in the cart. So > > if Mrs. Smith put little Billy on the class list, it would be full and not > > allow her to pick that same class for Jill. Then she has the option of > > putting Billy's class "back on the shelf". > > > > I'd also be sure to timestamp the transactions... just in case. > > > >> -----Original Message----- > >> From: [EMAIL PROTECTED] > >> [mailto:[EMAIL PROTECTED]]On Behalf Of Dan Stein > >> Sent: Monday, December 30, 2002 2:36 PM > >> To: Multiple recipients of list witango-talk > >> Subject: Witango-Talk: Courses Full? > >> > >> > >> Looking for suggestions. > >> > >> I have a community school application that allows users to sign up for > >> courses on line. For 90% of the courses the max amount of classes is not > >> critical. One or two over makes no difference. And class demand > >> is not high. > >> > >> Therefore this system works fine. > >> > >> When a user selects a course it is put in their basket. > >> > >> When the pay for the course(s) the course count is increased by one and if > >> it is = or > course max then course is closed. > >> > >> But now we are adding these kids swim program courses. They are > >> limited and > >> highly competitive to get in. Probably 150 people will sign up > >> kids between > >> 8 and 10 AM the 1st day. > >> > >> My problem is how to keep the course count accurate when they sign up more > >> than one kid in their family. > >> > >> So here is the scenario. > >> > >> Mrs. Smith has 3 kids > >> > >> She logs into the site and goes to registration > >> > >> She gets a drop down list of her family members. > >> > >> She picks bill and swimming and puts course 1401 in her basket ( there is > >> room for 32 kids and bill makes number 32) > >> > >> She then goes to add Jill > >> > >> She selects the same course > >> > >> Without counting Bill it is still open but in reality if she were > >> to pay for > >> Bills course now it would be closed. > >> > >> The system will think it is open and allow her to add Jill but now we are > >> one over. > >> > >> > >> The other issue is with so many people signing up at once while a > >> course is > >> open when you 1st sign up by the time you get to the checkout it might be > >> closed. > >> > >> I can deal with this last one I guess by checking the course count again > >> before checkout and if the course is now closed show them that > >> and wait list > >> them removing the charge. > >> > >> Any other thoughts on how to handle this? > >> > >> > >> -- > >> Dan Stein > >> Digital Software Solutions > >> 799 Evergreen Circle > >> Telford PA 18969 > >> Land: 215-799-0192 > >> Mobile: 610-256-2843 > >> Fax 413-410-9682 > >> FMP, WiTango, EDI,SQL 2000 > >> [EMAIL PROTECTED] > >> www.dss-db.com > >> > >> > >> ________________________________________________________________________ > >> TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] > >> with unsubscribe witango-talk in the message body > > > > ________________________________________________________________________ > > TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] > > with unsubscribe witango-talk in the message body > > > > ________________________________________________________________________ > TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] > with unsubscribe witango-talk in the message body ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body
