>
> on rereading your post - your storing session data in a db, why bother;
> secondly
> it sounds like you just overwriting the session record with a new
> transaction
> id rather than adding a new transaction id [record] and leaving any
> already existing
> transactions available.
>
> basically p
For what it's worth, I like Jochem's solution much better than the one
I gave you. :)
On 8/11/06, Jochem Maas <[EMAIL PROTECTED]> wrote:
a very crude idea below (you have to add a request variable named 'ordertransid'
in all links pointing to pages that have to act on an existing order
transac
Based on the general description you've given, I could imagine adding
a 'step number' in your session. Then validate it against what step
is being loaded. So, if you set your Session 'step' variable to 5,
and page 6 is loaded, that would seem OK. If your Session 'step'
variable is 6, and page 2
[EMAIL PROTECTED] wrote:
> I'll try to explain my problem as better as I can. Please, be "gentle" :)
>
> I developed a program for our salespeople (only them, no public) where
> they can order items for their customers. Order form is made of 6 pages
> (order info, items info, artwork, ad copies,..
I'll try to explain my problem as better as I can. Please, be "gentle" :)
I developed a program for our salespeople (only them, no public) where
they can order items for their customers. Order form is made of 6 pages
(order info, items info, artwork, ad copies,...). Also, they use the same
program
5 matches
Mail list logo
