> Excellent - yes, this is ultimately the same thing I was hoping to achieve:
> a single operation, rather than two or more disparate actions.
>
> Thankyou for the extra info and the link, I will definitely check that out very
> soon ( right now I'm in crunch mode and just to get something working,
> even if it's less elegant ). I'll post to the list if I successfully manage to
> get the single-statement, non-view solution working.
Well for testing purposes it should be fine to explicitly call out currentval. But be careful if
you are going to be using multiply connections at onces. I am not sure that currentval will give
you what you want if another connection calls nextval first before you insert a record to your
child table.
Regards,
Richard Broersma Jr.
