<i><font color="#663300"><i
Yea, I agree. Unfortunatly in 6.0 there is no way to do this, without putting the userid and password in the DBC, which is not very secure.
What you can do though is eliminate your CB login screen. Open your initial view, the user will get the Oracle Login. If this is successful, get the user ID from Oracle and silently log them into your client side security system. This way they get only one login screen.
Also, you don't have to worry about the 'where do I store the user names and logins and how do I access them before the user has logged into Oracle?' So, now, Oracle is handling passwords and authentication for you.
BOb
</font></i>
Again, thank you for the advise, I am working that solution out now. What I am concerned about is the login failure. The ODBC Driver Connect will reappear if the user enters a bad userid or password after Oracle returns an error message. This allows the user to try again. (I am assuming that the Oracle login attempts limit is still in affect for logining in through the ODBC Driver Connect.) My question is how do I capture the cancel if the user decides to cancel the login, so that I can bail out the application?
Mike D
Devman
mdevlin /AT/ ajdebruin .DOT com
©2002 Mike Devlin |
