This is really a two part question...

I have a custom script that allow users to request that pages be added to my portal. The script just adds a row to a 'Pending' table with the ParentTabID, so the new Tab will use it as its Parent.

1) What SQL do I need to write so that TabOrder and Level are automatically adjusted for a new Tab, which is generated by looking at the 'Pending' table and processing 1 request. I see that the AddTab Procedure doesn't take TabOrder or Level as params.

2) I know there is the Default template in Portals/_default/Templates. When I have finalised what will constitute my Template I will build another Template XML file that I can use it in the above process. How can I reference the new Template in SQL when I run the above process? Would I need to insert all the default module settings for each new module?

many thanks,

Steve

Thanks, but I'm not writing any new business logic for this process. I want to handle all the logic at the SQL end. I can already process one 'Pending' row, the other things not working are TabOrder and Level. Level would be pretty easy since it would be the Level of the ParentTabID + 1. TabOrder is a different story though. It's almost as if I'd need to create a temp sql table and then reorder the whole tab collection after the new one has been inserted.

There has to be a way to do all of this in SQL. My process script just processes on item in a ListX list. Then it's all handed over to SQL.

Are you saying that the only way this can be done is to use runtime code?

I'll try that again...

Actually Sebastian, you're probably right. I should just