<< Within UniVerse you can do the same thing. You can restrict user read, write, delete access to the database either setting OS level file access or by SQL security access. With the AUTHORIZE statement, you can allow subroutines to have a different access rights. Thus from UniObects one can only access the database through subroutines and they cannot do anything else. >>
<<Could you explain a little more fully how you do this? Thanks Will Johnson>> Within UniVerse Basic is an AUTHORIZE Statement which allows you to give the program different access rights to the user running the program. Ie AUTHORIZE "Administrator" This would give the program the access rights of Administrator at SQL security or OS file security level. The program has to be compiled by the user who the authorize statement will adopt as user rights ie the example above would have to be compiled by Administrator. ED BP TEST AUTHORIZE "Administrator" ... OPEN "","TEST" TO FV ELSE... ... WRITE REC TO FV,KEY User Joe has no access rights to the UniVerse data files either by setting OS file level security or by not GRANTing access if SQL level security installed. IF Joe did ED TEST 123 the system would not grant him access But if Joe runs the program TEST it would write the record to TEST file. Regards David Jordan ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/