Hi,
Thanks for the response.
My table structure is pretty basic, as follows;
table name=avail_items
item varchar(255) NULL default '',
PRIMARY KEY (item)
) TYPE=MyISAM;
I was thinking if having more than one field, and ID number for each item, there is 100 items, and I was also experimenting with have a reserved item field to insert the purchased item into, and then displaying a distinct command to only show items that there was one of in the table but I couldn't work that out.
It looks like my table might be wrong too? Should I have a field for each item rather than one field listing each item?
OK so exaclty what I would like to do is have a page with all available items called up, only items in the database are shown here in a list.
I would like my client to be able to choose an item (only one) and submit the choice via a form with some other info to be mailed to me (I know the mail code) when the form is sent I would like to have the item they have chosen deleted from the database or updated, the thing is that it must not show on the order page as available once it has been purchased. This will stop anyone placing an order for the same item as there is only one of each item.
Does that make sense?
So basically I want to call up my list of available items from my database
Have an order placed for an item
Have this item deleted or updated on my database with the action of submitting a form
Have item removed from the list of available items
I'll carry on with my own investigating in the meantime and see how I get along with your table structure... I was pulling my hair out yesterday though!!
Thanks