What are you doing exactly that will need more than 1400 levels???

The whole question is here "when trigger fires". Not a bad guess at all .

Also one other thing, if you have a user defined datatype you will get 2 rows for those columns... unless you didn't build the query exactly as I did back...

You're right it's possible. Did you try my trick???

Actually even if you have no row, you should have a PK... unless you don't want to have an actual table .

That's why I like to be the only programmer in the place .

You'd have to code everything with dynamic sql on the server anyways to do this. It might be easier to do it client side. Unless someone has some mapping trick...

We you can shorten to create param code to 1 line, but in any case you have to set all 25 parameters. I have no problems with that anymore...

A table is still a table, and it has to have some sort of unique key that uniquely identifies the data. Do you have an exemple of such a...

What happens if you copy the parameters to local variables and use those in the query?

This would seem like a lousy workaround,

from the "main" sp :

insert into #temptable (col1, col2)

exec dbo.SubSP params

Now you have a copy of the recordset in a temp table. ...

As far as I know access need at least a unique constraint to work. There are many problems related to that and you apparently discovered another one. BTW why...

Yup, I made it for insert/updates in case you have inserts with that flags on... but this is not necessary if that flag can only be updated.

Happy to hear that.

Welcome to the club... the not enough coffee club .