Sorry. I mean as the schema owner. I create a user called MyStoreApp and create all the tables, etc., as under that user. I then connect as MyStoreApp in my app. THe app users have no clue as to the user ID I am using since it is buried in the compiled app. Decompiling is my only real issue here. If there is more than one schema per app, then you are right back where you started needing the prefix.

While I do have some code in the biz layer, I do still have extensive data integrity checking in the DB layer in Oracle SPs.

>>Personally I prefer connecting as the DB owner within the app as Kelly talked about and NOT using SPs only. I do not have to prefix tables with the schema name, I do not have to deal with privs on the DB side. You can get as creative as you want with how you set up who can do what. I do this with a user access table in Oracle.
>
>How does this work if you are the db owner of more than one of the schemas?
>
>I like this approach.
>
>Problem is that this is generic code in a bus object layer. I think making assumptions like this are a bad call. As I mentioned to Kelly I think the only real workaround for this is to use a Database prefix as an optional property on the bus object.
>
>+++ Rick ---