Hello,
I've been running all of my daily activity transactions (order entry, purchase orders, inventory, pricing) on QA for the last 25 years. It has been a wonderful tool.
I am interested in the client/server abilities (speed) of Sesame, and would eventually need about 10 client licenses.
I've been looking over Sesame's online literature this weekend, and have a couple of questions: 1) I have a number of clients (likely to increase in number) who like to order online. I have a hodgepodge solution currently (build an Excel spreadsheet order page, then use a spreadsheet converter to turn it into a passworded HTML order page (with calculations programming) that allows the client to fill in quantities, print off a copy for their records, and then press a Submit button to email the order form to me. The downside is the form is static, and must be updated and uploaded - with current pricing - often enough to be a time-consumer. Question: Can Sesame produce an active HTML form report that would allow onscreen calculations based upon an online user's input ("quantity entered" x pricing, "Line Item totals summed up for a grand total", etc) ? In other words, for Customer A, can I run a report that shows the items and prices that he has bought in the last 3 months, and then I easily generate an HTML order form that includes product #, product description, product pricing, and blank fields for quantity input, and a calculated 'line item' totals field ...... that can then be posted on the Internet so the client can order product online?
2) In QA, nightly posting routines are very important to give me a current look at what my current inventory product costs are (they change quickly). The daily posting of items from Purchase Orders to my Inventory database will thus allow an inventory item record to tell me the 'last vendor', the last quantity, the last cost, the last po#, the last date the item was purchase. Then the next time I order that item, the most recent cost will be pulled into the Purchase Order, helping us stay up-to-date. Question: How would I accomplish this 'posting' result in Sesame? (maybe I'm thinking about it 2-dimensionally, instead of 3-dimensionally, and can't see how my information would be available without a posting routine - if so, please explain)
I have done all of the QA programming myself, and some of it is pretty intricate (including programming that allows my order screen to pull in client specific pricing on an item (pricing is different on Item A for Customer A versus Customer B). I hope I'm not too old to have one more programming design project left in me.
Larry Seale
|