Scheduling with FileMaker

[jasonwood]

Howdy folks!

I would like to use FileMaker to create a scheduling system. For arguments sake, lets say I was a chiropractor, and I needed a system in which I could schedule my clients for different times. Obviously, there would have to be layouts/reports to provide an overview of what time slots are available, what's taken, and so on.

I am quite famiar with most of the technical aspects of FileMaker databases, I just can't seem to develope in my mind how this would all fit together.

I would think that I should have one database file "Appointments" and each one would have a date and a start/end time. Now how would I report on this in a calendar format so I could see an overview of my schedule/availability?

To make it a little bit trickier, let's say there are two chiropractors that work in my office, so there could be two appointments at the same time, as long as they were with different chiropractors.

PS: I'm not a chiropractor.

Thanks!

[LiveOak]

This is a real "how do I build a space shuttle?" question. The scope of the answer goes far beyond what can be reasonably answered here. You've got the right idea on how to store appointments. The general answer to how to display in a calendar format is using a lot of relationships. The answer to how to manage overlap is to use a multi-key on each appointment with one entry for each time slot occupied. For instance, if you have 8 time slots in 8 hours and an appointment occupied the first two slots, the multi-key entry would be:

1

2

This type of application is not all that simple. Comprehensive systems are quite complex. Steve at OceanWest (forum owner) has about 2 man years in a scheduling application. Such applications for commercial purposes license at about $500+ per month for a few seats.

-bd

[ November 12, 2001: Message edited by: LiveOak ]

[jasonwood]

ya I am beginning to realize this as well. It's not really that I'm missing the point, it's just REALLY hard!

I think the best solution would be to have fixed time slots, each given a value.

Then call for them in portals.

It kinda takes away a lot of flexibility, but it might just be enough for some of the possible applications I had in mind.

PS: Sorry about the two threads thing, I must have pressed the back button a few too many times!-)