Muliple forms on a single page???

Question

Hello guys,
I have 3 tables, all of these tables have one column(p_id) in common to maintain one-one relationship btw 1st n 2nd table and in the same way 1st and the 3rd table.
Using the 1st table I am creating a form on the 1st page, and I have created trigger with sequence for auto increment of the primary key value.
Now after clicking "Enroll " button(which does two things first is it increments the p_id(pk key) value and second is navigating to next page, and into the enter application I'm playing with this newly creating p_id value)
So this is what I have achieved so far, now I am creating two forms on next coming 6th page(both the forms on same page) and both the forms are design using two different tables(i mean to say 2nd and 3rd table, which I describe above) and both these table have one-to-one relationship with the 1st tables(1st page form).
Now I am aware about the limitation for of the automatic "row fetch" and "row processing" processes: they were designed to work with one table, hence as per the below link:-
Report & form on Multiple table
I created "view" and "instead of" trigger for add/update/delete, but some how I am unable to do so.
So if somebody can help me out with the critical issue, I would be appreciated to him very much...
If anybody want I can create example on apex.oracle.com workspace and can give credentials.
regards,
Kumar

Answer 1

I'm afraid I have to agree with Dan, I have lost track of the goal here. If you will permit the use of an idiom, you seem to be swimming against the current. My experience with Apex indicates that this almost always means you are doing something wrong (again, spoken from hard experience).
Please give this a try, invest an hour or so in experimentation and I don't think you will be sorry:
1. Take a piece of paper and lay out your complete page flow from beginning to end. Try to keep each step small and simple. Take 5 minutes, tops.
2. Use the Wizard page template to set up a basic set of pages, one for each page in your flow.
3. On each page, set up the fields you need to capture; just start with a few and don't worry about the layout or look and feel.
4. If you want to capture what a user has entered on a step, regardless of how far they made it through the process (say you want to find out where people are "giving up" on a work flow), create a pl/sql process on each page to log that page's data into a table and only execute the process when the Next button is pressed (you will have to deal with the case where someone is updating something that has already been saved one or more times).
5. On the last page, create a pl/sql process to "finalize" the flow and associate that with the Finish button. You can also clear the cache for all of the pages in the flow if the user clicks the Cancel button or after your "finalize" procedure is complete.
Unless you really need to capture where someone is dropping out of a flow, I don't see why you want to store each page's data in a table. You are just giving yourself something to (a) keep up with and (b) clean up later.
-Tom
PS - I worked through a quick example and saw that misspoke in my previous post: the values for fields entered on earlier pages in a wizard are cached, not stored as hidden fields on the current page.