<i><font color="#663300">
Hey BOb,
Thanks for your answer, but it raises a few questions.
1. What SQL Login?
I am using CodeBook 6. I have created a new login form, which takes the username and password and passes it back to Oracle using a SQLEXEC statement. If all is well, the aplication then continues the login processing, setting the userid and password connection properties. Then ,using the CodeBook security, populates the security table, which is a parameterized view of the secure controls, with their enabled and visible states.
</font></i>
If you don't put the username and password in the connection, when you initiate the connection (open a remote view) a SQL Server login form will be displayed. This will allow the user to login to the server.
<i><font color="#663300">
2. What will the remote views use to access the data if the connection in the database does not have the required userid and password fields?</font></i>
Two answers here...
1. If your views are set to share a connection, once they are logged in, the connection is established, there are no futher connections/logins needed.
2. If you use NT Authentication (which is the best choice) then the user never sees the SQL Login, nor is an ID/Passwd needed and SQL server asks the domain controller to authenticate the user. Once SQL recieves this authentication it grants rights to the user accordingly. (Here you should also use shared connection views.
There are some other options, espesially with 7.0, but I'll wait till you ask me those questions.
BOb
©2002 Bob Archer |
