Ted
I will try the &connect and see if that works.
I am having a strange problem getting my app to work in V8 and I am working
with RBIT too..
I just did not want to ask them a syntax question and it appears this is the
line of code that
gives the error. My guess there is something strange about my app that is
causing the error
and it may not be that line of code that is the fault.
Or maybe I have some strange sypware thing giving me trouble?
Thanks
Marc
From: Ted Lienhard
Sent: Friday, April 24, 2009 2:26 PM
To: RBASE-L Mailing List
Subject: [RBASE-L] - Re: SET USER .vuser ??
Hi Marc,
I have been using this syntax for some time now, and it works fine for me. I
thought it might provide an alternative means for your purposes:
--This connects to the database by a username that only has rights to the
password table:
CONNECT DBName IDENTIFIED BY UserName password
--This next line sets the password variable (vpassword) to the desired
operational password stored in the table:
SET VAR vpassword TEXT = adminpassword IN adminpassword WHERE COUNT = 1
--This next line sets the entire connect command into a variable:
SET VAR vconnectstmt TEXT = ('CONNECT DBName IDENTIFIED BY MAINUser'&
.vpassword)
--The Ampersand variable run as a command line:
&vconnectstmt
--Finally, the variable is cleared so that it cannot be read by running the EEP
within RBase
clear variable vpassword, vconnectstmt
I run this command structure, or a variant, in an OnBeforeStart EEP in the
External Form used as the first form in my applications. Once this
authentication for the database is established by running the EEP, you can do
anything else you want regarding selection and authentication of users. It
works really well for functions that must have owner rights - re-numbering
autonumber columns, etc. You can CONNECT as owner, perform the necessary
task(s) and then CONNECT as the normal user for typical use.
An undocumented feature of RBase is that you can even CONNECT in the middle of
a normal form...just make sure your newly connected user has rights to that
form and any tables utilized therein!
By the way, don't forget to Disable Trace on the EEP form, or your code can be
read during a trace, including your password variable(s). I also include a SET
TRACE OFF command as the first line of the OnBeforeStart EEP, just for good
measure. My application is a compiled app, done by using R:Compiler. I
compile the first External Form, and then I don't even need to distribute the
External Form itself, just the compiled app. This combination of steps is how
I keep my code secure on a distributed application.
Probably too much information, but hope it is of some help.
Best Regards,
Ted
Ted Lienhard CNE NCT
Golden Valley Consulting
>>> MDRD<[email protected]> 4/24/2009 9:26 AM >>>
Hi
I am having trouble with this line in V8
SET USER .vuser it gives an Access Viiolation error
The var vuser is set and this code has been working fine in 7.5 for a long time.
Is there something special I need to do in V8?
I have the user type in a login Id and we look up their user password in a
table.
Thanks
Marc
