Hiding Confidential Information in a Lookup Database

[DBMS_Queen's]

I'm creating a database form that retrieves information from another reference database. The users of the form will be entering a password in a field linked to the reference database table. When a match is made, a number of other correlating fields are populated with information specific to the record related to that password from the reference database.

There are 2 problems:

- The field in which the application user must type their password enables a pop up list of all the info in the reference database (which is supposed to be confidential or sequestered).

- Even if the correct password has been entered, a mouse click will again reveal the contents of the reference database.

I have already tried turning off the display on the mapping form under the look-up tab, but this only converts the pop-up window to a blank form that users can still use to select other member's information (i.e. by clicking randomly within the pop-up form).

In the original Alpha 4 (I'm dating myself) version of this application, this problem is solved by selecting "Hidden" under the "Location" option for the Popup window of the lookup or reference database table.

This is a major hurdle. Any advice that would help hide the information in the lookup database or fill the fields linked to a password so no other confidential info is visible would be greatly appreciated.

[DaveM]

Re: Hiding Confidential Information in a Lookup Database

Probably not enough information given.
are you getting you lookup in field rules, how are you defining the correct user, how are you getting the password, how and where do that enter the password?
Pictures? sample table/db??
I too came from pre alpha5

[DBMS_Queen's]

Re: Hiding Confidential Information in a Lookup Database

Yes I am facilitating the look-up with the field rules and I have attached my field rule settings below:

Field Rule Settings.JPG

Each user is given a different password that is stored along with their other information on a reference database. Thus, when the user enters their password into the text box (as demonstrated in the image below), the form automatically fills in the rest of the information (also shown below):

User Form.JPGUser Form (After Password).JPG

However, as I pointed out in the image, an empty look-up form appears beside the password's text box that allows the user to click within this form and see another user's information. I wish to remove this pop-up look-up form while leaving the rest of the operations intact. I have attached a visual of the reference database if needed:

Reference Database.JPG

[Peter.Greulich]

Re: Hiding Confidential Information in a Lookup Database

Set the user password field value to a session variable. Then use the field rule lookup's filter expression to filter the field on the session var.

[DBMS_Queen's]

Re: Hiding Confidential Information in a Lookup Database

Peter, I am a very basic user (I am using Action Scripting as opposed to xBasic) so I am not familiar with this process. Would you be able to walk me through the steps to use the session variables?

I would also like to add that this application is meant for a stand-alone work station without internet access.

Thanks.

[Peter.Greulich]

Re: Hiding Confidential Information in a Lookup Database

On the form, in the password field's OnDepart event, put in the following code:

Dim shared vPwd as C = this.value

This assumes that your password field is character type, if it is numeric type do this:

Dim shared vPwd as N = this.value

Then in your field rules/table lookup filter put in something like:

YourFieldName = var->vPwd

Then the lookup should only show the records matching the password on the form.

[DBMS_Queen's]

Re: Hiding Confidential Information in a Lookup Database

Hi Peter,

This is Robert from Queen's University speaking on behalf of Chris. Thanks for the prompt response. Unfortunately, when following your instructions I have run into an error (it says that the variable vPwd cannot be found). I have attached an image below of the error message:

Error in Table Rules.JPG

I was wondering if this had to do with the first line of code that you gave: Dim shared vPwd as C = this.value. In this case, do I enter this.value into xBasic or is the "this" in the equation a substitute for a different file pathway that I should use? I have attached an example of what I have done below:

xBasic on Form.JPG

Thanks again.

[Peter.Greulich]

Re: Hiding Confidential Information in a Lookup Database

Hi Robert,

No you have the syntax right. To simplify this try changing the line of code as follows:

Dim Global vPwd as N = this.value

[Peter.Greulich]

Re: Hiding Confidential Information in a Lookup Database

Oh, in the event that Alpha won't allow you to save that line of code in the field rules. Go edit the table structure and vPwd as a global variable - see image...

Global var.png

[DBMS_Queen's]

Re: Hiding Confidential Information in a Lookup Database

To Peter,

Thank you very much for all of your help. However, despite your assistance I have yet to overcome this obstacle. Perhaps it will help if I provide some context to the situation:

I am working on recreating a perfectly functioning (DOS) database that I had created with Alpha Four for a Life Science stockroom. I regularly stock the room myself and then faculty check out their desired products through an honour system (i.e. they log in to the database and then choose an item and record their purchase). Upon doing this, the database records who made the purchase (as identified when they enter their password) as well as what was purchased, the total amount to be charged and the grant to charge it to.

In an imitation of the old database, I have been trying to create a user form that prompts for a password, and upon providing it, retrieves the user's specific data from a reference database and displays it on a form. Afterwards, the user can select items through a drop-down list of the inventory.

[Peter.Greulich]

Re: Hiding Confidential Information in a Lookup Database

Upload a sample db in a zip file and I will take a look and get it working for you. Please don't upload Alpha itself.

[Ray in Capetown]

Re: Hiding Confidential Information in a Lookup Database

... a user form that prompts for a password, and upon providing it, retrieves the user's specific data from a reference database and displays it on a form. Afterwards, the user can select items through a drop-down list of the inventory.

The first should not use a lookup or prompt any way. Once entered, fetch the matching record and if found complete the form.
The second part will, as described.

[DBMS_Queen's]

Re: Hiding Confidential Information in a Lookup Database

Peter,

Thank you very much for doing this, I am very grateful for your help both now and before. However, I would feel more comfortable sending this to you over email (as an attachment) if that is alright?

[DBMS_Queen's]

Re: Hiding Confidential Information in a Lookup Database

Peter,

I would like to thank you for your valuable assistance. With your prompt help I was able to overcome this major hurdle and continue forward with my creation. I appreciate the time you spent assisting me.

Robert