Re: Tables in a database

Thanks for replying. Unfortunately the tables are being forced upon us by the application: Business Objects. B.O. creates a repository that handles the users security etc. and we cannot control the structure, but each universe repository needs to have its own set of tables. I may have to rethink whether we will allow 2 repositories which would remove the need for multiples on the same d.b. The contractors who are in helping us set up the repository just keep saying *really* useful things like "You wouldn't have this problem with Oracle" or "You can do that on Oracle". I bite my tongue. Mark Fisher Britannic Assurance -- Nils Myklebust wrote: > > Most of the time when you have a problem like this you should either > be able to solve it via temporary tables (where each session can have > one of the same name) or some other simple construct. Sometimes an > extra column with the username in a common table may be appropriate. > > If you post something about what you intend to achieve someone might > give you more ideas. ------------------------------------------ The views expressed here are mine and not those of my employer, Britannic Assurance ------------------------------------------