Hi, I know that most of you have solved this one way or another, I just can't find a good way to do this:
What I basically need is to implement the following scenarios: A. user selects action that results in query to database[1] B. query result is presented to user[2] C. user edits and submits form D. data is updated in database and the result is presented again[2] When new data is submitted it is checked that it doesn't already exists. If it doesn't the database is updated and the result is presented (like step D). If it does already exist, some error message/action must be presented/taken. [1] it is a special kind of database for which I have already written some XSP pages. [2] initially data is presented as plain HTML, only when the user selects "edit" the data is presented again in Woody widgets. So the initial page in step B and the page in step D are identical. Problems I run into: - database handling is done in the XSP pages, so I need a "storeNewOrModifiedData" pipeline that puts the data into the database. After that I would like to "jump" to the pipeline I use to display step B, but I don't know how other than to copy the remaining part of that pipeline. - how do I elegantly differentiate between a "normal" query result and errors (e.g. could not connect to database or data already exists)? I've studied every database example I could find, but either the routing from page to page is entirely done in flow (petstore) or I cannot find a satisfying example of how data is stored in the database in all the other examples. I'm sure I miss something here. Note: I cannot use ESQL or any SQLTransformer for my databases, I'll have to write any connection/retrieval/storage myself. Any ideas/recommendations? Thanks and bye, Helma --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
