Hi Kelly,

Thanks for the feedback...

I think the solution to this problem is to allow a database prefix in the business object. This was really an oversight on my part. I have a tablename property in my bus-object which maps the 'default' table that the object is bound to. At first I thought I could use the tablename and simply store the database in that but that causes problems in a few other places where the table name is used (key generation for example)...

I have to play with this stuff some more and see, but after hitting the wall the other night with Oracle I was pretty fed up <g>... especially since I myself am not likely to use it <g>...

+++ Rick ---


>I think you're probably right about it not being realistic for 100% of Oracle production environments. It at least wouldn't be ideal if you didn't account for the possible need for schema prefixes.
>
>FWIW though, the Oracle/Fox app that I inherited and maintain/extend here does use a one-login/schema structure. It doesn't prevent me from knowing who's logged in because Oracle has a system "variable" that provides the Windows login name. Of course the app has them do a login anyway and that's used for security. But when looking at the Oracle management tools, it's nice to be able to see who the Windows user is even though they all have the same Oracle login name. Even the machine name is provided, which is also nice.
>
>My point is that a one-login solution can work just fine in production, but I don't know how prevelant that scenario is. Bottom line is that Oracle folks could use your class if they use a single login or have synonyms set up for all objects. Based on what Mark was saying, I'd guess that most people would do the latter, but you probably can't count on that.
>
>Kelly
>
>>Thanks Kelly,
>>
>>This actually makes a lot more sense now...
>>
>>This is just a test for me to see if I can get to work with the oracle provider. I'm trying to get my bus objects to work with it, and it works with the exception of the database prefixes which screws with my 'tablename'...
>>
>>I may have to rethink this and add an optional DataBasePrefix and embed that into each command as needed...
>>
>>Pretty lame that you can't select a data base directly, but with the Logon at least I might be able to test. Don't know if that is a realistic requirement though - you wouldn't want to have everybody logging in as the 'owner' fo the database...
>>
>>+++ Rick ---