This is what I'm doing – the following is part of a CRM:
I am using the same table (cu_action_act) to store a calendar event, then optional meta information about certain events. I use the same table because my customer wants to track a timeline for each contact on the CRM.
When the crm user inserts the calendar event, the page either returns to display the event (at event.php), or if a particular type of event is inserted the page redirects to another, hidden page (timeline_steps.php), which automatically inserts a further record in cu_action_act, using the session id (id_act) from the first transaction as a key:
The second transaction does NOT create a session id, as this is not needed:
On creation of the second record, the timeline_steps.php page redirects back to event.php
Several events may be inserted in succession, following this process.
Would it be advisable to create a session id in the second transaction? Would this then clear the incorrect session id in event.php?
Hope this is clear.