Hiding Info

[maxmangion]

Hi,

I have created a query from two tables which returns personal info such as firstname, surname, idcard etc. Due to data protection act i cannot distribute this information to third parties, however, i need a way where the third party can at least input the idcard number on a form and i simply return a message where that id exists in the list or not.

I have managed to achieve this by creating an unbound text box on a form to accept the id and used the dcount function to check whether the id exists i.e.

Private Sub btnSearch_Click()
Dim LTotal As Long
LTotal = DCount("stu_extr", "Query1", "stu_extr = '" & Me.Text0 & "'")
If LTotal = 0 Then
MsgBox "Student Not Found"
Else
MsgBox "Record Found"
End If
End Sub

The above works fine, however, my only concern is how can i pass on this database but "totally" preventing them from viewing the tables/query data (as accessing the tables/query would be defeating the purpose of the database)

Thank You

 

[namliam]

You dont... Unless you can upload the data onto a secured server environment like SQL Server/Oracle or the like.

Alternatively you can distribute a database with ONLY the card number in it in a table...
Or...
Load the table into an array in code, then secure the code to not be accessable at all.

Access is never 100% securable (as far as I know)

 

[maxmangion]

Hi namliam,

Thank you for your reply and suggestions. Right now i see the idea of simply distribute the database with the id field as the most viable option.

Load the table into an array in code, then secure the code to not be accessible at all.

I will try to research/read about this idea as i have never used it so far, so not sure how do i go about it. However, would this suggestion be feasible if at certain time of the year (maybe once or twice), i would have to update the list of idcards i.e. adding/deleting?

Thank you

 

[namliam]

Well either solution you have to update on a regular basis correct?

I havent used an array that big ever, so I dont know if it would work or how good it performs.

Doing a table with only IDs (thus protecting privacy) is the fastest and certainly easiest way... Unless you have some "big and secure" database at hand...
There is no good (enough) way to protect your tables (that I know of), perhaps hiding the table(s) will confuse the most "basic" of users, but more experienced "users" will find them regardless.

 

[tranchemontaigne]

putting information into an array in a code module is the less secure option and makes maintaining data a hassle
________
Magic Flight

 

[DCrake]

One other solution you could try would be to write some code to copy the record ids to a txt file using the Open file for output As #1 technique

Then simply send them the text file.

At the other end they would perform an Open File for Input As #1

to loop through all the contents of the text file. Or import them into an existing table in there mdb which they can do a dlookup on.

If you create a standard Encrypt and Decrypt code shared between each other you could include ecrypted data in the text file that could be decrypted by the other users.

Just a thought.

 

[maxmangion]

thanks both for the replies, i think the best solution would be to have a table with just the idcard field.

Thank You