I was using the DDT and found what I believe to be a minor but irritating bug. I am using Optimisitic Timestamps for my concurrency and have a table for the storage of error events which is meant to be Insert and Read Only (no deletes or updates). In table properties, I specfiically selected not to create the Update or Delete sprocs but to create the Insert.

The problem is not so much that the DDT doesn't want to create the sproc but that that the error message it gives just tells you that "a stored procedure" was not created and doesn't tell you which one. I have a large number of tables and it took me quite a while to track down the culprit.

Thanks!

Clay

Clayton,

I am not sure how to reproduce what you are talking about here.  Where do you get the error message?