How to ?

  • Thread starter Thread starter Mike J
  • Start date Start date
M

Mike J

I am considering designing and coding a project for a
customer. The project would be similar to how an
organizer works -- keep track of appointments etc. Every
hour would be split up into 8 min increments -- 12:00,
12:08. 12:16...etc. This would we done between the hours
of 8 - 5 which means there could be 56+ spaces for entries.
Now I could create a table with 56+ columns but that seems
inefficient. Could someone point me in the right
direction for this type of design which would store the
entry in the right time spot and then retrieve it?
Thanks!
 
You can certainly sit and starting coding and writing such a system.
However, setting up a such a system will take quite a bit of work and skill.

Have you tried using Outlook? Or, perhaps a better question is why not use
Outlook?

I see many a Dentists, Doctors office use outlook. What is great is it has
all the time slots made for you, and you can put in contacts etc. Further,
you can even printout nice calendar displays.

It would take a LOT of work to make the above....and the above is already
done in outlook?
 
-----Original Message-----
You can certainly sit and starting coding and writing such a system.
However, setting up a such a system will take quite a bit of work and skill.

Have you tried using Outlook? Or, perhaps a better question is why not use
Outlook?

I see many a Dentists, Doctors office use outlook. What is great is it has
all the time slots made for you, and you can put in contacts etc. Further,
you can even printout nice calendar displays.

It would take a LOT of work to make the above....and the above is already
done in outlook?

--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
(e-mail address removed)
http://www.attcanada.net/~kallal.msn


.
I understand what you are saying except this project is
Click to expand...
not really an organizer per say. I just want to know in
general terms or more how something would be stored at a
certain predetermined time slot.
 
Ok....I can only make a few suggestions here:

First..if you can...don't create a whole bunch of time slots for each day
(too much work..and for each day you have to create a whole bunch of
records.

The best approach is to let people book into a day with a start..and a end
time slot. You then prevent collisions. This code is MUCH less then the
typical design where you create a whole bunch of blank records (separated by
15 min intervals). So, just put bookings into each day with a start/end
time. That means for one day..if you only have two bookings..then you only
have two records...not a zillion little records split by 15 minutes.

So, just store records with a date+time start...and a date+time end value.

I actaully think that the reocrd storage part is easy...the diffciult part
is writing up a nice UI for the users....and likey this means a un-bound
form....
 
Back
Top