Need Suggestions... PLEASE!!

[TiMoGo]

I am currently working on an idea for a client...

Unfortunately, it is not really my area of specialty. However, they are a BIG client and I need to make them happy.

I was hoping someone could help me out, or at least point me in the right direction, but find it hard to explain what I need. As such, I kinda threw something together that looks like what I want, even if it does not function at the moment.

The page is currently located at http://www.timogo.com/twcbc/11-07.htm

Again, it does not work, I am guessing I need to use PHP and MySQL to get it to function as I would like it to, but would prefer an option that did not require all of that time and effort. The key is to make it save the changes that are made in the drop-down menus and the text area so that multiple people can see it.

Any help or direction you guys might have to offer would be appreciated!!

:)

[chrishirst]

An appointments database then

It will have to have some kind of data storage and a database schema is the simplest way of going about it.

I assume that you would want each of the selects to reflect the current state of play at each time slot.

Well actually you would want it just to display the information then have an "edit" button to select the one record to change.

[SEFL]

Hirst is right. If you want something like this, you're going to have to put in some time and effort.

PHP/MySQL should do it (I don't know, I'm not a PHP guy).

ASP/Access or SQL Server will do it with about 2-3 hours' worth of effort.

The one thing I would suggest that would make your life somewhat easier is to give all of your select boxes the same name (but NOT the same ID). This would allow you to gather up everything into one form element, which would look something like this:

Available, Pending, Filled, Pending, Filled, Available, Available, Pending

You could then split that up into an array and work with it from there.

[WebSavvy]

PHP/MySQL can use enom type field to house different "selection choices" for the same field.

Example:

field name is schools

enom can be "day care", "primary", "college", "university"

It can even be varchar(255) and have default set "day care" (or whatever) and then selection choice for the type can be supplied during the data insert.

Then when query against the db is made, it can be where schools="$this_type"

(e.g., day care, primary, and so on)

These were used as an example. You would of course craft it to fit your own application and fields.