<i><font color="#663300">1. Why not just let the user log in using the SQL Login and don't store the info in the connection. I don't populate those fields since they are not secure.
2. Putting a copy of the .DBC on the client machine would solve this and other issues.
BOb
</font></i>
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.
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?
Devman
mdevlin /at/ ajdebruin .D.O.T com
©2002 Mike Devlin |
