Have a new brain-picker of a problem 2

[chunkII123]

As I stated in my last thread I amnota programmer, aspiring programmer, nor do i have the urge or want to be a programmer. I was however thrust into a job that requires me to do minor tweaks and fixing of another idiots programming, that being said I now have a new problem with some coding, in the management section of our little Access Database we have a spot to put in the password and anyone who has a head on top of their shoulders can pull up the debug menu for the module. The first thing you see within this module is

Private Sub enterButton_Click()

Dim Entry As String

If Len(password.value) >= 0 Then

Entry = password.value

If (Entry = "makelovenotwar" Or Entry = "th3s3condmonth" Or Entry = "flowers4sale!" Or Entry = "321") Then
SignsButton.Enabled = True
MenuDMButton.Enabled = True
MenuSourceButton.Enabled = True
MenuOtherOfficeButton.Enabled = True
MenuOfficeButton.Enabled = True
MenuEditButton.Enabled = True
MenuOtherButton.Enabled = True
SourcesButton.Enabled = True
MenuReportButton.Enabled = True
EmployeesButton.Enabled = True
lookupButton.Enabled = True
employee_weekly.Enabled = True
openReport.Enabled = True
printDaily.Enabled = True

now those are the passwords used to access the management module and functions, how would one go about hiding the entries within this statement "If (Entry = "makelovenotwar" Or Entry = "th3s3condmonth" Or Entry = "flowers4sale!" Or Entry = "321") Then" Any helpis appreciated.

 

[PWise]

change the file to an mde

 

[randy700]

Put the valid passwords in a table and with an input mask of password. Use dlookup to determine if the value entered is in the password table.


Randy

 

[TheAceMan1]

How are ya Matchmakermmi . . .

Be aware: all a programmer in the know has to do is [blue]set a break point[/blue] and hover the cursor over whatever you use to return the values!

The best I can think of is to set a [blue]password[/blue] for viewing your VBA. In any code module [blue]Tools[/blue] - [blue]Design Properties[/blue] - [blue]Protection Tab[/blue]. Check the [blue]Lock project for Viewing[/blue] checkbox and set your password. Click OK then close/reopen the db and try to get into any code module.

[blue]Your Thoughts? . . .[/blue]

BTW: Welcome to [blue]Tek-Tips![/blue] Do have a look at one of the links at the bottom of my post. The links will help you [blue]ask better questions[/blue], get [blue]quick responses[/blue], [blue]better answers[/blue], and insite into [blue]etiquette[/blue] here in the forums. Again . . . Welcome to [blue]Tek-Tips![/blue] [blue]Its Worthy Reading![/blue]

See Ya! . . . . . .

Be sure to see thread181-473997 [blue]Worthy Reading![/blue]
Also faq181-2886 [blue]Worthy Reading![/blue]

 

[chunkII123]

Randy,

How would I go about doing that, I am curious, would the password table still be viewable from the debugger? Thanks ahead of time.

-Josh

 

[TheAceMan1]

Matchmakermmi . . .

[blue]There's no place to hide values that a learned programmer won't eventually find![/blue]

Wether its a table, DB Properties (my initial thought), or some devised encryption. Other than tables (security of which for me is easy to break), VBA is required to track down and finally reveal values sought. DB properties can only be accessed thru VBA, as well as encryption which has to have a decryption routine/function to return the vales.

My point is: for all the complexity you may hide values with, which 99.999% of the time requires VBA ... [blue]a pasword to unhide VBA will be the hardest to break![/blue] ... This is why I prompted to hide VBA! All the complexity to hide a value is there! ... somewhere!

Give it more thought!

[blue]Your Thoughts? . . .[/blue]

See Ya! . . . . . .

Be sure to see thread181-473997 [blue]Worthy Reading![/blue]
Also faq181-2886 [blue]Worthy Reading![/blue]

 

[chunkII123]

Aceman

I would have thanked you sooner, however I was locking down the other parts of our network and requiring login's and passwords for authentication to server (just like high school). Anywho, After reading that I followed your directions to a 'T' and found that that worked great, no one but myself is able to access the VBA code, so we're good to go, and thank you everyone for the help!

-Josh