Is there a way to run a High Level process by a Low 1 user ?

Like enforcing a procedure with High Level userid and password in the DQL code.

Download Sample

Hi Arul.

No and yes.
The restrictions are there for a reason so if there was a hack to go around them there wouldn't really be any security.

The way to do this is simply to start another instance of DataEase with a user that has high privilege from a DQL with low privileges.

see example below.

define "retval" text .

retval := executefile(concat("/'",getcurrent("Progrpath"),"dataease.exe/' /'",getcurrent("AppPath")," runhighfromlow/' high high")) .

Remember that you need " " around path and app name etc. if they contain spaces.

For other reasons this is achieved by using the escape character for " which is /' in DE8. 

When you open a High session in DE8 even with a direct open of a document the user will be able to go to Development mode if you don't take precaution.

1. The best way is to use Player (in our example we use Developer but you can just change out the path/program).
2. Remove the FileMenu completely on the DQL as all shortcuts are stored here so user can't use shortcuts.
3. start up with a chainmenu that exit dataease silently in the next button (se sample).
4. Remove all toolbars/filemenus in DQL with SetCurrent().

define "retval" text .

retval := SetCurrent("FileMenu","Off")+SetCurrent("Toolbar","Off")+SetCurrent("TabBar","Off") . 

This question started. Because, I wanted to get Current Password, for someone already logged in with Low 1 access.

By getting this password, we are going to activate another program outside of DataEase.

Can we get current password? similar to current user name

Hi Arul.

No there is no such feature and in many peoples mind that is a good thing. It is a bad thing that you can see all passwords when you have high.

Passwords should never be stored and we will remedy this and store only a hash of passwords in the future so you can come to the same answer when you type in the password but you can't calculate backwards to find the password. This is industry standard now.

You can lookup the password value from user table but not when you have Low1 so this is a dead end street.