Hi Leland,

Thanks. I looked at your site. The menu looks nice and I like the idea of appearing/disappearing items (dynamic menu). Is it in the separate frame?

>Hi Nadya,
>
>Once the customer had authenticated into the system, I would have some kind of query-by-example form that the customer could fill out and submit. This would create a recordset of merchandise that meets the customer's wishes like all recordings by a particular artist. Adjacent to each item in the recordset, I would have an "Add to Chart" button that when clicked would submit the item into a table of [items selected]. The customer could view his selections at any time by clicking a button that would link to a new page on which all records in the [selected items] table owned by the customer could be view. When the customer reviewed his cart, I would have a button, that when clicked, would delete items from the [selected items] table. On the page where the customer views his order would be a button that when clicked would link back to the query by example form that would allow the customer to grab recordset from the [merchandise on hand] table for items which the customer had an
>interest. Then the customer could continue shopping and adding items he wished to his cart. The customer should be allowed to view his selections at any time and then return back to the list of merchandise avaiable for selection. This could be a problem and may requie an additional table if there were no way to maintain the queried recordset when changing pages. Maybe you could work with the customer's SQL and pass it between pages. When the customer returns to the page where he selects items from his query, the SQL could be re-executed to rebuild the recordset.
>
>Also, the customer should be able to press a button and link back into the page that contains the form which allow for the query of additional items he would like to browse.
>
>Once the customer is ready to check-out, he should be able to click a button that links to the check-out page. This would contain all items in the [selected items] table owned by the customer per his account number.
>
>The check-out from would list all items selected by the customer including description, price, etc. When the customer clicks on the submit button of the check-out page, item he owns in the [selected items] table should be written to the receivables/sales table, items in the [selected items] table owned by the customer should then be deleted.
>
>I don't know whether you plan to track inventory or not, if so you would need to generate something that goes to the shipping department like the customer's purchase order. From the Purchase Order, the shipping department could pull the recordings selected and ship them out. When the customer clicks on the submit button at the check-out, update the [items-in-stock] table for item purchased by the customer. This would be in addition to recording the sale per above. The transactions against the [merchandise-on-hand] table would carry a negative quantity and cost amount repesenting the charged out inventory. The table of [items-on-hand] could be queried at anytime to determine inventory quantities.
>
>I have been working on an example database that might give you some ideas. You probably will not like the interface by you can have a look see at my web site at:
>
>https://www.smvfp.com
>
>Select the menu item [Fun Stufff] --> Example Database --> Add/Edit Records.
>
>I have just re-written it and don't have it fully debugged, but it seem to be working for the most part. Also, I have a new menu system based of java applets that seem to give problems when used with the IE browser, so you may need to refresh the page a few time before the menu works. If the menu system does not stabilize, I will go back to my previous menus.
>
>LelandJ